From: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Dong Aisheng <aisheng.dong@nxp.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Angelo Compagnucci <angelo@amarulasolutions.com>
Subject: Re: [PATCH] pinctrl: Support pin that does not support configuration option
Date: Mon, 1 Feb 2021 12:53:53 +0100 [thread overview]
Message-ID: <CAOf5uwmSR1MjGdFd2ShHWchrdL6Kxo1HJOys9JoVP1vCDX57Lw@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5DyKDj_RjHM-qwcU9gcuROL6OYzDj3a_fdRRqCwOxWcdw@mail.gmail.com>
Hi Fabio
On Mon, Feb 1, 2021 at 12:47 PM Fabio Estevam <festevam@gmail.com> wrote:
>
> Hi Michael,
>
> On Sat, Jan 30, 2021 at 5:21 AM Michael Trimarchi
> <michael@amarulasolutions.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
Michael
--
Michael Nazzareno Trimarchi
Amarula Solutions BV
COO Co-Founder
Cruquiuskade 47 Amsterdam 1018 AM NL
T. +31(0)851119172
M. +39(0)3479132170
[`as] https://www.amarulasolutions.com
next prev parent reply other threads:[~2021-02-01 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 8:21 [PATCH] pinctrl: Support pin that does not support configuration option Michael Trimarchi
2021-02-01 11:47 ` Fabio Estevam
2021-02-01 11:53 ` Michael Nazzareno Trimarchi [this message]
2021-02-12 8:26 ` Linus Walleij
2021-02-12 8:31 ` Michael Nazzareno Trimarchi
2021-02-13 11:26 ` Michael Nazzareno Trimarchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOf5uwmSR1MjGdFd2ShHWchrdL6Kxo1HJOys9JoVP1vCDX57Lw@mail.gmail.com \
--to=michael@amarulasolutions.com \
--cc=aisheng.dong@nxp.com \
--cc=angelo@amarulasolutions.com \
--cc=festevam@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).