To avoid recursive dependencies on GPIOLIB when 'imply IIO' is requested
with other drivers we should switch GPIOLIB to an imply.
This isn't the most ideal solution but avoids modifiying the Kconfig for
other drivers, and only requires a singular IS_REACHABLE(CONFIG_GPIOLIB)
check.
Signed-off-by: Matt Ranostay <matt.ranostay@konsulko.com>
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Change-Id: Ie379ae18bd2aae09b576238298715055ca616f0d
Switch from i2c_add_adapter() to resource managed devm_i2c_add_adapter()
for matching rest of driver initialization, and more concise code.
Signed-off-by: Matt Ranostay <matt.ranostay@konsulko.com>
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Change-Id: I642fcb5af3894a2010b4a8f2f06098abaecf6812
SoC level driver bugs to manage kernel binaries as well as import them
to initramfs to make them load very early, this could cause boot failure
when one fails to update initramfs. So such driver must be in kernel
blob itself, not to miss.
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
Change-Id: Iea67d3fa3a97146db47cae25b2a7d5eb5b938f5c
PD#SWPL-185765
Currently, rumble is only supported via bluetooth on a single xbox
controller, called 'model 1708'. On the back of the device, it's named
'wireless controller for xbox one'. However, in 2021, Microsoft released
a firmware update for this controller. As part of this update, the HID
descriptor of the device changed. The product ID was also changed from
0x02fd to 0x0b20. On this controller, rumble was supported via
hid-microsoft, which matched against the old product id (0x02fd). As a
result, the firmware update broke rumble support on this controller.
The hid-microsoft driver actually supports rumble on the new firmware,
as well. So simply adding new product id is sufficient to bring back
this support.
After discussing further with the xbox team, it was pointed out that
another xbox controller, xbox elite series 2, can be supported in a
similar way.
Add rumble support for all of these devices in this patch. Two of the
devices have received firmware updates that caused their product id's to
change. Both old and new firmware versions of these devices were tested.
The tested controllers are:
1. 'wireless controller for xbox one', model 1708
2. 'xbox wireless controller', model 1914. This is also sometimes
referred to as 'xbox series S|X'.
3. 'elite series 2', model 1797.
The tested configurations are:
1. model 1708, pid 0x02fd (old firmware)
2. model 1708, pid 0x0b20 (new firmware)
3. model 1914, pid 0x0b13
4. model 1797, pid 0x0b05 (old firmware)
5. model 1797, pid 0x0b22 (new firmware)
I verified rumble support on both bluetooth and usb.
Change-Id: Ia84736e95dadc61e442276ae943f370fe0cb6526
Reviewed-by: Bastien Nocera <hadess@hadess.net>
Signed-off-by: Siarhei Vishniakou <svv@google.com>
The use of kmap() is being deprecated in favor of kmap_local_page()
where it is feasible. With kmap_local_page(), the mapping is per
thread, CPU local and not globally visible.
binder_alloc_clear_buf() is a function where the use of kmap_local_page()
in place of kmap() is correctly suited because the mapping is local to the
thread.
Therefore, use kmap_local_page() / kunmap_local() but, instead of open
coding these two functions and adding a memset() of the virtual address
of the mapping, prefer memset_page().
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Acked-by: Todd Kjos <tkjos@google.com>
Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
Link: https://lore.kernel.org/r/20220425175754.8180-2-fmdefrancesco@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Bug: 368205746
Bug: 365876437
(cherry picked from commit 26eff2d66a)
Change-Id: I7bc041db662ee1e8758c173861b2229d6ad8eb1e
Signed-off-by: yenchia.chen <yenchia.chen@mediatek.com>
Signed-off-by: Carlos Llamas <cmllamas@google.com>
The use of kmap() is being deprecated in favor of kmap_local_page()
where it is feasible. With kmap_local_page(), the mapping is per
thread, CPU local and not globally visible.
binder_alloc_copy_user_to_buffer() is a function where the use of
kmap_local_page() in place of kmap() is correctly suited because
the mapping is local to the thread.
Therefore, use kmap_local_page() / kunmap_local().
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Acked-by: Todd Kjos <tkjos@google.com>
Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
Link: https://lore.kernel.org/r/20220425175754.8180-3-fmdefrancesco@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Bug: 365876437
Bug: 367895677
(cherry picked from commit 1d625960e4)
Change-Id: I49739365cf5dcf584be1aab0c93848aa9ce886a8
Signed-off-by: Carlos Llamas <cmllamas@google.com>
PD#SWPL-169224
Problem:
ntfs3 fs_umode_to_dtype not in abi list
Solution:
ntfs3 fs_umode_to_dtype not in abi list
Verify:
local
Change-Id: Ibf190585f7606539b5df98151e8dd617ad66c9da
Signed-off-by: qinglin.li <qinglin.li@amlogic.com>
PD#SWPL-170009
Problem:
Synchronous run queues cause eMMC performance degradation.
Solution:
Asynchronous Run work queue.
Verify:
T3
Change-Id: I214f2d813373b46fd5fc64f050e00a395dd35828
Signed-off-by: Long <long.yu@amlogic.com>
PD#SWPL-153208
PD#SWPL-131346
Problem:
1.When the memory is in short supply, if the
order is too large, the memory will not be
allocated at one time, which will increase
the allocation time.
2.Modify in vb2 did not following gki2.0
Solution:
1.According to the degree of memory shortage,
adjust the size of the order, so as to allocate
memory in small amounts and multiple times to
improve efficiency.
2.The modify in vb2 only for versions prior to
androidT and do not need to follow gki2.0. Now
use the new config to pass gki check.
Verify:
ohm
Change-Id: I4be66b8b06f9870041afefe9506d1e9f480c0bdd
Signed-off-by: Hao Shi <hao.shi@amlogic.com>
PD#SWPL-150301
Problem:
Fdtoverlay cann't support remove unnecessary dts node.
Solution:
Add __removenode__ key work to support the function.
Verify:
local
Change-Id: I3819a82663a90ae7a4da1d9c30c990af2d3a5fa0
Signed-off-by: haotian.qu <haotian.qu@amlogic.com>
This reverts commit 3a94958894.
It conflicts with scheduler changes going into 6.3-rc1 so it must be
removed. If it is still needed it can be brought back after 6.3-rc1 is
merged into android-mainline.
Bug: 157906395
Cc: J. Avila <elavila@google.com>
Cc: Stephen Dickey <quic_dickey@quicinc.com>
Cc: Lee Jones <joneslee@google.com>
Change-Id: I9870034226407bc811db9c36802f0446289f13f0
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
PD#SWPL-106598
Problem:
Support making dtb-deb.
Solution:
Support making dtb-deb.
Verify:
local
Change-Id: I3cb8e8d5666f073468e55e4a4e8862f12e60b15f
Signed-off-by: yi.liu <yi.liu@amlogic.com>
PD#SWPL-130061
Problem:
Need to support trusted key for FBE.
Solution:
Hook trusted key to fscrypt
Verify:
1. fscryptctl(add_key)
2. on SC2(ah212)
Change-Id: Ie40df4ec2506f4fc4d6f7c2a52863db6e3bc661c
Signed-off-by: Mingyen Hung <mingyen.hung@amlogic.com>
PD#SWPL-135783
Problem:
1. need use regulator to delay dvfs voltage set;
2. for boot to kernel vddcpu/vddee voltage
change to max problem;
Solution:
1. add dvfs delay time at s7 pxp;
2. add init voltage at txhd2 trunk;
Verify:
build pass
Change-Id: I877e9affaced264b57c887c05f4545ad22816789
Signed-off-by: chengbing.wu <chengbing.wu@amlogic.com>
