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
- The PWM pins are not fit to a ODROID_C4 manual list of extension pins. To fit
the list, a pwm_ab is added. And pwm_cd's pwm_d pin is moved.
- The Device tree Overlay feature is applied to the PWM.
Change-Id: I77b5b5691ab9f71740edfd5fe3d3bdc430fdaca3
PD#SWPL-16891
Problem:
For automatical test, the HDMI cable are always connected between Tx and Rx
without manully action.
Solution:
add a fake hpd for system test
echo 0[1] > /sys/class/amhdmitx/amhdmitx0/fake_plug
Verify:
G12/U212
Change-Id: I826fc0094845a13066a1535a4a87727b4ecad452
Signed-off-by: Zongdong Jiao <zongdong.jiao@amlogic.com>
PD#SWPL-18673
Problem:
when hotplug cable very quickly, the pin contact may
be loose and edid read wrong, system will output
default 1080p+rgb signal, after the pin contact
ok and edid read ok, DV module send DV signal, the
output mode and DV signal may not match, cause
TV show green screen.
Solution:
only attach vinfo after hdmi mode setting done.
Verify:
AC214
Change-Id: Ice60d44f55ed377dbab4bef4639d67c263a6bbb6
Signed-off-by: Hang Cheng <hang.cheng@amlogic.com>
PD#SWPL-16472
Problem:
on Hisense-HZ55A65, under Y420+deep color,
it will show blue(for some ms) and then keep
green screen after receive set_avmute
Solution:
after set avmute, decrease the delay time to
disable output, to avoid flash on Hisense-HZ55A65
Verify:
AC214
Change-Id: Id2a25b21c56118f363f7085d22ac590051dec585
Signed-off-by: Hang Cheng <hang.cheng@amlogic.com>
PD#SWPL-17841
Problem:
need correct the threshold value of rxsense
Solution:
correct the threshold value of rxsense, regress OTT-1968 to trunk
Verify:
G12/U212
Change-Id: I53f370cf51c0ad39e92fd64a0cc98cc4680eea4d
Signed-off-by: Zongdong Jiao <zongdong.jiao@amlogic.com>
