From: Rob Herring <robh@kernel.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Jason Cooper" <jason@lakedaemon.net>,
"Marc Zyngier" <marc.zyngier@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, "Roc He" <hepeng@zidoo.tv>,
蒋丽琴 <jiang.liqin@geniatech.com>,
"Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: Re: [RFC 1/3] dt-bindings: interrupt-controller: Add Realtek RTD1295
Date: Mon, 21 Aug 2017 21:14:59 -0500 [thread overview]
Message-ID: <20170822021459.l3oiid3f4fs6vfa2@rob-hp-laptop> (raw)
In-Reply-To: <20170817101140.32000-2-afaerber@suse.de>
On Thu, Aug 17, 2017 at 12:11:38PM +0200, Andreas Färber wrote:
> Add binding for Realtek RTD1295 IRQ mux.
>
> Signed-off-by: Andreas Färber <afaerber@suse.de>
> ---
> .../interrupt-controller/realtek,rtd119x-mux.txt | 28 ++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/realtek,rtd119x-mux.txt
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/realtek,rtd119x-mux.txt b/Documentation/devicetree/bindings/interrupt-controller/realtek,rtd119x-mux.txt
> new file mode 100644
> index 000000000000..4b43370e3d74
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/interrupt-controller/realtek,rtd119x-mux.txt
> @@ -0,0 +1,28 @@
> +Realtek RTD119x/129x IRQ Mux Controller
> +=======================================
> +
> +Required properties:
> +
> +- compatible : Should be one of the following:
> + - "realtek,rtd1295-irq-mux"
> + - "realtek,rtd1295-iso-irq-mux"
> +- reg : Specifies base physical address and size of the registers.
> +- interrupts : Specifies the interrupt line which is mux'ed.
> +- interrupt-controller : Presence indicates the node as interrupt controller.
> +- #interrupt-cells : Shall be 1. See common bindings in interrupt.txt.
> +
> +
> +Optional properties:
> +
> +See interrupt.txt for common bindings.
What else would apply here? interrupt-parent is the only thing I see,
but that's really implicit anyway.
> +
> +
> +Example:
> +
> + interrupt-controller@98007000 {
> + compatible = "realtek,rtd1295-iso-irq-mux";
> + reg = <0x98007000 0x100>;
> + interrupts = <GIC_SPI 41 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-controller;
> + #interrupt-cells = <1>;
> + };
> --
> 2.12.3
>
next prev parent reply other threads:[~2017-08-22 2:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 10:11 [RFC 0/3] arm64: Realtek RTD1295 IRQ mux Andreas Färber
2017-08-17 10:11 ` [RFC 1/3] dt-bindings: interrupt-controller: Add Realtek RTD1295 Andreas Färber
2017-08-22 2:14 ` Rob Herring [this message]
2017-08-25 19:41 ` Andreas Färber
2017-08-17 10:11 ` [RFC 2/3] arm64: dts: realtek: Add irq mux to RTD1295 Andreas Färber
2017-08-17 10:11 ` [RFC 3/3] irqchip: Add Realtek RTD1295 mux driver Andreas Färber
2017-08-18 10:53 ` Marc Zyngier
2017-08-18 17:21 ` Andreas Färber
2017-08-18 17:47 ` Marc Zyngier
2017-08-20 1:44 ` Andreas Färber
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=20170822021459.l3oiid3f4fs6vfa2@rob-hp-laptop \
--to=robh@kernel.org \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=hepeng@zidoo.tv \
--cc=jason@lakedaemon.net \
--cc=jiang.liqin@geniatech.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®