From: Linus Walleij <linus.walleij@linaro.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jon Hunter <jonathanh@nvidia.com>,
Prathamesh Shete <pshete@nvidia.com>,
Vidya Sagar <vidyas@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v3 4/4] arm64: tegra: Separate AON pinmux from main pinmux on Tegra194
Date: Tue, 8 Nov 2022 15:11:10 +0100 [thread overview]
Message-ID: <CACRpkdbegcxckaYA5h0VKQonK72srZWDZYynHhUKSTHngWGHWA@mail.gmail.com> (raw)
In-Reply-To: <20221104142345.1562750-5-thierry.reding@gmail.com>
On Fri, Nov 4, 2022 at 3:23 PM Thierry Reding <thierry.reding@gmail.com> wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The registers for the AON pinmux reside in a partition different from
> the registers for the main pinmux. Instead of treating them as one and
> the same device, split them up so that they are each their own devices.
> Also add gpio-ranges properties to the corresponding GPIO controllers
> such that the pinmux and GPIO controllers can be paired up properly.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
Is this one of those few cases where this patch should also be
applied to the pin control tree to keep things coherent for e.g.
git bisect?
Normally I would ask for this to be queued in the SoC tree separately.
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-11-08 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 14:23 [PATCH v3 0/4] pinctrl: tegra: Separate Tegra194 instances Thierry Reding
2022-11-04 14:23 ` [PATCH v3 1/4] dt-bindings: pinctrl: tegra: Convert to json-schema Thierry Reding
2022-11-07 20:48 ` Rob Herring
2022-11-04 14:23 ` [PATCH v3 2/4] dt-bindings: pinctrl: tegra194: Separate instances Thierry Reding
2022-11-07 20:50 ` Rob Herring
2022-11-04 14:23 ` [PATCH v3 3/4] pinctrl: tegra: Separate Tegra194 instances Thierry Reding
2022-11-04 14:23 ` [PATCH v3 4/4] arm64: tegra: Separate AON pinmux from main pinmux on Tegra194 Thierry Reding
2022-11-08 14:11 ` Linus Walleij [this message]
2022-11-08 14:10 ` [PATCH v3 0/4] pinctrl: tegra: Separate Tegra194 instances Linus Walleij
2022-11-11 15:19 ` Thierry Reding
2022-11-14 13:18 ` Linus Walleij
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=CACRpkdbegcxckaYA5h0VKQonK72srZWDZYynHhUKSTHngWGHWA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pshete@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vidyas@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).