From: Florian Fainelli <f.fainelli@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Phil Elwell <phil@raspberrypi.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
Thierry Reding <treding@nvidia.com>,
devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 2/2] ARM: dts: gpio-ranges property is now required
Date: Mon, 6 Dec 2021 09:24:59 -0800 [thread overview]
Message-ID: <04acf5f1-7d82-b12b-f70f-1712a4a2610c@gmail.com> (raw)
In-Reply-To: <CACRpkdYJAZcr_PPCGPYcitfcwd9GDFf+7hPJkOmjomqCrruNfw@mail.gmail.com>
On 12/6/21 2:33 AM, Linus Walleij wrote:
> On Mon, Dec 6, 2021 at 10:22 AM Phil Elwell <phil@raspberrypi.com> wrote:
>
>> 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")
>> Signed-off-by: Phil Elwell <phil@raspberrypi.com>
>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> Please funnel this patch through the SoC tree.
This one was definitively going to go via ARM SoC in the absence of any
explicit routing, did you mean that patch #1 should also be routed via
ARM SoC?
--
Florian
next prev parent reply other threads:[~2021-12-06 17:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 9:22 [PATCH v2 0/2] pinctrl: bcm2835: Fix gpio hogs and pin reinitialisation Phil Elwell
2021-12-06 9:22 ` [PATCH v2 1/2] pinctrl: bcm2835: Change init order for gpio hogs Phil Elwell
2021-12-07 18:32 ` Florian Fainelli
2021-12-09 23:24 ` Linus Walleij
2021-12-29 19:07 ` Stefan Wahren
2021-12-29 21:11 ` Florian Fainelli
2022-01-02 6:54 ` Linus Walleij
2022-01-02 11:02 ` Jan Kiszka
2022-01-02 12:33 ` Stefan Wahren
2022-01-02 15:12 ` Jan Kiszka
2022-01-02 15:16 ` Jan Kiszka
2022-01-04 17:04 ` Linus Walleij
2021-12-06 9:22 ` [PATCH v2 2/2] ARM: dts: gpio-ranges property is now required Phil Elwell
2021-12-06 10:33 ` Linus Walleij
2021-12-06 17:24 ` Florian Fainelli [this message]
2021-12-07 15:29 ` Linus Walleij
2021-12-10 11:12 ` nicolas saenz julienne
[not found] ` <CGME20211214142139eucas1p1c100b7fd4b8c8ce85bc03e1ce6b783db@eucas1p1.samsung.com>
2021-12-14 14:21 ` Marek Szyprowski
2021-12-14 14:32 ` Phil Elwell
2021-12-14 17:12 ` Florian Fainelli
2021-12-15 9:02 ` nicolas saenz julienne
2021-12-15 17:14 ` Florian Fainelli
2021-12-16 3:27 ` Linus Walleij
2021-12-16 3:28 ` Florian Fainelli
2021-12-16 3:31 ` Linus Walleij
2021-12-16 8:28 ` nicolas saenz julienne
2021-12-15 17:15 ` Florian Fainelli
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=04acf5f1-7d82-b12b-f70f-1712a4a2610c@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenz@kernel.org \
--cc=phil@raspberrypi.com \
--cc=robh+dt@kernel.org \
--cc=treding@nvidia.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).