All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
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, robh+dt@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 v2 1/2] dt-bindings: interrupt-controller: Amazon's Annapurna Labs FIC
Date: Wed, 5 Jun 2019 12:08:55 +0100	[thread overview]
Message-ID: <20190605110855.GC20813@e107155-lin> (raw)
In-Reply-To: <1559731921-14023-2-git-send-email-talel@amazon.com>

On Wed, Jun 05, 2019 at 01:52:00PM +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         | 22 ++++++++++++++++++++++
>  1 file changed, 22 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..a2f31a6
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/interrupt-controller/amazon,al-fic.txt
> @@ -0,0 +1,22 @@
> +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.
> +- interrupt-parent: specifies the parent interrupt controller.
> +- interrupts: describes which input line in the interrupt parent, this
> +  fic's output is connected to.
> +
> +Example:
> +
> +amazon_fic: amazon_fic {

above must be:

amazon_fic: interrupt-controller@0xfd8a8500 {

--
Regards,
Sudeep

  reply	other threads:[~2019-06-05 11:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 10:51 [PATCH v2 0/2] Amazon's Annapurna Labs Fabric Interrupt Controller Talel Shenhar
2019-06-05 10:51 ` Talel Shenhar
2019-06-05 10:52 ` [PATCH v2 1/2] dt-bindings: interrupt-controller: Amazon's Annapurna Labs FIC Talel Shenhar
2019-06-05 10:52   ` Talel Shenhar
2019-06-05 11:08   ` Sudeep Holla [this message]
2019-06-05 15:49   ` Eduardo Valentin
2019-06-05 15:49     ` Eduardo Valentin
2019-06-06  7:23     ` Shenhar, Talel
2019-06-06  7:23       ` Shenhar, Talel
2019-06-05 10:52 ` [PATCH v2 2/2] irqchip: al-fic: Introduce Amazon's Annapurna Labs Fabric Interrupt Controller Driver Talel Shenhar
2019-06-05 10:52   ` Talel Shenhar
2019-06-05 12:22   ` Marc Zyngier
2019-06-05 14:38     ` Shenhar, Talel
2019-06-05 14:38       ` Shenhar, Talel
2019-06-05 15:12       ` Marc Zyngier
2019-06-05 22:06         ` Benjamin Herrenschmidt
2019-06-06  7:05           ` Marc Zyngier
2019-06-06  7:05             ` Marc Zyngier
2019-06-06  7:49             ` Benjamin Herrenschmidt
2019-06-06  7:25         ` Shenhar, Talel
2019-06-06  7:25           ` Shenhar, Talel
2019-06-05 22:02     ` Benjamin Herrenschmidt
2019-06-06  7:10       ` Marc Zyngier
2019-06-06  7:10         ` Marc Zyngier
2019-06-05 12:50   ` Greg KH
2019-06-05 14:51     ` Shenhar, Talel
2019-06-05 14:51       ` Shenhar, Talel
2019-06-05 15:40       ` Greg KH
2019-06-05 14:56     ` David Woodhouse

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=20190605110855.GC20813@e107155-lin \
    --to=sudeep.holla@arm.com \
    --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=robh+dt@kernel.org \
    --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.