All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Prathamesh Shete <pshete@nvidia.com>,
	jonathanh@nvidia.com, linus.walleij@linaro.org,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-gpio@vger.kernel.org, smangipudi@nvidia.com
Subject: Re: [PATCH 3/3] arm64: tegra: Add Tegra234 pinmux device
Date: Wed, 8 Feb 2023 12:00:06 +0100	[thread overview]
Message-ID: <Y+OAthBgds9InvKp@orome> (raw)
In-Reply-To: <f0d58e5b-74df-26cf-592e-302a00d08eee@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]

On Tue, Feb 07, 2023 at 04:33:42PM +0100, Krzysztof Kozlowski wrote:
> On 07/02/2023 12:56, Prathamesh Shete wrote:
> > This change adds pinmux node for Tegra234.
> > 
> > Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
> > ---
> >  arch/arm64/boot/dts/nvidia/tegra234.dtsi | 14 ++++++++++++++
> >  1 file changed, 14 insertions(+)
> > 
> > diff --git a/arch/arm64/boot/dts/nvidia/tegra234.dtsi b/arch/arm64/boot/dts/nvidia/tegra234.dtsi
> > index eaf05ee9acd1..c91b88bc56d1 100644
> > --- a/arch/arm64/boot/dts/nvidia/tegra234.dtsi
> > +++ b/arch/arm64/boot/dts/nvidia/tegra234.dtsi
> > @@ -701,6 +701,13 @@
> >  			interrupt-controller;
> >  			#gpio-cells = <2>;
> >  			gpio-controller;
> > +			gpio-ranges = <&pinmux 0 0 164>;
> > +		};
> > +
> > +		pinmux: pinmux@2430000 {
> > +			compatible = "nvidia,tegra234-pinmux";
> > +			reg = <0x2430000 0x19100>;
> > +			status = "okay";
> 
> Why? Anything disabled it?
> 
> >  		};
> >  
> >  		mc: memory-controller@2c00000 {
> > @@ -1664,6 +1671,13 @@
> >  			interrupt-controller;
> >  			#gpio-cells = <2>;
> >  			gpio-controller;
> > +			gpio-range = <&pinmux_aon 0 0 32>;
> > +		};
> > +
> > +		pinmux_aon: pinmux@c300000 {
> > +			compatible = "nvidia,tegra234-pinmux-aon";
> > +			reg = <0xc300000 0x4000>;
> > +			status = "okay";
> 
> Also why?

These are probably copy-pasted from Tegra194 where these snuck in. I can
drop those when applying. I'll also prepare a patch to drop these from
the tegra194.dtsi.

I wonder if there's a good way to detect these. We'd have to run checks
on the DT source files, so that's a bit difficult. I do have an
experimental script that tries to capture some common pitfalls on
sources but it's quite ugly and slow, but I guess I could add something
like this. But perhaps there are better ways?

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-02-08 11:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 11:56 [PATCH 1/3] dt-bindings: pinctrl: tegra234: Add DT binding doc Prathamesh Shete
2023-02-07 11:56 ` [PATCH 2/3] pinctrl: tegra: Add Tegra234 pinmux driver Prathamesh Shete
2023-02-07 11:56 ` [PATCH 3/3] arm64: tegra: Add Tegra234 pinmux device Prathamesh Shete
2023-02-07 15:33   ` Krzysztof Kozlowski
2023-02-08 11:00     ` Thierry Reding [this message]
2023-02-08 12:01       ` Krzysztof Kozlowski
2023-02-08 12:06         ` Krzysztof Kozlowski
2023-02-08 15:46           ` Thierry Reding
2023-02-07 14:37 ` [PATCH 1/3] dt-bindings: pinctrl: tegra234: Add DT binding doc Rob Herring
2023-02-08 11:29   ` Thierry Reding
2023-02-07 15:33 ` Krzysztof Kozlowski
2023-02-08 11:24   ` Thierry Reding
2023-02-08 11:57     ` Krzysztof Kozlowski
2023-03-08 11:45       ` Prathamesh Shete
2023-03-08 12:24         ` Krzysztof Kozlowski
2023-03-23 14:11           ` Thierry Reding
2023-03-26 12:19             ` Krzysztof Kozlowski
2023-03-28 12:39               ` Thierry Reding
2023-03-30 13:58                 ` Krzysztof Kozlowski
2023-03-30 16:32                   ` Thierry Reding
2023-04-20 17:06                     ` Thierry Reding
2023-04-20 17:16                       ` Krzysztof Kozlowski

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=Y+OAthBgds9InvKp@orome \
    --to=thierry.reding@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@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=smangipudi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.