[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230421190428.GA1617382-robh@kernel.org>
Date: Fri, 21 Apr 2023 14:04:28 -0500
From: Rob Herring <robh@...nel.org>
To: Binbin Zhou <zhoubb.aaron@...il.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Binbin Zhou <zhoubinbin@...ngson.cn>,
Huacai Chen <chenhuacai@...nel.org>,
WANG Xuerui <kernel@...0n.name>,
Jiaxun Yang <jiaxun.yang@...goat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Marc Zyngier <maz@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Jianmin Lv <lvjianmin@...ngson.cn>,
Huacai Chen <chenhuacai@...ngson.cn>,
linux-kernel@...r.kernel.org, linux-mips@...r.kernel.org,
loongarch@...ts.linux.dev, devicetree@...r.kernel.org,
loongson-kernel@...ts.loongnix.cn
Subject: Re: [PATCH V3 1/2] dt-bindings: interrupt-controller: Add Loongson
EIOINTC
On Thu, Apr 20, 2023 at 09:00:42PM +0800, Binbin Zhou wrote:
> On Thu, Apr 20, 2023 at 4:09 AM Krzysztof Kozlowski
> <krzysztof.kozlowski@...aro.org> wrote:
> >
> > On 19/04/2023 09:17, Binbin Zhou wrote:
> > > Add Loongson Extended I/O Interrupt controller binding with DT schema
> > > format using json-schema.
> > >
> > > Signed-off-by: Binbin Zhou <zhoubinbin@...ngson.cn>
> > > ---
> > > .../loongson,eiointc.yaml | 74 +++++++++++++++++++
> > > 1 file changed, 74 insertions(+)
> > > create mode 100644 Documentation/devicetree/bindings/interrupt-controller/loongson,eiointc.yaml
> > >
> > > diff --git a/Documentation/devicetree/bindings/interrupt-controller/loongson,eiointc.yaml b/Documentation/devicetree/bindings/interrupt-controller/loongson,eiointc.yaml
> > > new file mode 100644
> > > index 000000000000..4ab4efb061e1
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/interrupt-controller/loongson,eiointc.yaml
> > > @@ -0,0 +1,74 @@
> > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > > +%YAML 1.2
> > > +---
> > > +$id: http://devicetree.org/schemas/interrupt-controller/loongson,eiointc.yaml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: Loongson Extended I/O Interrupt Controller
> > > +
> > > +maintainers:
> > > + - Binbin Zhou <zhoubinbin@...ngson.cn>
> > > +
> > > +description: |
> > > + This interrupt controller is found on the Loongson-3 family chips and
> > > + Loongson-2K series chips and is used to distribute interrupts directly to
> > > + individual cores without forwarding them through the HT's interrupt line.
> > > +
> > > +allOf:
> > > + - $ref: /schemas/interrupt-controller.yaml#
> > > +
> > > +properties:
> > > + compatible:
> > > + enum:
> > > + - loongson,ls2k0500-eiointc
> > > + - loongson,ls2k2000-eiointc
> > > +
> > > + reg:
> > > + items:
> > > + - description: Interrupt enable registers
> > > + - description: Interrupt status registers
> > > + - description: Interrupt clear registers
> > > + - description: Interrupt routing configuration registers
> > > +
> > > + reg-names:
> > > + items:
> > > + - const: enable
> > > + - const: status
> > > + - const: clear
> > > + - const: route
> > > +
> > > + interrupts:
> > > + maxItems: 1
> > > +
> > > + interrupt-controller: true
> > > +
> > > + '#interrupt-cells':
> > > + const: 1
> > > +
> > > +required:
> > > + - compatible
> > > + - reg
> > > + - interrupts
> > > + - interrupt-controller
> > > + - '#interrupt-cells'
> > > +
> > > +unevaluatedProperties: false
> > > +
> > > +examples:
> > > + - |
> > > + eiointc: interrupt-controller@...11600 {
> > > + compatible = "loongson,ls2k0500-eiointc";
> > > + reg = <0x1fe11600 0x10>,
> > > + <0x1fe11700 0x10>,
> > > + <0x1fe11800 0x10>,
> > > + <0x1fe114c0 0x4>;
> >
> > Binding is OK, but are you sure you want to split the address space like
> > this? It looks like two address spaces (enable+clear+status should be
> > one). Are you sure this is correct?
> >
> Hi Krzysztof:
>
> These registers are all in the range of chip configuration registers,
> in the case of LS2K0500, which has a base address of 0x1fe10000.
Where is the schema for this? Either it should be the
interrupt-controller itself or this binding should be a child node of
it. Which way really depends on whether the eiointc is reused on
multiple chips with different register offsets or parent block.
Can't really give better advice without a complete picture of the 'chip
configuration registers'. So please provide that.
Rob
Powered by blists - more mailing lists