linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Nishanth Menon <nm@ti.com>
Cc: Tero Kristo <kristo@kernel.org>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 0/5] arm64: dts: ti: k3*: Fix gic-v3 compatible regs
Date: Wed, 16 Feb 2022 09:16:14 +0000	[thread overview]
Message-ID: <87a6er41ep.wl-maz@kernel.org> (raw)
In-Reply-To: <20220215201008.15235-1-nm@ti.com>

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.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-02-16  9:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 20:10 [PATCH 0/5] arm64: dts: ti: k3*: Fix gic-v3 compatible regs Nishanth Menon
2022-02-15 20:10 ` [PATCH 1/5] arm64: dts: ti: k3-am65: " Nishanth Menon
2022-02-15 20:10 ` [PATCH 2/5] arm64: dts: ti: k3-j721e: " Nishanth Menon
2022-02-15 20:10 ` [PATCH 3/5] arm64: dts: ti: k3-j7200: " Nishanth Menon
2022-02-15 20:10 ` [PATCH 4/5] arm64: dts: ti: k3-am64: " Nishanth Menon
2022-02-15 20:10 ` [PATCH 5/5] arm64: dts: ti: k3-j721s2: " Nishanth Menon
2022-02-16  9:16 ` Marc Zyngier [this message]
2022-02-22 19:31 ` [PATCH 0/5] arm64: dts: ti: k3*: " Nishanth Menon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a6er41ep.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).