On Fri, Aug 1, 2025 at 4:43 AM Thierry Reding [off-list ref] wrote:

On Thu, Jul 31, 2025 at 04:36:17PM -0500, Aaron Kling wrote:

quoted

On Mon, Jul 14, 2025 at 12:35 AM Aaron Kling [off-list ref] wrote:

quoted

On Mon, Jun 30, 2025 at 2:27 PM Aaron Kling [off-list ref] wrote:

quoted

On Wed, May 28, 2025 at 12:42 PM Aaron Kling [off-list ref] wrote:

quoted

On Tue, May 13, 2025 at 4:10 PM Aaron Kling via B4 Relay
[off-list ref] wrote:

quoted

From: Aaron Kling <redacted>

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 <redacted>
---
 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 [off-list ref]

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