[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaL1-Mw85hrJNbKk0rY2txeQ3bYVS9TYpwQ=+R3Wvxpug@mail.gmail.com>
Date: Tue, 2 Mar 2021 16:22:00 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Álvaro Fernández Rojas <noltari@...il.com>
Cc: Florian Fainelli <f.fainelli@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Jonas Gorski <jonas.gorski@...il.com>,
Necip Fazil Yildiran <fazilyildiran@...il.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 03/12] Documentation: add BCM6358 pincontroller binding documentation
On Thu, Feb 25, 2021 at 5:42 PM Álvaro Fernández Rojas
<noltari@...il.com> wrote:
> Add binding documentation for the pincontrol core found in BCM6358 SoCs.
>
> Signed-off-by: Álvaro Fernández Rojas <noltari@...il.com>
> Signed-off-by: Jonas Gorski <jonas.gorski@...il.com>
(...)
> + interrupts-extended:
> + description:
> + One interrupt per each of the 4 GPIO ports supported by the controller,
4? Below says 6.
> + sorted by port number ascending order.
> + minItems: 6
> + maxItems: 6
As noted in the review I think this interrupt controller is hierarchical
and this is not needed. All that is needed is for the chip to know
its interrupt-parent.
Yours,
Linus Walleij
Powered by blists - more mailing lists