[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGhQ9Vw4DrhOn8=ACzTsX5ykbnq0Gp-qAjOrMhEHjgpz=8hO=A@mail.gmail.com>
Date: Wed, 2 Mar 2016 19:25:27 +0100
From: Joachim Eastwood <manabian@...il.com>
To: Rob Herring <robh@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, devicetree@...r.kernel.org
Subject: Re: [PATCH 2/2] devicetree: document NXP LPC1850 PINT irq controller binding
On 2 March 2016 at 19:13, Rob Herring <robh@...nel.org> wrote:
> On Thu, Feb 25, 2016 at 11:04:47PM +0100, Joachim Eastwood wrote:
>> Add binding documentation for NXP LPC1850 GPIO Pin Interrupt (PINT)
>> controller.
>>
>> Signed-off-by: Joachim Eastwood <manabian@...il.com>
>> ---
>> .../interrupt-controller/nxp,lpc1850-gpio-pint.txt | 22 ++++++++++++++++++++++
>> 1 file changed, 22 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/nxp,lpc1850-gpio-pint.txt
>>
>> diff --git a/Documentation/devicetree/bindings/interrupt-controller/nxp,lpc1850-gpio-pint.txt b/Documentation/devicetree/bindings/interrupt-controller/nxp,lpc1850-gpio-pint.txt
>> new file mode 100644
>> index 000000000000..dc43f187ebda
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/interrupt-controller/nxp,lpc1850-gpio-pint.txt
>> @@ -0,0 +1,22 @@
>> +NXP LPC18xx/43xx GPIO Pin Interrupt (PINT) controller
>> +
>> +Required properties:
>> +
>> +- compatible : should be "nxp,lpc1850-gpio-pint".
>> +- reg : Specifies base physical address and size of the registers.
>> +- interrupt-controller : Identifies the node as an interrupt controller
>> +- #interrupt-cells : Specifies the number of cells needed to encode an
>> + interrupt source. The value shall be 2.
>> +- interrupts : Specifies the CPU interrupts the controller is connected to.
>
> How many (8?) and what's the ordering?
The PINT on has 8 interrupts, but this is device dependent. Up to 32
could be supported.
The order is also device dependent. The interrupts on PINT are merely
mapped onto the main interrupt controller.
I tried to keep the wording in the binding generic so it could support
the PINT on different devices. I'll update the text with some more
details.
regards,
Joachim Eastwood
Powered by blists - more mailing lists