The Bluetooth parts of RTL8723D and RTL8723B share the same lmp
subversion, thus we need to check both lmp subversion and hci revision
to distinguish the two. The same situation is true for RTL8821A and
RTL8821C. Accordingly, the selection code is revised.
To improve maintainability, a new id_table struct is defined, and an
array of such structs is constructed. Adding a new device can thus be
as simple as adding another value to the table.
Signed-off-by: Alex Lu <alex_lu@realsil.com.cn>
Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Change-Id: Ic98eb91ac87a671d7fc3d2a611545e36c3c8cf69
In case of using BT_ERR and BT_INFO, convert to bt_dev_err and
bt_dev_info when possible. This allows for controller specific
reporting.
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Change-Id: I3cd472bf3ce8e797b112c36227884ee2d80b6394
We accidentally return success if the kmemdup() fails. It results in
a NULL dereference in the caller.
Fixes: 1110a2dbe6 ("Bluetooth: btrtl: Add RTL8822BE Bluetooth device")
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Change-Id: Idd4ff62726885f4aafb3aae69c7cddb12c08442b
The message concerning missing config files for 8723b, 8821a, and
8761a should have been issued with BT_INFO() rather than BT_ERR() as
this condition is not fatal. After looking at that code, I have
reworked the logic to log such messages only if the device needs such a
config file. At the moment, only the 8822b fits that description.
Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
Acked-by: 陆朱伟 <alex_lu@realsil.com.cn>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Change-Id: I8449be0c4487c8e7af034753cddcc795205ff503
The existing force64b routine might not work properly under specific
conditions. This patch fixes that bug of 64 bits per word and forces
use that option. It will improve SPI performance significantly.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I85a58d425303ea1765b7b83ee5dd5f0a7f4203fc
In case of 2560x1600@60hz, unstable display operation may occur
with some specific monitors those pixel clock is under 300MHz.
So, default timing for 2560x1600p60hz is set as following.
Detailed mode: Clock 268.500 MHz, 641 mm x 401 mm
2560 2608 2640 2720 ( 48 32 80)
1600 1602 1608 1646 ( 2 6 38)
+hsync -vsync
VertFreq: 59.972 Hz, HorFreq: 98.713 kHz
Change-Id: Iec9df8713211cf5e0dc7ba09f3dba2948e479b4f
- To avoid conflicts with the default gpio-power key pin and the SPI
pin, default shortcut pin maps are changed.
Change-Id: If857eafc1e9df101357203ad61ea6ea81b11b571
- To support ap6255, we made wifi/bt combo support board. To use it with
a ODROID-C4, You need chagne R45 to 10k register. Or please change a
'gpio_reset' to other pins.
Signed-off-by: Luke go <sangch.go@gmail.com>
Change-Id: I208c11251e3b36bdf27d1505e5bb25a1f4a059c4
PD#SWPL-15199
Problem:
tunig process of hs400 is too slow
Solution:
saved tuning parameter of hs400 on emmc
Verify:
passed on tm2_t962e2_ab311
Change-Id: Ifd1ba375dd93745c9db33a94f3480ebfc21e999f
Signed-off-by: Ruixuan Li <ruixuan.li@amlogic.com>
Signed-off-by: chunlong.cao <chunlong.cao@amlogic.com>
PD#SWPL-28058
Problem:
the PCIe wifi is not recognized,
because wifi is not powered on.
Solution:
power on wifi by default.
Verify:
AC200
Signed-off-by: libo <bo.li@amlogic.com>
Change-Id: I254324756695bdcabfa808d84b69298d392f669d
PD#SWPL-30668
Problem:
too many vecm printk durning boot.
Solution:
Unnecessary prints by annotated
Verify:
on x301
Change-Id: Ia15dc9c83d62e1055bbf2c4dedf7d0619be17344
Signed-off-by: Cheng Wang <cheng.wang@amlogic.com>
PD#SWPL-30662
Problem:
Too many logs during kernel boot up, which slows system down
Solution:
Remove unnecessary logs
Verify:
AC214
only two lines remained
[4.967828] unifykey: no efuse-version set, use default value: -1
[4.968140] unifykey: aml_unifykeys_init done!
Change-Id: I093f93825f8478bb692092c877b32d374cdb7039
Signed-off-by: Jiamin Ma <jiamin.ma@amlogic.com>
PD#SWPL-20468
Problem:
nv12 format is not support in vpp
Solution:
add nv12 format support
Verify:
on U212
Change-Id: I1e621bede63a283931743c2cd3a5ea1548149368
Signed-off-by: Dezhi Kong <dezhi.kong@amlogic.com>
