linux-kernel - Re: [PATCH] arm64: dts: ti: k3-j722s-evm: Fix USB gpio-hog level for Type-C

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: <175205778774.925763.11396013784655604242.b4-ty@ti.com>
Date: Wed, 9 Jul 2025 16:13:22 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <nm@...com>, <kristo@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
        <conor+dt@...nel.org>, <rogerq@...nel.org>,
        Siddharth Vadapalli
	<s-vadapalli@...com>
CC: Vignesh Raghavendra <vigneshr@...com>, <stable@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <srk@...com>
Subject: Re: [PATCH] arm64: dts: ti: k3-j722s-evm: Fix USB gpio-hog level for Type-C

Hi Siddharth Vadapalli,

On Mon, 23 Jun 2025 15:36:57 +0530, Siddharth Vadapalli wrote:
> According to the "GPIO Expander Map / Table" section of the J722S EVM
> Schematic within the Evaluation Module Design Files package [0], the
> GPIO Pin P05 located on the GPIO Expander 1 (I2C0/0x23) has to be pulled
> down to select the Type-C interface. Since commit under Fixes claims to
> enable the Type-C interface, update the property within "p05-hog" from
> "output-high" to "output-low", thereby switching from the Type-A
> interface to the Type-C interface.
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/1] arm64: dts: ti: k3-j722s-evm: Fix USB gpio-hog level for Type-C
      commit: 65ba2a6e77e9e5c843a591055789050e77b5c65e

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh