From: Thierry Reding <thierry.reding@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
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 0/4] pinctrl: tegra: Separate Tegra194 instances
Date: Fri, 11 Nov 2022 16:19:30 +0100 [thread overview]
Message-ID: <Y25oAmZMcfBOCat3@orome> (raw)
In-Reply-To: <CACRpkdYT0X09bWYg9za8x+3YkcbVmBm8Prb0Fyk2nfi_eanDyw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2914 bytes --]
On Tue, Nov 08, 2022 at 03:10:01PM +0100, Linus Walleij wrote:
> On Fri, Nov 4, 2022 at 3:23 PM Thierry Reding <thierry.reding@gmail.com> wrote:
>
> > From: Thierry Reding <treding@nvidia.com>
> >
> > This patch series changes the pin controller DT description on Tegra194
> > in order to properly describe how the hardware works. Currently a
> > simplified description is used that merges two pin controller instances
> > (called AON and main) into a single DT node. This has some disadvantages
> > such as creating a complicated mapping between the pins in those pin
> > controllers and the corresponding GPIO controllers (which are already
> > separated).
> >
> > As a prerequisite, the first patch in this series converts the device
> > tree bindings to json-schema. A second patch then adds an additional
> > compatible string for the AON instance (along with more details about
> > each controller's pins) and finally patch 3 converts the driver to
> > cope with these changes. A fourth patch makes the corresponding
> > changes in the Tegra194 DTS file.
> >
> > Note that while this changes the DT node in an incompatible way, this
> > doesn't have any practical implications for backwards-compatibility. The
> > reason for this is that device trees have only reconfigured a very
> > narrow subset of pins of the main controller, so the new driver will
> > remain backwards-compatible with old device trees.
> >
> > Changes in v3:
> > - address more review comments by Rob Herring and make validation work
>
> This looks good to me!
>
> I tried to apply them to the pinctrl devel branch but this happens:
>
> $ git am --signoff
> ./v3_20221104_thierry_reding_pinctrl_tegra_separate_tegra194_instances.mbx
> Applying: dt-bindings: pinctrl: tegra: Convert to json-schema
> error: Documentation/devicetree/bindings/clock/nvidia,tegra124-dfll.yaml:
> does not exist in index
> Patch failed at 0001 dt-bindings: pinctrl: tegra: Convert to json-schema
>
> I guess there are some prerequisites?
Yeah, I noticed the same thing as I was just testing to cherry-pick just
the first three patches to a vanilla upstream branch. So yes, that pre-
requisite is another json-schema conversion that I have in my tree but
which hasn't been merged yet.
The good news is that my testing confirms what I recollect about the DT
backwards-compatibility not being an issue. In practice the only pins
from this that are being used are in the first controller, so if we
change the driver to only take control of one of them, the second will
be ignored and that's really a no-op.
What that also implies is that the pinctrl driver patch is completely
standalone, so you can apply that whenever you want and I can apply the
DT patch to the Tegra tree. I can then also pick up the DT bindings
patches and resolve the conflict there. That is, if you don't mind.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-11 15:20 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
2022-11-08 14:10 ` [PATCH v3 0/4] pinctrl: tegra: Separate Tegra194 instances Linus Walleij
2022-11-11 15:19 ` Thierry Reding [this message]
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=Y25oAmZMcfBOCat3@orome \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pshete@nvidia.com \
--cc=robh+dt@kernel.org \
--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).