From: Florian Fainelli <f.fainelli@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
arm@kernel.org, soc@kernel.org,
Nicolas Saenz Julienne <nsaenz@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Phil Elwell <phil@raspberrypi.com>,
Stefan Wahren <stefan.wahren@i2se.com>,
Jan Kiszka <jan.kiszka@web.de>
Subject: Re: [PATCH] ARM: dts: gpio-ranges property is now required
Date: Tue, 4 Jan 2022 13:57:30 -0800 [thread overview]
Message-ID: <6f42ceda-c000-7506-65ec-53534b5aef7d@gmail.com> (raw)
In-Reply-To: <20220104170247.956760-1-linus.walleij@linaro.org>
On 1/4/22 9:02 AM, Linus Walleij wrote:
> 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.
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
Now that "pinctrl: bcm2835: Change init order for gpio hogs" is in
Linus' master this patch can go in... what a mess, let's not do this again.
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-01-04 21:59 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 [this message]
2022-01-08 21:04 ` Stefan Wahren
2022-01-08 21:18 ` Olof Johansson
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=6f42ceda-c000-7506-65ec-53534b5aef7d@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arm@kernel.org \
--cc=jan.kiszka@web.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nsaenz@kernel.org \
--cc=phil@raspberrypi.com \
--cc=soc@kernel.org \
--cc=stefan.wahren@i2se.com \
/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).