linux-kernel - Re: [PATCH] ARM: lpc3250: fix uda1380 gpio numbers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAK8P3a0q+UM_7wY_rdbkJOzLfoS4HYCXSXodpqtHHY=h-7_mpQ@mail.gmail.com>
Date:   Mon, 15 Jan 2018 13:57:58 +0100
From:   Arnd Bergmann <arnd@...db.de>
To:     Vladimir Zapolskiy <vz@...ia.com>,
        Sylvain Lemieux <slemieux.tyco@...il.com>
Cc:     Arnd Bergmann <arnd@...db.de>, Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        DTML <devicetree@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ARM: lpc3250: fix uda1380 gpio numbers

On Wed, Jan 10, 2018 at 5:22 PM, Arnd Bergmann <arnd@...db.de> wrote:
> 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@...A0000/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@...A0000/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@...A0000/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@...A0000/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.
>
> Link: https://unix.stackexchange.com/questions/59497/alsa-asoc-how-to-correctly-load-devices-drivers/62217#62217
> Signed-off-by: Arnd Bergmann <arnd@...db.de>

I've applied this to the next/dt branch now.

       Arnd