devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Marc Zyngier <maz@kernel.org>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH] dt-bindings: interrupt-controller: arm,gic-v3: Make the v2 compat requirements explicit
Date: Sat, 9 Apr 2022 12:49:38 +0200	[thread overview]
Message-ID: <4557c5fe-6c39-2014-65a4-c14dac98f902@linaro.org> (raw)
In-Reply-To: <20220409101617.268796-1-maz@kernel.org>

On 09/04/2022 12:16, Marc Zyngier wrote:
> A common mistake when writing a device tree for a platform that is using
> GICv3 with ancient CPUs is to overlook the MMIO frames that implement
> the GICv2 compatibility feature, because this feature is implemented by
> the CPUs and not by the GIC itself.
> 
> The compatibility feature itself is optional (all the modern
> implementations have dropped it), but is present in all the ARM Ltd
> implementations of the ARMv8.0 architecture (A3x, A53, A57, A72, A73),
> and many others from various implementers.
> 
> Make it explicit that GICC, GICH and GICV are required for these CPUs.
> Also take this opportunity to update my email address, as people keep
> sending them to the wrong place...
> 
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
> ---
>  .../bindings/interrupt-controller/arm,gic-v3.yaml         | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 


Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>


Best regards,
Krzysztof

      reply	other threads:[~2022-04-09 10:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09 10:16 [PATCH] dt-bindings: interrupt-controller: arm,gic-v3: Make the v2 compat requirements explicit Marc Zyngier
2022-04-09 10:49 ` Krzysztof Kozlowski [this message]

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=4557c5fe-6c39-2014-65a4-c14dac98f902@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=robh+dt@kernel.org \
    /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).