public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Jon Hunter <jonathanh@nvidia.com>,
	Prathamesh Shete <pshete@nvidia.com>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH v5 0/3] pinctrl: tegra: Add Tegra234 pinmux driver
Date: Tue, 6 Jun 2023 15:07:48 +0200	[thread overview]
Message-ID: <ZH8vpP-J30qThiDp@orome> (raw)
In-Reply-To: <20230605154230.2910847-1-thierry.reding@gmail.com>

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

On Mon, Jun 05, 2023 at 05:42:27PM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> Hi,
> 
> this is an updated version of v4 of the series, which can be found here:
> 
> 	http://patchwork.ozlabs.org/project/linux-tegra/list/?series=357888
> 
> This adds the missing DT bindings example for the AON pinmux controller
> and addresses some review comments from Andy that I had previously
> missed.
> 
> Changes in v5:
> - add missing DT bindings example for AON controller
> - use generic device_get_match_data() instead of OF-specific variant
> - drop comma for of_device_id table sentinel entry
> - drop unneeded .owner initialization
> - drop redundant license text
> - add missing includes
> 
> Once accepted, patches 1 and 2 can go through the pinctrl tree and I can
> pick up patch 3 into the Tegra tree. Alternatively I can also pick up
> patch 1 into the Tegra tree to help with validation. We're not quite at
> a point yet where the Tegra DTs fully validate, so it doesn't matter
> much which way these get applied.

Linus,

I've applied patches 1 and 3 to the Tegra tree. Let me know if you'd
prefer to pick up patch 1 along with patch 2 and I can drop it.

Thanks,
Thierry

> 
> Thanks,
> Thierry
> 
> Prathamesh Shete (3):
>   dt-bindings: pinctrl: Document Tegra234 pin controllers
>   pinctrl: tegra: Add Tegra234 pinmux driver
>   arm64: tegra: Add Tegra234 pin controllers
> 
>  .../pinctrl/nvidia,tegra234-pinmux-aon.yaml   |   78 +
>  .../nvidia,tegra234-pinmux-common.yaml        |   66 +
>  .../pinctrl/nvidia,tegra234-pinmux.yaml       |  139 ++
>  arch/arm64/boot/dts/nvidia/tegra234.dtsi      |   12 +
>  drivers/pinctrl/tegra/Kconfig                 |    4 +
>  drivers/pinctrl/tegra/Makefile                |    1 +
>  drivers/pinctrl/tegra/pinctrl-tegra234.c      | 1961 +++++++++++++++++
>  drivers/soc/tegra/Kconfig                     |    1 +
>  8 files changed, 2262 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux-aon.yaml
>  create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux-common.yaml
>  create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux.yaml
>  create mode 100644 drivers/pinctrl/tegra/pinctrl-tegra234.c
> 
> -- 
> 2.40.1
> 

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

  parent reply	other threads:[~2023-06-06 13:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05 15:42 [PATCH v5 0/3] pinctrl: tegra: Add Tegra234 pinmux driver Thierry Reding
2023-06-05 15:42 ` [PATCH v5 1/3] dt-bindings: pinctrl: Document Tegra234 pin controllers Thierry Reding
2023-06-06  8:47   ` Krzysztof Kozlowski
2023-06-05 15:42 ` [PATCH v5 2/3] pinctrl: tegra: Add Tegra234 pinmux driver Thierry Reding
2023-06-05 15:48   ` Andy Shevchenko
2023-06-05 15:42 ` [PATCH v5 3/3] arm64: tegra: Add Tegra234 pin controllers Thierry Reding
2023-06-06 13:07 ` Thierry Reding [this message]
2023-06-09  7:16 ` [PATCH v5 0/3] pinctrl: tegra: Add Tegra234 pinmux driver 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=ZH8vpP-J30qThiDp@orome \
    --to=thierry.reding@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=conor+dt@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 \
    /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