Re: [PATCH] dt-bindings: arm,nvic: Binding for ARM NVIC interrupt controller on Cortex-M

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> On Apr 3, 2017, at 8:32 AM, Rob Herring <robh@xxxxxxxxxx> wrote:
> 
> On Mon, Mar 27, 2017 at 01:09:05PM -0500, Kumar Gala wrote:
>> Signed-off-by: Kumar Gala <kumar.gala@xxxxxxxxxx>
>> ---
>> Note: This is a new binding and not used by the linux kernel code right now for
>> the nvic.  The intent would be to support both the current 'arm,armv7m-nvic'
>> compatible and this binding in the code in the future.  The 'arm,armv7m-nvic'
>> doesnt have any binding spec covering it today.
>> 
>> .../bindings/interrupt-controller/arm,nvic.txt     | 37 ++++++++++++++++++++++
>> 1 file changed, 37 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/arm,nvic.txt
>> 
>> diff --git a/Documentation/devicetree/bindings/interrupt-controller/arm,nvic.txt b/Documentation/devicetree/bindings/interrupt-controller/arm,nvic.txt
>> new file mode 100644
>> index 0000000..60ee89c
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/interrupt-controller/arm,nvic.txt
>> @@ -0,0 +1,37 @@
>> +* ARM Nested Vector Interrupt Controller (NVIC)
>> +
>> +The NVIC provides an interrupt controller that is tightly coupled to
>> +Cortex-M based processor cores.  The NVIC implemented on different SoCs
>> +vary in the number of interrupts and priority bits per interrupt.
>> +
>> +Main node required properties:
>> +
>> +- compatible : should be one of:
>> +	"arm,v6m-nvic"
>> +	"arm,v7m-nvic"
>> +	"arm,v8m-nvic"
>> +	"arm,nvic"
> 
> I'd drop this last one.

done

> 
>> +- interrupt-controller : Identifies the node as an interrupt controller
>> +- #interrupt-cells : Specifies the number of cells needed to encode an
>> +  interrupt source.  The type shall be a <u32> and the value shall be 2.
>> +
>> +  The 1st cell contains the interrupt number for the interrupt type.
>> +
>> +  The 2nd cell is the priority of the interrupt.
> 
> No level/edge flags needed?

Nope, it seems to be implied in how the IRQs get wired up to the NVIC.

> 
>> +
>> +- reg : Specifies base physical address(s) and size of the NVIC registers.
>> +  This is at a fixed address (0xe000e100) and size (0xc00).
>> +
>> +- arm,num-irq-priority-bits: The number of priority bits implemented by the
>> +  given SoC
>> +
>> +Example:
>> +
>> +	intc: interrupt-controller@e000e100 {
>> +		compatible = "arm,nvic";
>> +		#interrupt-cells = <2>;
>> +		#address-cells = <1>;
>> +		interrupt-controller;
>> +		reg = <0xe000e100 0xc00>;
>> +		arm,num-irq-priority-bits = <4>;
>> +	};
>> -- 
>> 2.9.3
>> 

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux