From: <Claudiu.Beznea@microchip.com>
To: <Eugen.Hristev@microchip.com>, <linux-arm-kernel@lists.infradead.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<Nicolas.Ferre@microchip.com>
Subject: Re: [PATCH] ARM: dts: at91: sama7g5: remove interrupt-parent from gic node
Date: Mon, 9 May 2022 05:57:39 +0000 [thread overview]
Message-ID: <f5cc90c5-c822-7db5-8480-593c6cc90659@microchip.com> (raw)
In-Reply-To: <20220503133127.64320-1-eugen.hristev@microchip.com>
On 03.05.2022 16:31, Eugen Hristev wrote:
> interrupt-parent is not to be used as a boolean property.
> It is already present in the DT in the proper way it's supposed to be used:
> interrupt-parent = <&gic>;
>
> This is also reported by dtbs_check:
> arch/arm/boot/dts/at91-sama7g5ek.dtb: interrupt-controller@e8c11000: interrupt-parent: True is not of type 'array'
> From schema: /.local/lib/python3.8/site-packages/dtschema/schemas/interrupts.yaml
>
> Fixes: 7540629e2fc7 ("ARM: dts: at91: add sama7g5 SoC DT and sama7g5-ek")
> Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>
> ---
> arch/arm/boot/dts/sama7g5.dtsi | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/sama7g5.dtsi b/arch/arm/boot/dts/sama7g5.dtsi
> index cdaa9c825f69..f4f174314e4e 100644
> --- a/arch/arm/boot/dts/sama7g5.dtsi
> +++ b/arch/arm/boot/dts/sama7g5.dtsi
> @@ -949,7 +949,6 @@ gic: interrupt-controller@e8c11000 {
> #interrupt-cells = <3>;
> #address-cells = <0>;
> interrupt-controller;
> - interrupt-parent;
> reg = <0xe8c11000 0x1000>,
> <0xe8c12000 0x2000>;
> };
prev parent reply other threads:[~2022-05-09 6:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 13:31 [PATCH] ARM: dts: at91: sama7g5: remove interrupt-parent from gic node Eugen Hristev
2022-05-09 5:57 ` Claudiu.Beznea [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=f5cc90c5-c822-7db5-8480-593c6cc90659@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Eugen.Hristev@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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).