diff options
| author | Diederik de Haas <didi.debian@cknow.org> | 2024-10-18 17:45:50 +0300 |
|---|---|---|
| committer | Heiko Stuebner <heiko@sntech.de> | 2024-10-25 09:41:15 +0300 |
| commit | 08846522d9a7bccf18d4f97c3f39d03c7a193970 (patch) | |
| tree | 3a1afb1e9ed6eb0145d1e3c7dcff4fc2e09fb93a /tools/perf/scripts/python/mem-phys-addr.py | |
| parent | a4dca88c9c3abd2ba73d09fb5b365fdf7d5198a3 (diff) | |
| download | linux-08846522d9a7bccf18d4f97c3f39d03c7a193970.tar.xz | |
arm64: dts: rockchip: Correct GPIO polarity on brcm BT nodes
Paragraph "3.4 Power up Timing Sequence" of the AzureWave-CM256SM
datasheet mentions the following about the BT_REG_ON pin, which is
connected to GPIO0_C4_d:
When this pin is low and WL_REG_ON is high,
the BT section is in reset.
Therefor set that pin to GPIO_ACTIVE_HIGH so that it can be pulled low
for a reset.
If set to GPIO_ACTIVE_LOW, the following errors are observed:
Bluetooth: hci0: command 0x0c03 tx timeout
Bluetooth: hci0: BCM: Reset failed (-110)
So fix the GPIO polarity by setting it to ACTIVE_HIGH.
This also matches what other devices with the same BT device have.
Fixes: 2b6a3f857550 ("arm64: dts: rockchip: Fix reset-gpios property on brcm BT nodes")
Signed-off-by: Diederik de Haas <didi.debian@cknow.org>
Link: https://lore.kernel.org/r/20241018145053.11928-2-didi.debian@cknow.org
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions