diff options
| author | Diederik de Haas <didi.debian@cknow.org> | 2024-10-08 13:15:39 +0200 |
|---|---|---|
| committer | Heiko Stuebner <heiko@sntech.de> | 2024-10-08 21:17:23 +0200 |
| commit | 2b6a3f857550e52b1cd4872ebb13cb3e3cf12f5f (patch) | |
| tree | 1b86a77035f8d2ce6a1801688762eb7debc80f61 /tools/perf/scripts/python | |
| parent | 87299d6ee95a37d2d576dd8077ea6860f77ad8e2 (diff) | |
arm64: dts: rockchip: Fix reset-gpios property on brcm BT nodes
For most compatibles, the "brcm,bluetooth.yaml" binding doesn't allow
the 'reset-gpios' property, but there is a 'shutdown-gpios' property.
Page 12 of the AzureWave-CM256SM datasheet (v1.9) has the following wrt
pin 34 'BT_REG_ON' (connected to GPIO0_C4_d on the PineNote):
Used by PMU to power up or power down the internal regulators used
by the Bluetooth section. Also, when deasserted, this pin holds the
Bluetooth section in reset. This pin has an internal 200k ohm pull
down resistor that is enabled by default.
So it is safe to replace 'reset-gpios' with 'shutdown-gpios'.
Fixes: d449121e5e8a ("arm64: dts: rockchip: Add Pine64 PineNote board")
Signed-off-by: Diederik de Haas <didi.debian@cknow.org>
Link: https://lore.kernel.org/r/20241008113344.23957-5-didi.debian@cknow.org
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions