devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <maz@kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Jonas Gorski <jonas.gorski@gmail.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	linux-mips@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: interrupt-controller: document BCM6345 external interrupt controller
Date: Sun, 7 Mar 2021 11:12:55 +0100	[thread overview]
Message-ID: <889b9814-40d4-e012-ff7c-39b00f8c623a@gmail.com> (raw)
In-Reply-To: <20210306201404.GB1137882@robh.at.kernel.org>

Hi Rob,

El 06/03/2021 a las 21:14, Rob Herring escribió:
> On Wed, Feb 24, 2021 at 08:56:39AM +0100, Álvaro Fernández Rojas wrote:
>> Document the binding for the BCM6345 external interrupt controller.
>>
>> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
>> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
>> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
>> ---
>>   v3: pass dt_binding_check.
>>   v2: fix title typo.
>>
>>   .../brcm,bcm6345-ext-intc.yaml                | 78 +++++++++++++++++++
>>   1 file changed, 78 insertions(+)
>>   create mode 100644 Documentation/devicetree/bindings/interrupt-controller/brcm,bcm6345-ext-intc.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm6345-ext-intc.yaml b/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm6345-ext-intc.yaml
>> new file mode 100644
>> index 000000000000..a691510e78b7
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm6345-ext-intc.yaml
>> @@ -0,0 +1,78 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/interrupt-controller/brcm,bcm6345-ext-intc.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Broadcom BCM6345 external interrupt controller
>> +
>> +maintainers:
>> +  - Álvaro Fernández Rojas <noltari@gmail.com>
>> +  - Jonas Gorski <jonas.gorski@gmail.com>
>> +
>> +properties:
>> +  compatible:
>> +    enum:
>> +      - brcm,bcm6318-ext-intc
>> +      - brcm,bcm6345-ext-intc
>> +
>> +  "#interrupt-cells":
>> +    const: 2
>> +
>> +  reg:
>> +    maxItems: 1
>> +
>> +  "#address-cells":
>> +    const: 0
>> +
>> +  interrupt-controller: true
>> +
>> +  interrupts:
>> +    description: Specifies the interrupt line(s) in the interrupt-parent
>> +      controller node. Valid values depend on the type of parent interrupt
>> +      controller.
>> +    maxItems: 4
>> +
>> +  brcm,field-width:
>> +    description: Interrupt controller field width (the default is 4).
> 
> default: 4
> 
>> +    maxItems: 1
> 
> All uint32's are 1 item.

Ok, so I should remove this :)

> 
> What's the set or range of values?

Only BCM6348 needs to set this value to 5, other BCM63xx use the default 
value of 4 (BCM3368, BCM6318, BCM6328, BCM6338, BCM6345, BCM6358, 
BCM6362, BCM6368, BCM63268).

> 
>> +    $ref: /schemas/types.yaml#/definitions/uint32
>> +
>> +required:
>> +  - "#address-cells"
>> +  - compatible
>> +  - reg
>> +  - "#interrupt-cells"
>> +  - interrupt-controller
>> +  - interrupts
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> +  - |
>> +    interrupt-controller@10000018 {
>> +      #address-cells = <0>;
>> +      compatible = "brcm,bcm6345-ext-intc";
>> +      reg = <0x10000018 0x4>;
>> +
>> +      interrupt-parent = <&periph_intc>;
>> +      #interrupt-cells = <2>;
>> +
>> +      interrupt-controller;
>> +      interrupts = <24>, <25>, <26>, <27>;
>> +    };
>> +
>> +  - |
>> +    interrupt-controller@fffe0014 {
>> +      #address-cells = <0>;
>> +      compatible = "brcm,bcm6345-ext-intc";
>> +      reg = <0xfffe0014 0x4>;
>> +
>> +      interrupt-controller;
>> +      #interrupt-cells = <2>;
>> +
>> +      interrupt-parent = <&cpu_intc>;
>> +      interrupts = <3>, <4>, <5>, <6>;
>> +
>> +      brcm,field-width = <5>;
>> +    };
>> -- 
>> 2.20.1
>>

Best regards,
Álvaro.

  reply	other threads:[~2021-03-07 10:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 18:08 [PATCH 0/2] irqchip: add support for BCM6345 interrupt controller Álvaro Fernández Rojas
2021-02-23 18:08 ` [PATCH 1/2] dt-bindings: interrupt-controller: document BCM6345 external " Álvaro Fernández Rojas
2021-02-23 19:34   ` Rob Herring
2021-02-24  9:35   ` kernel test robot
2021-02-23 18:08 ` [PATCH 2/2] irqchip: add support for BCM6345 " Álvaro Fernández Rojas
2021-02-24  1:38   ` kernel test robot
2021-02-23 20:43 ` [PATCH v2 0/2] " Álvaro Fernández Rojas
2021-02-23 20:43   ` [PATCH v2 1/2] dt-bindings: interrupt-controller: document BCM6345 external " Álvaro Fernández Rojas
2021-02-24  3:39     ` Florian Fainelli
2021-02-24  3:49     ` Rob Herring
2021-02-23 20:43   ` [PATCH v2 2/2] irqchip: add support for " Álvaro Fernández Rojas
2021-02-24  3:43     ` Florian Fainelli
2021-02-24  7:08       ` Álvaro Fernández Rojas
2021-02-24  7:56   ` [PATCH v2 0/2] irqchip: add support for BCM6345 " Álvaro Fernández Rojas
2021-02-24  7:56     ` [PATCH v2 1/2] dt-bindings: interrupt-controller: document BCM6345 external " Álvaro Fernández Rojas
2021-03-06 20:14       ` Rob Herring
2021-03-07 10:12         ` Álvaro Fernández Rojas [this message]
2021-03-10 17:21           ` Rob Herring
2021-02-24  7:56     ` [PATCH v2 2/2] irqchip: add support for " Álvaro Fernández Rojas
2021-03-09 10:58       ` Marc Zyngier
2021-02-24  7:58     ` [PATCH v2 0/2] irqchip: add support for BCM6345 " Álvaro Fernández Rojas
2021-02-24 10:03       ` Marc Zyngier
2021-02-27  6:49     ` Álvaro Fernández Rojas
2021-03-06 20:11       ` 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=889b9814-40d4-e012-ff7c-39b00f8c623a@gmail.com \
    --to=noltari@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=jonas.gorski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=robh@kernel.org \
    --cc=tglx@linutronix.de \
    /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).