Hi Andrew Davis,
On Thu, 20 Oct 2022 11:02:53 -0500, Andrew Davis wrote:
> Same story as for AM64x[0] and AM62x[1], this time for J7x.
>
> This one was a little more involved that the last 2 rounds as some IP
> (like UART) are pinned out using the default pinmux. Perhaps we should be
> explicit here and have pinmux nodes that simply restate the defaults. I
> can go solve that in a follow up series if we think that is what we
> want to do.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[01/12] arm64: dts: ti: k3-j721e: Enable UART nodes at the board level
commit: fe17e20fde14c6cbaf1cae97aef370b6f4c73518
[02/12] arm64: dts: ti: k3-j721e: Enable I2C nodes at the board level
commit: 282c4ad3b8c1da99095e0edbbe617cdf4dcb138b
[03/12] arm64: dts: ti: k3-j721e: Enable MCASP nodes at the board level
commit: 256596ad158c80c8e4104a6310a411ec8829f9eb
[04/12] arm64: dts: ti: k3-j721e: Enable MCAN nodes at the board level
commit: 39e7758b94e31071a87489364c723afe92849ae7
[05/12] arm64: dts: ti: k3-j7200: Enable UART nodes at the board level
commit: dae322f8a7ef11a06bfb61bada4ebbcac219783e
[06/12] arm64: dts: ti: k3-j7200: Enable I2C nodes at the board level
commit: a9ed915cd55c883fed72e50b45988fa4305496a7
[07/12] arm64: dts: ti: k3-j721s2: Enable UART nodes at the board level
commit: 0e63f35a9c6acf1d74bd693c492f8955bb16c89a
[08/12] arm64: dts: ti: k3-j721e: Enable Mailbox nodes at the board level
commit: 7e48b665100ee84bdaa163dece6d40351077f664
[09/12] arm64: dts: ti: k3-j7200: Enable Mailbox nodes at the board level
commit: 74f0f58d3122c3e2cc313dd6311b9742dbfd54e0
[10/12] arm64: dts: ti: k3-j721s2: Enable Mailbox nodes at the board level
commit: 3fb0402f65959edc9a14842dc36828d2c7109ae2
[11/12] arm64: dts: ti: k3-j721s2: Enable MCAN nodes at the board level
commit: 06639b8ae0e9be0cf0195209e6b69f4e254687b0
[12/12] arm64: dts: ti: k3-j721s2: Enable I2C nodes at the board level
commit: 0aef5131380628e2a9bfcbbcfed5d6477c8f9651
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] git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
