devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "André Przywara" <andre.przywara@arm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Herring <robh@kernel.org>, Liviu Dudau <liviu.dudau@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH v3 01/20] dt-bindings: arm: gic: Allow combining arm,gic-400 compatible strings
Date: Tue, 19 May 2020 10:19:56 +0100	[thread overview]
Message-ID: <6e2cc3e9-b14f-2b50-0390-addcc82389e0@arm.com> (raw)
In-Reply-To: <CAMuHMdXkHF3ioOVzDZQARiO2i1z8rVjdN_Q0VggaVD4Ln7J+Dw@mail.gmail.com>

On 19/05/2020 08:39, Geert Uytterhoeven wrote:

Hi Geert,


> On Wed, May 13, 2020 at 12:31 PM Andre Przywara <andre.przywara@arm.com> wrote:
>> The arm,gic-400 compatible is probably the best matching string for the
>> GIC in most modern SoCs, but was only introduced later into the kernel.
>> For historic reasons and to keep compatibility, some SoC DTs were thus
>> using a combination of this name and one of the older strings, which
>> currently the binding denies.
>>
>> Add a stanza to the DT binding to allow "arm,gic-400", followed by
>> either "arm,cortex-a15-gic" or "arm,cortex-a7-gic". This fixes binding
>> compliance for quite some SoC .dtsi files in the kernel tree.
>>
>> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> 
> Thanks for your patch, I was just looking into this issue ;-)
> 
>> --- a/Documentation/devicetree/bindings/interrupt-controller/arm,gic.yaml
>> +++ b/Documentation/devicetree/bindings/interrupt-controller/arm,gic.yaml
>> @@ -39,6 +39,12 @@ properties:
>>                - qcom,msm-8660-qgic
>>                - qcom,msm-qgic2
>>
>> +      - items:
>> +          - const: arm,gic-400
>> +          - enum:
>> +             - arm,cortex-a15-gic
>> +             - arm,cortex-a7-gic
>> +
>>        - items:
>>            - const: arm,arm1176jzf-devchip-gic
>>            - const: arm,arm11mp-gic
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/r9a06g032.dtsi#n177
> has them in the other order.
> 
> What do you think is the preferred solution: reverting the order, or dropping
> one or the other?

Reverting the order would be the right thing. Theoretically this might
change what the drivers match against, but there should be no difference
between those strings anyway. And certainly Linux does not care which of
the many strings it sees.

The proper order is not really obvious here, but the cortex-a{15,7}-gic
names serve as the missing "arm,gic-v2" generic fallback string here, I
think just for historical reasons.

Cheers,
Andre.

  reply	other threads:[~2020-05-19  9:20 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 10:29 [PATCH v3 00/20] dts/dt-bindings: Fix Arm Ltd. ARMv8 "boards" Andre Przywara
2020-05-13 10:29 ` [PATCH v3 01/20] dt-bindings: arm: gic: Allow combining arm,gic-400 compatible strings Andre Przywara
2020-05-15  3:16   ` [PATCH v3 01/20] dt-bindings: arm: gic: Allow combining arm, gic-400 " Rob Herring
2020-05-19  7:39   ` [PATCH v3 01/20] dt-bindings: arm: gic: Allow combining arm,gic-400 " Geert Uytterhoeven
2020-05-19  9:19     ` André Przywara [this message]
2020-05-26 15:49       ` Rob Herring
2020-05-13 10:29 ` [PATCH v3 02/20] arm64: dts: arm: Fix node address fields Andre Przywara
2020-05-13 17:01   ` Sudeep Holla
2020-05-13 10:29 ` [PATCH v3 03/20] arm64: dts: arm: fvp: Move fixed devices out of bus node Andre Przywara
2020-05-13 17:22   ` Sudeep Holla
2020-05-13 10:30 ` [PATCH v3 04/20] arm64: dts: arm: vexpress: " Andre Przywara
2020-05-13 17:26   ` Sudeep Holla
2020-05-28  2:48   ` Guenter Roeck
2020-05-28  2:55     ` Guenter Roeck
2020-06-27  3:57       ` Guenter Roeck
2020-06-29  8:55         ` Sudeep Holla
2020-05-28 13:30     ` André Przywara
2020-06-01 10:14       ` André Przywara
2020-06-01 23:12         ` Rob Herring
2020-06-03 11:20           ` André Przywara
2020-06-03 13:49             ` Rob Herring
2020-05-13 10:30 ` [PATCH v3 05/20] arm64: dts: arm: foundation: Move fixed clocks " Andre Przywara
2020-05-13 10:30 ` [PATCH v3 06/20] arm64: dts: arm: juno: Move fixed devices " Andre Przywara
2020-05-13 10:30 ` [PATCH v3 07/20] arm64: dts: juno: Fix mem-timer Andre Przywara
2020-05-13 10:30 ` [PATCH v3 08/20] arm64: dts: arm: model: Fix GIC compatible names Andre Przywara
2020-05-13 18:21   ` Sudeep Holla
2020-05-15 15:10     ` André Przywara
2020-05-13 10:30 ` [PATCH v3 09/20] arm64: dts: arm: juno: Fix GIC child nodes Andre Przywara
2020-05-13 10:30 ` [PATCH v3 10/20] arm64: dts: arm: foundation: " Andre Przywara
2020-05-13 10:30 ` [PATCH v3 11/20] arm64: dts: arm: Fix ITS node names and #msi-cells Andre Przywara
2020-05-13 10:30 ` [PATCH v3 12/20] arm64: dts: juno: usb: Use proper DT node name Andre Przywara
2020-05-13 10:30 ` [PATCH v3 13/20] arm64: dts: arm: Fix serial node names Andre Przywara
2020-05-13 10:30 ` [PATCH v3 14/20] arm64: dts: fvp: Fix SMMU DT node Andre Przywara
2020-05-13 10:30 ` [PATCH v3 15/20] arm64: dts: arm: Fix bus node names Andre Przywara
2020-05-13 10:30 ` [PATCH v3 16/20] arm64: dts: juno: Fix GPU interrupt order Andre Przywara
2020-05-13 18:24   ` Sudeep Holla
2020-05-15 15:13     ` André Przywara
2020-05-13 10:30 ` [PATCH v3 17/20] arm64: dts: arm: Fix VExpress LED names Andre Przywara
2020-05-13 10:30 ` [PATCH v3 18/20] arm64: dts: juno: Fix SCPI shared mem node name Andre Przywara
2020-05-13 10:30 ` [PATCH v3 19/20] dt-bindings: mali-midgard: Allow dma-coherent Andre Przywara
2020-05-15  3:16   ` Rob Herring
2020-05-13 10:30 ` [PATCH v3 20/20] dt-bindings: ehci/ohci: Allow iommus property Andre Przywara
2020-05-13 18:28   ` Sudeep Holla
2020-05-15  3:17   ` Rob Herring
2020-05-18  8:15 ` [PATCH v3 00/20] dts/dt-bindings: Fix Arm Ltd. ARMv8 "boards" Sudeep Holla
2020-05-18 11:31 ` Sudeep Holla

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=6e2cc3e9-b14f-2b50-0390-addcc82389e0@arm.com \
    --to=andre.przywara@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=liviu.dudau@arm.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=robh@kernel.org \
    --cc=sudeep.holla@arm.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).