[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <167395338059.410173.2860390217539466023.b4-ty@ti.com>
Date: Tue, 17 Jan 2023 19:04:43 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Sjoerd Simons <sjoerd@...labora.com>, Nishanth Menon <nm@...com>
CC: Vignesh Raghavendra <vigneshr@...com>,
Rob Herring <robh+dt@...nel.org>, <martyn.welch@...labora.com>,
<devicetree@...r.kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Nitin Yadav <n-yadav@...com>, Tero Kristo <kristo@...nel.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <kernel@...labora.com>
Subject: Re: [PATCH v4 0/3] Improve K3-am625-sk support (USB, MMC)
Hi Sjoerd Simons,
On Thu, 12 Jan 2023 17:28:43 +0100, Sjoerd Simons wrote:
> This series picks up a few patches from the TI BSP tree that
> unfortunately didn't make it upstream thusfar.
>
> The first patch improve SD card compatibility (allowing U1 class cards
> to be used), the remaining ones add USB support.
>
> The type-c connector isn't entirely modelled with these changes as
> it goes through a TPS6598 PD controller. Unfortunately the dtb bindings
> for that currently require an irq line, which is not connected on E1 and
> E2 version boards. The patchese to support this setup unfortunately didn't land
> yet[0].. As such the last patch ignored the PD controller and simply
> configures usb0 as periphal only rather then mode switch capable, which
> at least gives some basic usability of that USB port.
>
> [...]
I have applied the following to branch ti-k3-next on [1].
Thank you!
[1/3] arm64: dts: ti: k3-am62-main: Update OTAP and ITAP delay select
commit: bd2912f400934d71ecb040f625685b886ccdcc20
[2/3] arm64: dts: ti: k3-am62-main: Add support for USB
commit: 2240f96cf3cd0f74f5c349fb212c4176627f69b0
[3/3] arm64: dts: ti: k3-am625-sk: Add support for USB
commit: 2d94dfc438853dca9b390a3f32fe5331c336fd28
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
Powered by blists - more mailing lists