[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALHNRZ8ndcd3mvGP+W2DVFcm65t4Ai4epNeGigPv=Oo8Cf3LkQ@mail.gmail.com>
Date: Tue, 29 Apr 2025 16:38:36 -0500
From: Aaron Kling <webgeek1234@...il.com>
To: webgeek1234@...il.com
Cc: Linus Walleij <linus.walleij@...aro.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Thierry Reding <thierry.reding@...il.com>, Jonathan Hunter <jonathanh@...dia.com>,
Bartosz Golaszewski <brgl@...ev.pl>, linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] pinctrl: tegra: Add Tegra186 pinmux driver
On Tue, Apr 29, 2025 at 4:33 PM Aaron Kling via B4 Relay
<devnull+webgeek1234.gmail.com@...nel.org> wrote:
>
> This series adds support for Tegra186 pin control, based on a downstream
> driver, updated to match the existing Tegra194 driver.
>
> Signed-off-by: Aaron Kling <webgeek1234@...il.com>
> ---
> Aaron Kling (4):
> dt-bindings: pinctrl: Document Tegra186 pin controllers
> dt-bindings: gpio: tegra186: Add gpio-ranges
> pinctrl: tegra: Add Tegra186 pinmux driver
> arm64: tegra: Add Tegra186 pin controllers
>
> .../bindings/gpio/nvidia,tegra186-gpio.yaml | 3 +
> .../bindings/pinctrl/nvidia,tegra186-pinmux.yaml | 285 ++++
> arch/arm64/boot/dts/nvidia/tegra186.dtsi | 12 +
> drivers/pinctrl/tegra/Kconfig | 4 +
> drivers/pinctrl/tegra/Makefile | 1 +
> drivers/pinctrl/tegra/pinctrl-tegra186.c | 1784 ++++++++++++++++++++
> drivers/soc/tegra/Kconfig | 1 +
> 7 files changed, 2090 insertions(+)
> ---
> base-commit: 1110ce6a1e34fe1fdc1bfe4ad52405f327d5083b
> change-id: 20250308-tegra186-pinctrl-651ffbbbe816
>
> Best regards,
> --
> Aaron Kling <webgeek1234@...il.com>
>
>
Thierry and Jonathan, as the maintainers for the other tegra pinmux
drivers, I listed you as the maintainers for this one in the dt
bindings. And I think MAINTAINERS will do that by default for the
driver itself. Are you okay with taking over ongoing maintenance for
this one once it is approved for merge? I made it match the others as
closely as possible, so it shouldn't need any additional changes over
time that the others don't. But I don't want to sign anyone up for
work without prior approval.
Sincerely,
Aaron
Powered by blists - more mailing lists