From: Rob Herring <robh@kernel.org>
To: Talel Shenhar <talel@amazon.com>
Cc: nicolas.ferre@microchip.com, jason@lakedaemon.net,
marc.zyngier@arm.com, mark.rutland@arm.com,
mchehab+samsung@kernel.org, davem@davemloft.net,
shawn.lin@rock-chips.com, tglx@linutronix.de,
devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, dwmw@amazon.co.uk,
benh@kernel.crashing.org, jonnyc@amazon.com, hhhawa@amazon.com,
ronenk@amazon.com, hanochu@amazon.com, barakw@amazon.com
Subject: Re: [PATCH v4 1/2] dt-bindings: interrupt-controller: Amazon's Annapurna Labs FIC
Date: Mon, 8 Jul 2019 20:23:01 -0600 [thread overview]
Message-ID: <20190709022301.GA8734@bogus> (raw)
In-Reply-To: <1560155683-29584-2-git-send-email-talel@amazon.com>
On Mon, Jun 10, 2019 at 11:34:42AM +0300, Talel Shenhar wrote:
> Document Amazon's Annapurna Labs Fabric Interrupt Controller SoC binding.
>
> Signed-off-by: Talel Shenhar <talel@amazon.com>
> ---
> .../interrupt-controller/amazon,al-fic.txt | 29 ++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/amazon,al-fic.txt
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/amazon,al-fic.txt b/Documentation/devicetree/bindings/interrupt-controller/amazon,al-fic.txt
> new file mode 100644
> index 0000000..4e82fd5
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/interrupt-controller/amazon,al-fic.txt
> @@ -0,0 +1,29 @@
> +Amazon's Annapurna Labs Fabric Interrupt Controller
> +
> +Required properties:
> +
> +- compatible: should be "amazon,al-fic"
> +- reg: physical base address and size of the registers
> +- interrupt-controller: identifies the node as an interrupt controller
> +- #interrupt-cells: must be 2.
> + First cell defines the index of the interrupt within the controller.
> + Second cell is used to specify the trigger type and must be one of the
> + following:
> + - bits[3:0] trigger type and level flags
> + 1 = low-to-high edge triggered
> + 4 = active high level-sensitive
No need to define this here. Reference the standard definition.
> +- interrupt-parent: specifies the parent interrupt controller.
Drop this. It is implied and could be in the parent.
> +- interrupts: describes which input line in the interrupt parent, this
> + fic's output is connected to. This field property depends on the parent's
> + binding
> +
> +Example:
> +
> +amazon_fic: interrupt-controller@0xfd8a8500 {
Drop the '0x'
> + compatible = "amazon,al-fic";
> + interrupt-controller;
> + #interrupt-cells = <2>;
> + reg = <0x0 0xfd8a8500 0x0 0x1000>;
> + interrupt-parent = <&gic>;
> + interrupts = <GIC_SPI 0x0 IRQ_TYPE_LEVEL_HIGH>;
> +};
> --
> 2.7.4
>
next prev parent reply other threads:[~2019-07-09 2:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 8:34 [PATCH v4 0/2] Amazon's Annapurna Labs Fabric Interrupt Controller Talel Shenhar
2019-06-10 8:34 ` Talel Shenhar
2019-06-10 8:34 ` [PATCH v4 1/2] dt-bindings: interrupt-controller: Amazon's Annapurna Labs FIC Talel Shenhar
2019-06-10 8:34 ` Talel Shenhar
2019-06-18 10:46 ` Marc Zyngier
2019-07-09 2:23 ` Rob Herring [this message]
2019-07-09 5:59 ` Shenhar, Talel
2019-07-09 5:59 ` Shenhar, Talel
2019-07-09 8:15 ` Marc Zyngier
2019-07-09 8:17 ` Shenhar, Talel
2019-07-09 8:17 ` Shenhar, Talel
2019-07-09 13:25 ` Rob Herring
2019-06-10 8:34 ` [PATCH v4 2/2] irqchip: al-fic: Introduce Amazon's Annapurna Labs Fabric Interrupt Controller Driver Talel Shenhar
2019-06-10 8:34 ` Talel Shenhar
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=20190709022301.GA8734@bogus \
--to=robh@kernel.org \
--cc=barakw@amazon.com \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hanochu@amazon.com \
--cc=hhhawa@amazon.com \
--cc=jason@lakedaemon.net \
--cc=jonnyc@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=ronenk@amazon.com \
--cc=shawn.lin@rock-chips.com \
--cc=talel@amazon.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.