All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: pshete@nvidia.com, linusw@kernel.org, thierry.reding@kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org
Cc: webgeek1234@gmail.com, rosenp@gmail.com,
	linux-tegra@vger.kernel.org, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] Add Tegra238 and Tegra264 pinctrl support
Date: Wed, 29 Apr 2026 10:38:52 +0100	[thread overview]
Message-ID: <e134911f-e4cc-41ab-be41-0c559790acde@nvidia.com> (raw)
In-Reply-To: <20260427134231.531222-1-pshete@nvidia.com>


On 27/04/2026 14:42, pshete@nvidia.com wrote:
> From: Prathamesh Shete <pshete@nvidia.com>
> 
> Add pinctrl driver support for Tegra238 and Tegra264 along with the
> corresponding device tree binding documentation. Additionally, export
> tegra_pinctrl_probe() to allow the drivers to be built as loadable modules.
> 
> Changes in v3:
>    - Wrap commit message to 75 chars per line (v2 was too short).
> Changes in v2:
>    - Drop the "arm64: defconfig: make Tegra238 and Tegra264 Pinctrl ..."
>      patch and instead add 'default m if ARCH_TEGRA_{238,264}_SOC' to
>      the PINCTRL_TEGRA238 / PINCTRL_TEGRA264 Kconfig entries so the
>      drivers are auto-enabled as modules.
>    - New patch "arm64: tegra: Add pinctrl nodes for Tegra264" that
>      describes the three Tegra264 pin controllers (pinmux_main,
>      pinmux_aon, pinmux_uphy) in tegra264.dtsi.
>    - dt-bindings (Tegra238 and Tegra264 pinmux):
>       * Add 'required: compatible, reg' to the top-level schemas.
>       * Switch 'unevaluatedProperties: false' to
>         'additionalProperties: false' on the top-level schemas.
>    - Reword commit messages to use imperative mood.
> 
> Link to v1:
> https://lore.kernel.org/linux-tegra/20260409131340.168556-1-pshete@nvidia.com/
> 
> 
> Prathamesh Shete (6):
>    pinctrl: tegra: Export tegra_pinctrl_probe()
>    dt-bindings: pinctrl: Document Tegra238 pin controllers
>    pinctrl: tegra: Add Tegra238 pinmux driver
>    dt-bindings: pinctrl: Document Tegra264 pin controllers
>    pinctrl: tegra: Add Tegra264 pinmux driver
>    arm64: tegra: Add pinctrl nodes for Tegra264
> 
>   .../pinctrl/nvidia,tegra238-pinmux-aon.yaml   |   82 +
>   .../nvidia,tegra238-pinmux-common.yaml        |   73 +
>   .../pinctrl/nvidia,tegra238-pinmux.yaml       |  219 ++
>   .../pinctrl/nvidia,tegra264-pinmux-aon.yaml   |   80 +
>   .../nvidia,tegra264-pinmux-common.yaml        |   84 +
>   .../pinctrl/nvidia,tegra264-pinmux-main.yaml  |  167 ++
>   .../pinctrl/nvidia,tegra264-pinmux-uphy.yaml  |   78 +
>   arch/arm64/boot/dts/nvidia/tegra264.dtsi      |   15 +
>   drivers/pinctrl/tegra/Kconfig                 |   20 +
>   drivers/pinctrl/tegra/Makefile                |    2 +
>   drivers/pinctrl/tegra/pinctrl-tegra.c         |    2 +
>   drivers/pinctrl/tegra/pinctrl-tegra238.c      | 2056 +++++++++++++++
>   drivers/pinctrl/tegra/pinctrl-tegra264.c      | 2216 +++++++++++++++++
>   13 files changed, 5094 insertions(+)
>   create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra238-pinmux-aon.yaml
>   create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra238-pinmux-common.yaml
>   create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra238-pinmux.yaml
>   create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra264-pinmux-aon.yaml
>   create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra264-pinmux-common.yaml
>   create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra264-pinmux-main.yaml
>   create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra264-pinmux-uphy.yaml
>   create mode 100644 drivers/pinctrl/tegra/pinctrl-tegra238.c
>   create mode 100644 drivers/pinctrl/tegra/pinctrl-tegra264.c
> 


For the series ...

Reviewed-by: Jon Hunter <jonathanh@nvidia.com>

Thanks!
Jon

-- 
nvpublic


  parent reply	other threads:[~2026-04-29  9:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 13:42 [PATCH v3 0/6] Add Tegra238 and Tegra264 pinctrl support pshete
2026-04-27 13:42 ` [PATCH v3 1/6] pinctrl: tegra: Export tegra_pinctrl_probe() pshete
2026-04-27 13:42 ` [PATCH v3 2/6] dt-bindings: pinctrl: Document Tegra238 pin controllers pshete
2026-04-29  6:40   ` Krzysztof Kozlowski
2026-04-27 13:42 ` [PATCH v3 3/6] pinctrl: tegra: Add Tegra238 pinmux driver pshete
2026-04-27 13:42 ` [PATCH v3 4/6] dt-bindings: pinctrl: Document Tegra264 pin controllers pshete
2026-04-29  6:41   ` Krzysztof Kozlowski
2026-04-27 13:42 ` [PATCH v3 5/6] pinctrl: tegra: Add Tegra264 pinmux driver pshete
2026-04-27 13:42 ` [PATCH v3 6/6] arm64: tegra: Add pinctrl nodes for Tegra264 pshete
2026-04-28  6:10 ` [PATCH v3 0/6] Add Tegra238 and Tegra264 pinctrl support Krzysztof Kozlowski
2026-04-29  9:38 ` Jon Hunter [this message]
2026-05-14  8:17   ` Jon Hunter

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=e134911f-e4cc-41ab-be41-0c559790acde@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=pshete@nvidia.com \
    --cc=robh@kernel.org \
    --cc=rosenp@gmail.com \
    --cc=thierry.reding@kernel.org \
    --cc=webgeek1234@gmail.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.