linux-kernel - Re: [PATCH] pinctrl: Support pin that does not support configuration option

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] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 12 Feb 2021 09:26:09 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Michael Nazzareno Trimarchi <michael@...rulasolutions.com>
Cc:     Fabio Estevam <festevam@...il.com>,
        Dong Aisheng <aisheng.dong@....com>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Angelo Compagnucci <angelo@...rulasolutions.com>
Subject: Re: [PATCH] pinctrl: Support pin that does not support configuration option

On Mon, Feb 1, 2021 at 12:54 PM Michael Nazzareno Trimarchi
<michael@...rulasolutions.com> wrote:
> On Mon, Feb 1, 2021 at 12:47 PM Fabio Estevam <festevam@...il.com> wrote:
> >
> > Hi Michael,
> >
> > On Sat, Jan 30, 2021 at 5:21 AM Michael Trimarchi
> > <michael@...rulasolutions.com> wrote:
> > >
> > > Some of the iMX25 pins have not an associated configuration register so
> > > when they are configured the standard way through the device tree the
> > > kernel complains with:
> > >
> > > imx25-pinctrl 43fac000.iomuxc: Pin(MX25_PAD_EXT_ARMCLK) does not support
> > > config function
> >
> > Could you please share your device tree that causes this warning?
> >
> > Shouldn't you pass 0x80000000 in the devicetree for this pad then?
> >
> > 0x80000000 means that the kernel should not touch the PAD_CTL register
> > and use the default configuration from the bootloader/POR.
>
> arch/arm/boot/dts/imx25-lisa.dts:
> MX25_PAD_EXT_ARMCLK__GPIO_3_15  0x80000000
>
> The problem that exists pad that can be muxed but not configured

Did you reach any conclusion on this?

I need Fabio's consent to apply the patch, but it seems maybe the
DTS should be changed instead?

Yours,
Linus Walleij