From: Rob Herring <robh@kernel.org>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, maz@kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: interrupt-controller: arm,gic-v3: Make 'interrupts' optional
Date: Tue, 23 Aug 2022 10:41:26 -0500 [thread overview]
Message-ID: <20220823154126.GA3260525-robh@kernel.org> (raw)
In-Reply-To: <20220822152224.507497-3-jean-philippe@linaro.org>
On Mon, 22 Aug 2022 16:22:23 +0100, Jean-Philippe Brucker wrote:
> A GICv3 implementation without virtualization, such as the base QEMU
> virt machine (without -M virtualization=on), does not issue maintenance
> interrupts. Therefore its device-tree node does not need an 'interrupts'
> property. Currently, validating the QEMU virt device-tree throws a
> warning that 'interrupts' is missing. Make it optional.
>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> ---
> .../devicetree/bindings/interrupt-controller/arm,gic-v3.yaml | 1 -
> 1 file changed, 1 deletion(-)
>
Applied, thanks!
next prev parent reply other threads:[~2022-08-23 17:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 15:22 [PATCH 0/3] dt-bindings: Some schema fixes Jean-Philippe Brucker
2022-08-22 15:22 ` [PATCH 1/3] dt-bindings: regulator: Fix qcom,spmi-regulator schema Jean-Philippe Brucker
2022-08-22 19:42 ` Rob Herring
2022-08-30 12:45 ` Rob Herring
2022-08-22 15:22 ` [PATCH 2/3] dt-bindings: interrupt-controller: arm,gic-v3: Make 'interrupts' optional Jean-Philippe Brucker
2022-08-22 19:46 ` Rob Herring
2022-08-22 19:47 ` Marc Zyngier
2022-08-23 15:41 ` Rob Herring [this message]
2022-08-22 15:22 ` [PATCH 3/3] dt-bindings: interrupt-controller: arm,gic: Support two address and size cells Jean-Philippe Brucker
2022-08-22 19:46 ` Marc Zyngier
2022-08-22 19:50 ` Rob Herring
2022-08-22 21:43 ` Marc Zyngier
2022-08-23 15:41 ` Rob Herring
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=20220823154126.GA3260525-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jean-philippe@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.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).