Message ID | 20220901141328.899100-1-vigneshr@ti.com (mailing list archive) |
---|---|
Headers | show |
Series | arm64: dts: ti: Add support for AM62A family of SoCs | expand |
On 01/09/22 19:43, Vignesh Raghavendra wrote: > This series adds basic boot support for AM62A SoCs with UART, MMC/SD and > GPIO support on AM62A SK EVM > > Bootlog: https://gist.github.com/r-vignesh/4d88f53bb0489f1675fa78f993e95d3f > Tech Ref manual: https://www.ti.com/lit/zip/spruj16 > Schematics: https://www.ti.com/lit/zip/sprr459 > Tested-By: Devarsh Thakkar <devarsht@ti.com> Boot logs: https://gist.github.com/devarsht/f7f95e77d8019bdf7ce7265a20ea64a4
Hi Vignesh Raghavendra, On Thu, 1 Sep 2022 19:43:23 +0530, Vignesh Raghavendra wrote: > This series adds basic boot support for AM62A SoCs with UART, MMC/SD and > GPIO support on AM62A SK EVM > > Bootlog: https://gist.github.com/r-vignesh/4d88f53bb0489f1675fa78f993e95d3f > Tech Ref manual: https://www.ti.com/lit/zip/spruj16 > Schematics: https://www.ti.com/lit/zip/sprr459 > > [...] I have applied the following to branch ti-k3-dts-next on [1]. Thank you! [1/5] dt-bindings: arm: ti: Rearrange IOPAD macros alphabetically commit: a3c52977419beabc5cb4d6f0b062fd4cb460e54d [2/5] dt-bindings: arm: ti: Add bindings for AM62A7 SoC commit: cad20a8de86f37d2500963b1a424f9d658d8e54a [3/5] dt-bindings: pinctrl: k3: Introduce pinmux definitions for AM62A commit: 1607e6f9289cdb4c982a223e80ff3c5e827b7cd4 [4/5] arm64: dts: ti: Introduce AM62A7 family of SoCs commit: 5fc6b1b62639c764e6e7e261f384d2fb47eff39b [5/5] arm64: dts: ti: Add support for AM62A7-SK commit: 38c4a08c820cd2483750a68f2bf84c3665fe6137 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