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:   Mon, 1 Feb 2021 08:47:34 -0300
From:   Fabio Estevam <festevam@...il.com>
To:     Michael Trimarchi <michael@...rulasolutions.com>
Cc:     Linus Walleij <linus.walleij@...aro.org>,
        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

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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ