linux-kernel - Re: [PATCH] arm64: tegra: Remove otg id gpio from Jetson TX2 NX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CALHNRZ9uJ9g6BGhUmBaaMM3DhQDh7mTtqKKr0A98X-5V4ompEg@mail.gmail.com>
Date: Mon, 18 Aug 2025 13:56:42 -0500
From: Aaron Kling <webgeek1234@...il.com>
To: Thierry Reding <thierry.reding@...il.com>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
	Conor Dooley <conor+dt@...nel.org>, Jonathan Hunter <jonathanh@...dia.com>, devicetree@...r.kernel.org, 
	linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: tegra: Remove otg id gpio from Jetson TX2 NX

On Fri, Aug 1, 2025 at 4:43 AM Thierry Reding <thierry.reding@...il.com> wrote:
>
> On Thu, Jul 31, 2025 at 04:36:17PM -0500, Aaron Kling wrote:
> > On Mon, Jul 14, 2025 at 12:35 AM Aaron Kling <webgeek1234@...il.com> wrote:
> > >
> > > On Mon, Jun 30, 2025 at 2:27 PM Aaron Kling <webgeek1234@...il.com> wrote:
> > > >
> > > > On Wed, May 28, 2025 at 12:42 PM Aaron Kling <webgeek1234@...il.com> wrote:
> > > > >
> > > > > On Tue, May 13, 2025 at 4:10 PM Aaron Kling via B4 Relay
> > > > > <devnull+webgeek1234.gmail.com@...nel.org> wrote:
> > > > > >
> > > > > > From: Aaron Kling <webgeek1234@...il.com>
> > > > > >
> > > > > > The p3509 carrier board does not connect the id gpio. Prior to this, the
> > > > > > gpio role switch driver could not detect the mode of the otg port.
> > > > > >
> > > > > > Signed-off-by: Aaron Kling <webgeek1234@...il.com>
> > > > > > ---
> > > > > >  arch/arm64/boot/dts/nvidia/tegra186-p3509-0000+p3636-0001.dts | 1 -
> > > > > >  1 file changed, 1 deletion(-)
> > > > > >
> > > > > > diff --git a/arch/arm64/boot/dts/nvidia/tegra186-p3509-0000+p3636-0001.dts b/arch/arm64/boot/dts/nvidia/tegra186-p3509-0000+p3636-0001.dts
> > > > > > index 26f71651933d1d8ef32bbd1645cac1820bd2e104..81f204e456409df355bbcb691ef99b0d0c9d504e 100644
> > > > > > --- a/arch/arm64/boot/dts/nvidia/tegra186-p3509-0000+p3636-0001.dts
> > > > > > +++ b/arch/arm64/boot/dts/nvidia/tegra186-p3509-0000+p3636-0001.dts
> > > > > > @@ -669,7 +669,6 @@ connector {
> > > > > >                                         vbus-gpios = <&gpio
> > > > > >                                                       TEGRA186_MAIN_GPIO(L, 4)
> > > > > >                                                       GPIO_ACTIVE_LOW>;
> > > > > > -                                       id-gpios = <&pmic 0 GPIO_ACTIVE_HIGH>;
> > > > > >                                 };
> > > > > >                         };
> > > > > >
> > > > > >
> > > > > > ---
> > > > > > base-commit: 405e6c37c89ef0df2bfc7a988820a3df22dacb1b
> > > > > > change-id: 20250513-tx2nx-role-switch-37ec55d25189
> > > > > >
> > > > > > Best regards,
> > > > > > --
> > > > > > Aaron Kling <webgeek1234@...il.com>
> > > > > >
> > > > > >
> > > > >
> > > > > Friendly reminder about this patch.
> > > >
> > > > Re-reminder about this patch.
> > >
> > > Yet another reminder about this patch. It's been over two months
> > > without a response and many other patches have been pulled in the
> > > meantime.
> >
> > Reminder yet again about this patch. It's now been two and a half
> > months without even an acknowledgement from the maintainers.
> >
> > This one is getting annoying. What does it take to get a response from
> > the tegra subsystem maintainers? Does time have to be pre-allocated by
> > the company to look at patches that aren't from @nvidia.com's? Are
> > there certain times during a development cycle? When responses happen,
> > it seems like there's a lot of activity. But then everything goes
> > silent again for months. I've not seen any pattern to it so far and
> > it's becoming extremely frustrating.
>
> Just people being busy. Nothing more, nothing less. I'll pick this up
> once the merge window closes.

If I understand correctly, the merge window closed on August 10th. And
I still haven't seen any movement on open patches. If everything
unrelated is on hold until after Tegra264 launch or something like
that, it would be nice to at least set that expectation instead of
everything being held arbitrarily in suspense.

Aaron