Commit ca32e0c4 authored by Arnd Bergmann's avatar Arnd Bergmann

ARM: lpc3250: fix uda1380 gpio numbers

dtc warns about obviously incorrect GPIO numbers for the audio codec
on both lpc32xx boards:

arch/arm/boot/dts/lpc3250-phy3250.dtb: Warning (gpios_property): reset-gpio property size (12) too small for cell size 3 in /ahb/apb/i2c@400A0000/uda1380@18
arch/arm/boot/dts/lpc3250-phy3250.dtb: Warning (gpios_property): power-gpio property size (12) too small for cell size 3 in /ahb/apb/i2c@400A0000/uda1380@18
arch/arm/boot/dts/lpc3250-ea3250.dtb: Warning (gpios_property): reset-gpio property size (12) too small for cell size 3 in /ahb/apb/i2c@400A0000/uda1380@18
arch/arm/boot/dts/lpc3250-ea3250.dtb: Warning (gpios_property): power-gpio property size (12) too small for cell size 3 in /ahb/apb/i2c@400A0000/uda1380@18

It looks like the nodes are written for a different binding that combines
the GPIO number into a single number rather than a bank/number pair.
I found the right numbers on stackexchange.com, so this patch fixes
the warning and has a reasonable chance of getting things to actually
work.

Cc: stable@vger.kernel.org
Link: https://unix.stackexchange.com/questions/59497/alsa-asoc-how-to-correctly-load-devices-drivers/62217#62217Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
parent 7ac1f59c
...@@ -156,8 +156,8 @@ &i2c1 { ...@@ -156,8 +156,8 @@ &i2c1 {
uda1380: uda1380@18 { uda1380: uda1380@18 {
compatible = "nxp,uda1380"; compatible = "nxp,uda1380";
reg = <0x18>; reg = <0x18>;
power-gpio = <&gpio 0x59 0>; power-gpio = <&gpio 3 10 0>;
reset-gpio = <&gpio 0x51 0>; reset-gpio = <&gpio 3 2 0>;
dac-clk = "wspll"; dac-clk = "wspll";
}; };
......
...@@ -81,8 +81,8 @@ &i2c1 { ...@@ -81,8 +81,8 @@ &i2c1 {
uda1380: uda1380@18 { uda1380: uda1380@18 {
compatible = "nxp,uda1380"; compatible = "nxp,uda1380";
reg = <0x18>; reg = <0x18>;
power-gpio = <&gpio 0x59 0>; power-gpio = <&gpio 3 10 0>;
reset-gpio = <&gpio 0x51 0>; reset-gpio = <&gpio 3 2 0>;
dac-clk = "wspll"; dac-clk = "wspll";
}; };
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment