From: Rob Herring <robh@kernel.org>
To: Phil Edworthy <phil.edworthy@renesas.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Mark Rutland <mark.rutland@arm.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings/interrupt-controller: rzn1: Add RZ/N1 gpio irq mux binding
Date: Sat, 17 Nov 2018 08:32:53 -0600 [thread overview]
Message-ID: <20181117143253.GA27381@bogus> (raw)
In-Reply-To: <20181113130910.22130-2-phil.edworthy@renesas.com>
On Tue, Nov 13, 2018 at 01:09:09PM +0000, Phil Edworthy wrote:
> Add device binding documentation for the Renesas RZ/N1 GPIO interrupt
> multiplexer.
>
> Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
> ---
> v3:
> - Use 'interrupt-map' DT property correctly.
> v2:
> - Use interrupt-map to allow the GPIO controller info to be specified
> as part of the irq.
> - Don't show status in binding examples.
> - Don't show the soc/board split in binding doc.
> ---
> .../interrupt-controller/renesas,rzn1-mux.txt | 73 +++++++++++++++++++
> 1 file changed, 73 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/renesas,rzn1-mux.txt
A few nits, otherwise:
Reviewed-by: Rob Herring <robh@kernel.org>
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/renesas,rzn1-mux.txt b/Documentation/devicetree/bindings/interrupt-controller/renesas,rzn1-mux.txt
> new file mode 100644
> index 000000000000..6515880e25cc
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/interrupt-controller/renesas,rzn1-mux.txt
> @@ -0,0 +1,73 @@
> +* Renesas RZ/N1 GPIO Interrupt Multiplexer
> +
> +On Renesas RZ/N1 devices, there are several GPIO Controllers each with a number
> +of interrupt outputs. All of the interrupts from the GPIO Controllers are passed
> +to the GPIO Interrupt Multiplexer, which selects a sub-set of the interrupts to
> +pass onto the system interrupt controller.
> +
> +A single node in the device tree is used to describe the GPIO IRQ Muxer.
> +
> +Required properties:
> +- compatible: SoC-specific compatible string "renesas,<soc-specific>-gpioirqmux"
> + followed by "renesas,rzn1-gpioirqmux" as fallback. The SoC-specific compatible
> + strings must be one of:
> + "renesas,r9a06g032-gpioirqmux" for RZ/N1D
> + "renesas,r9a06g033-gpioirqmux" for RZ/N1S
> +- reg: Base address and size of GPIO IRQ Muxer registers.
> +- interrupts: List of output interrupts.
> +- #interrupt-cells: Numder of cells in the input interrupt specifier, must be 1.
> +- #address-cells: Must be 0.
> +- interrupt-map-mask: must be 127.
> +- interrupt-map: Standard property detailing the maps between input irqs and the
> + corresponding output irq. This consist of a list of:
> + <input-irq-spec phandle-to-interrupt-controller output-irq-spec>
> + The input-irq-spec is from 0 to 95, corresponding to the outputs of the GPIO
> + Controllers.
> +
> +Example:
> +
> + The following is an example for the RZ/N1D SoC.
> +
> + gpioirqmux: gpioirqmux@51000480 {
interrupt-controller@...
> + compatible = "renesas,r9a06g032-gpioirqmux",
> + "renesas,rzn1-gpioirqmux";
> + reg = <0x51000480 0x20>;
> + interrupts =
> + <GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 104 IRQ_TYPE_LEVEL_HIGH>;
This is a bit redundant as the same information is in interrupt-map, but
I guess you need it to get the irq resources.
> +
> + #interrupt-cells = <1>;
> + #address-cells = <0>;
> + interrupt-map-mask = <127>;
Use hex for masks.
> + interrupt-map =
> + /* gpio2a 24, pin 146: ETH Port 1 IRQ */
> + <88 &gic GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>,
> + /* gpio2a 26, pin 148: TouchSCRN_IRQ */
> + <90 &gic GIC_SPI 104 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> + gpio2: gpio@5000d000 {
> + compatible = "snps,dw-apb-gpio";
> + reg = <0x5000d000 0x80>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + clock-names = "bus";
> + clocks = <&sysctrl R9A06G032_HCLK_GPIO2>;
> +
> + gpio2a: gpio-controller@0 {
gpio@0
> + compatible = "snps,dw-apb-gpio-port";
> + bank-name = "gpio2a";
> + gpio-controller;
> + #gpio-cells = <2>;
> + snps,nr-gpios = <32>;
> + reg = <0>;
> +
> + interrupt-controller;
> + interrupt-parent = <&gpioirqmux>;
> + interrupts = < 64 65 66 67 68 69 70 71
> + 72 73 74 75 76 77 78 79
> + 80 81 82 83 84 85 86 87
> + 88 89 90 91 92 93 94 95 >;
> + #interrupt-cells = <2>;
> + };
> + };
> --
> 2.17.1
>
next prev parent reply other threads:[~2018-11-17 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 13:09 [PATCH v3 0/2] irqchip: Add support for Renesas RZ/N1 GPIO interrupt multiplexer Phil Edworthy
2018-11-13 13:09 ` [PATCH v3 1/2] dt-bindings/interrupt-controller: rzn1: Add RZ/N1 gpio irq mux binding Phil Edworthy
2018-11-17 14:32 ` Rob Herring [this message]
2018-11-19 9:39 ` Phil Edworthy
2018-11-19 21:50 ` Rob Herring
2018-11-20 10:30 ` Phil Edworthy
2018-11-13 13:09 ` [PATCH v3 2/2] irqchip: Add support for Renesas RZ/N1 GPIO interrupt multiplexer Phil Edworthy
2019-02-19 15:27 ` Phil Edworthy
2019-02-19 15:39 ` Marc Zyngier
2019-02-19 15:41 ` Phil Edworthy
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=20181117143253.GA27381@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=phil.edworthy@renesas.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;
as well as URLs for NNTP newsgroup(s).