public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-gpio@vger.kernel.org, linux-tegra@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Jon Hunter <jonathanh@nvidia.com>,
	devicetree@vger.kernel.org, Prathamesh Shete <pshete@nvidia.com>,
	Vidya Sagar <vidyas@nvidia.com>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v3 2/4] dt-bindings: pinctrl: tegra194: Separate instances
Date: Mon, 7 Nov 2022 14:50:17 -0600	[thread overview]
Message-ID: <166785421422.1609632.2807084957651673122.robh@kernel.org> (raw)
In-Reply-To: <20221104142345.1562750-3-thierry.reding@gmail.com>


On Fri, 04 Nov 2022 15:23:43 +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> Tegra194 has two separate instances of the pin controller, one called
> AON (in the always-on domain) and another called "main". Instead of
> treating them as a single pin controller, split them up into two
> separate controllers. Doing so allows the mapping between the pinmux and
> GPIO controllers to be trivial identity mappings and more cleanly
> separates the AON from the main IP blocks.
> 
> 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.
> 
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> Changes in v3:
> - update for common bindings restructure
> 
> Changes in v2:
> - add missing "type: object" to patternProperties nodes
> - add note about backwards-compatibility
> 
>  .../pinctrl/nvidia,tegra194-pinmux.yaml       | 235 ++++++++++++++++--
>  1 file changed, 215 insertions(+), 20 deletions(-)
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2022-11-07 20:50 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 [this message]
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
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=166785421422.1609632.2807084957651673122.robh@kernel.org \
    --to=robh@kernel.org \
    --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=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