[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <169126186772.69126.7798113611877655523.b4-ty@ti.com>
Date: Sat, 5 Aug 2023 14:00:45 -0500
From: Nishanth Menon <nm@...com>
To: Vignesh Raghavendra <vigneshr@...com>,
Tero Kristo <kristo@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Francesco Dolcini <francesco@...cini.it>
CC: Nishanth Menon <nm@...com>,
Francesco Dolcini <francesco.dolcini@...adex.com>,
<linux-arm-kernel@...ts.infradead.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Judith Mendez <jm@...com>
Subject: Re: [PATCH v2 0/2] arm64: dts: ti: k3-am62: Add MCU MCAN
Hi Francesco Dolcini,
On Wed, 02 Aug 2023 09:36:33 +0200, Francesco Dolcini wrote:
> From: Francesco Dolcini <francesco.dolcini@...adex.com>
>
> On AM62x there are no hardware interrupts routed to A53 GIC
> interrupt controller for MCU MCAN IPs, so MCU MCAN nodes were
> omitted from MCU dtsi.
>
> Timer polling was introduced in commits [1][2] so now add MCU MCAN nodes
> to the MCU dtsi for Cortex A53.
I understand the dependency, it does create a dtbs_check warnings on
rc1, but I am picking this up since the yaml fixup is in next already
and not a new compatible addition. if the fixups does'nt end up in
linus-master for 6.6-rc1, we might need to look at what we need to do.
Please let me know if there is any concerns and I can drop this series
from my tree.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/2] arm64: dts: ti: k3-am62: Add MCU MCAN nodes
commit: 108f61e03963a3a019486fd80cc84d5db5c204d0
[2/2] arm64: dts: ti: k3-am625-verdin: enable CAN_2
commit: 7480cea33b4c36aeffe592eb6f151bc9974fee70
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
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists