diff options
| author | Lorenz Brun <[email protected]> | 2023-04-21 21:38:41 +0000 |
|---|---|---|
| committer | Heiko Stuebner <[email protected]> | 2023-05-07 21:46:47 +0000 |
| commit | 03633c4ef1fb5ee119296dfe0c411656a9b5e04f (patch) | |
| tree | b3c7cfeeacb205e6570ecb89c1a730023e0d7999 /net/unix/af_unix.c | |
| parent | Linux 6.4-rc1 (diff) | |
| download | kernel-03633c4ef1fb5ee119296dfe0c411656a9b5e04f.tar.gz kernel-03633c4ef1fb5ee119296dfe0c411656a9b5e04f.zip | |
arm64: dts: rockchip: fix USB regulator on ROCK64
Currently the ROCK64 device tree specifies two regulators, vcc_host_5v
and vcc_host1_5v for USB VBUS on the device. Both of those are however
specified with RK_PA2 as the GPIO enabling them, causing the following
error when booting:
rockchip-pinctrl pinctrl: pin gpio0-2 already requested by vcc-host-5v-regulator; cannot claim for vcc-host1-5v-regulator
rockchip-pinctrl pinctrl: pin-2 (vcc-host1-5v-regulator) status -22
rockchip-pinctrl pinctrl: could not request pin 2 (gpio0-2) from group usb20-host-drv on device rockchip-pinctrl
reg-fixed-voltage vcc-host1-5v-regulator: Error applying setting, reverse things back
Looking at the schematic, there are in fact three USB regulators,
vcc_host_5v, vcc_host1_5v and vcc_otg_v5. But the enable signal for all
three is driven by Q2604 which is in turn driven by GPIO_A2/PA2.
Since these three regulators are not controllable separately, I removed
the second one which was causing the error and added labels for all
rails to the single regulator.
Signed-off-by: Lorenz Brun <[email protected]>
Tested-by: Diederik de Haas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Heiko Stuebner <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions