public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Martin Schiller <ms@dev.tdt.de>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpiolib: of: fix lookup quirk for MIPS Lantiq
Date: Mon, 1 Jul 2024 10:35:06 -0700	[thread overview]
Message-ID: <ZoLoyjBa6xY85YBv@google.com> (raw)
In-Reply-To: <CAMRc=McMn6k7QMXLHphNS03BtO=i9xKBwxa71MeVXhtNSFdiXA@mail.gmail.com>

On Mon, Jul 01, 2024 at 10:51:00AM +0200, Bartosz Golaszewski wrote:
> On Fri, Jun 28, 2024 at 8:35 PM Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> >
> > As it turns out, there is a large number of out-of-tree DTSes (in
> > OpenWrt project) that used to specify incorrect (active high) polarity
> > for the Lantiq reset GPIO, so to keep compatibility while they are
> > being updated a quirk for force the polarity low is needed. Luckily
> > these old DTSes used nonstandard name for the property ("gpio-reset" vs
> > "reset-gpios") so the quirk will not hurt if there are any new devices
> > that need inverted polarity as they can specify the right polarity in
> > their DTS when using the standard "reset-gpios" property.
> >
> > Additionally the condition to enable the translation from standard to
> > non-standard reset GPIO property name was inverted and the replacement
> > name for the property was not correct. Fix this as well.
> >
> > Fixes: fbbbcd177a27 ("gpiolib: of: add quirk for locating reset lines with legacy bindings")
> > Fixes: 90c2d2eb7ab5 ("MIPS: pci: lantiq: switch to using gpiod API")
> > Reported-by: Martin Schiller <ms@dev.tdt.de>
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > ---
> >  drivers/gpio/gpiolib-of.c | 14 ++++++++++++--
> >  1 file changed, 12 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.c
> > index 59c7f8a2431a..d21085830632 100644
> > --- a/drivers/gpio/gpiolib-of.c
> > +++ b/drivers/gpio/gpiolib-of.c
> > @@ -203,6 +203,16 @@ static void of_gpio_try_fixup_polarity(const struct device_node *np,
> >                  */
> >                 { "qi,lb60",            "rb-gpios",     true },
> >  #endif
> > +#if IS_ENABLED(CONFIG_PCI_LANTIQ)
> > +               /*
> > +                * According to the PCI specification, the RST# pin is an
> > +                * active-low signal. However, most of the device trees that
> > +                * have been widely used for a long time incorrectly describe
> > +                * reset GPIO as active-high, and were also using wrong name
> > +                * for the property.
> > +                */
> > +               { "lantiq,pci-xway",    "gpio-reset",   false },
> > +#endif
> >  #if IS_ENABLED(CONFIG_TOUCHSCREEN_TSC2005)
> >                 /*
> >                  * DTS for Nokia N900 incorrectly specified "active high"
> > @@ -512,9 +522,9 @@ static struct gpio_desc *of_find_gpio_rename(struct device_node *np,
> >                 { "reset",      "reset-n-io",   "marvell,nfc-uart" },
> >                 { "reset",      "reset-n-io",   "mrvl,nfc-uart" },
> >  #endif
> > -#if !IS_ENABLED(CONFIG_PCI_LANTIQ)
> > +#if IS_ENABLED(CONFIG_PCI_LANTIQ)
> >                 /* MIPS Lantiq PCI */
> > -               { "reset",      "gpios-reset",  "lantiq,pci-xway" },
> > +               { "reset",      "gpio-reset",   "lantiq,pci-xway" },
> >  #endif
> >
> >                 /*
> > --
> > 2.45.2.803.g4e1b14247a-goog
> >
> >
> > --
> > Dmitry
> 
> Can you rebase it on top of v6.10-rc6? It doesn't apply to my fixes branch.

Ah, yes, I had another quirk to TSC2005 in my tree that gave the
conflict.

Thanks.

-- 
Dmitry

      reply	other threads:[~2024-07-01 17:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 18:35 [PATCH] gpiolib: of: fix lookup quirk for MIPS Lantiq Dmitry Torokhov
2024-07-01  6:12 ` Martin Schiller
2024-07-01  8:51 ` Bartosz Golaszewski
2024-07-01 17:35   ` Dmitry Torokhov [this message]

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=ZoLoyjBa6xY85YBv@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=brgl@bgdev.pl \
    --cc=hauke@hauke-m.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ms@dev.tdt.de \
    --cc=tsbogend@alpha.franken.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