| Message ID | 20220215201008.15235-1-nm@ti.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | arm64: dts: ti: k3*: Fix gic-v3 compatible regs | expand |
On Tue, 15 Feb 2022 20:10:03 +0000, Nishanth Menon <nm@ti.com> wrote: > > Hi, > > This series was triggered by the discussion in [1], and we realized we > need to cleanup the definitions in K3 SoC. Usage of kvm with gic-v2 > compatibility is a bit niche usecase, but valid and possible with A53 > and A72 even though the GIC500 instantiation is done with no backward > compatibility. > > Nishanth Menon (5): > arm64: dts: ti: k3-am65: Fix gic-v3 compatible regs > arm64: dts: ti: k3-j721e: Fix gic-v3 compatible regs > arm64: dts: ti: k3-j7200: Fix gic-v3 compatible regs > arm64: dts: ti: k3-am64: Fix gic-v3 compatible regs > arm64: dts: ti: k3-j721s2: Fix gic-v3 compatible regs > > arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 5 ++++- > arch/arm64/boot/dts/ti/k3-am64.dtsi | 1 + > arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 5 ++++- > arch/arm64/boot/dts/ti/k3-am65.dtsi | 1 + > arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 5 ++++- > arch/arm64/boot/dts/ti/k3-j7200.dtsi | 1 + > arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 5 ++++- > arch/arm64/boot/dts/ti/k3-j721e.dtsi | 1 + > arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 5 ++++- > arch/arm64/boot/dts/ti/k3-j721s2.dtsi | 1 + > 10 files changed, 25 insertions(+), 5 deletions(-) > > [1] https://lore.kernel.org/all/87k0e0tirw.wl-maz@kernel.org/ For the series: Acked-by: Marc Zyngier <maz@kernel.org> M.
Hi Nishanth Menon, On Tue, 15 Feb 2022 14:10:03 -0600, Nishanth Menon wrote: > This series was triggered by the discussion in [1], and we realized we > need to cleanup the definitions in K3 SoC. Usage of kvm with gic-v2 > compatibility is a bit niche usecase, but valid and possible with A53 > and A72 even though the GIC500 instantiation is done with no backward > compatibility. > > Nishanth Menon (5): > arm64: dts: ti: k3-am65: Fix gic-v3 compatible regs > arm64: dts: ti: k3-j721e: Fix gic-v3 compatible regs > arm64: dts: ti: k3-j7200: Fix gic-v3 compatible regs > arm64: dts: ti: k3-am64: Fix gic-v3 compatible regs > arm64: dts: ti: k3-j721s2: Fix gic-v3 compatible regs > > [...] I have applied the following to branch ti-k3-dts-next on [1]. Thank you! [1/5] arm64: dts: ti: k3-am65: Fix gic-v3 compatible regs commit: 8cae268b70f387ff9e697ccd62fb2384079124e7 [2/5] arm64: dts: ti: k3-j721e: Fix gic-v3 compatible regs commit: a06ed27f3bc63ab9e10007dc0118d910908eb045 [3/5] arm64: dts: ti: k3-j7200: Fix gic-v3 compatible regs commit: 1a307cc299430dd7139d351a3b8941f493dfa885 [4/5] arm64: dts: ti: k3-am64: Fix gic-v3 compatible regs commit: de60edf1be3d42d4a1b303b41c7c53b2f865726e [5/5] arm64: dts: ti: k3-j721s2: Fix gic-v3 compatible regs commit: a966803781fc5e1875511db9392b0d16174c5dd2 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