linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: ARM-SoC Maintainers <arm@kernel.org>, SoC Team <soc@kernel.org>,
	 Linus Walleij <linus.walleij@linaro.org>,
	 Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
	Phil Elwell <phil@raspberrypi.com>,
	 Florian Fainelli <f.fainelli@gmail.com>,
	Jan Kiszka <jan.kiszka@web.de>,
	 Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] ARM: dts: gpio-ranges property is now required
Date: Sat, 8 Jan 2022 13:18:43 -0800	[thread overview]
Message-ID: <CAOesGMjQavd+2eupBE40BfhBwVq4_K493Kn0uzsCi9DoPHB19A@mail.gmail.com> (raw)
In-Reply-To: <07f6beef-8824-e995-577e-3c705ed7d40f@i2se.com>

On Sat, Jan 8, 2022 at 1:04 PM Stefan Wahren <stefan.wahren@i2se.com> wrote:
>
> Hi Olof,
>
> Am 04.01.22 um 18:02 schrieb Linus Walleij:
> > From: Phil Elwell <phil@raspberrypi.com>
> >
> > Since [1], added in 5.7, the absence of a gpio-ranges property has
> > prevented GPIOs from being restored to inputs when released.
> > Add those properties for BCM283x and BCM2711 devices.
> >
> > [1] commit 2ab73c6d8323 ("gpio: Support GPIO controllers without
> >     pin-ranges")
> >
> > Fixes: 2ab73c6d8323 ("gpio: Support GPIO controllers without pin-ranges")
> > Fixes: 266423e60ea1 ("pinctrl: bcm2835: Change init order for gpio hogs")
> > Reported-by: Stefan Wahren <stefan.wahren@i2se.com>
> > Reported-by: Florian Fainelli <f.fainelli@gmail.com>
> > Reported-by: Jan Kiszka <jan.kiszka@web.de>
> > Signed-off-by: Phil Elwell <phil@raspberrypi.com>
> > Acked-by: Florian Fainelli <f.fainelli@gmail.com>
> > Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> > Link: https://lore.kernel.org/r/20211206092237.4105895-3-phil@raspberrypi.com
> > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> > ---
> > Hi SoC maintainers, please apply this directly for fixes, the
> > missing patch is wreacking havoc in the RPi world.
>
> this patch has been send to soc@kernel.org in order to fix a regression
> [1] caused by "pinctrl: bcm2835: Change init order for gpio hog". Would
> be great to get it into 5.16
>
> [1] -
> https://lore.kernel.org/all/ec60b52b-7a59-266d-9608-11c0da9053a6@i2se.com/

Yeah, my bad -- I only scanned for pull requests and missed this
patch. I'll send it up. Linus just merged the pull request I sent so
I'll do an incremental one.

-Olof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2022-01-08 21:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 17:02 [PATCH] ARM: dts: gpio-ranges property is now required Linus Walleij
2022-01-04 21:57 ` Florian Fainelli
2022-01-08 21:04 ` Stefan Wahren
2022-01-08 21:18   ` Olof Johansson [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=CAOesGMjQavd+2eupBE40BfhBwVq4_K493Kn0uzsCi9DoPHB19A@mail.gmail.com \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=jan.kiszka@web.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=phil@raspberrypi.com \
    --cc=soc@kernel.org \
    --cc=stefan.wahren@i2se.com \
    --cc=torvalds@linux-foundation.org \
    /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).