mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: Joakim Zhang <qiangqing.zhang@nxp.com>, <maz@kernel.org>,
	<tglx@linutronix.de>, <jason@lakedaemon.net>,
	<robh+dt@kernel.org>, <mark.rutland@arm.com>,
	<shawnguo@kernel.org>, <s.hauer@pengutronix.de>
Cc: <fugang.duan@nxp.com>, <linux-kernel@vger.kernel.org>,
	<linux-imx@nxp.com>, <kernel@pengutronix.de>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V3 1/2] dt-bindings/irq: add binding for NXP INTMUX interrupt multiplexer
Date: Fri, 20 Dec 2019 17:10:26 +0530	[thread overview]
Message-ID: <0cecd3af-8bca-c0d3-1312-925624c63dbf@ti.com> (raw)
In-Reply-To: <1576827431-31942-2-git-send-email-qiangqing.zhang@nxp.com>



On 20/12/19 1:07 PM, Joakim Zhang wrote:
> This patch adds the DT bindings for the NXP INTMUX interrupt multiplexer
> for i.MX8 family SoCs.
> 
> Signed-off-by: Joakim Zhang <qiangqing.zhang@nxp.com>
> ---
>  .../interrupt-controller/fsl,intmux.txt       | 36 +++++++++++++++++++
>  1 file changed, 36 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,intmux.txt
> 
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/fsl,intmux.txt b/Documentation/devicetree/bindings/interrupt-controller/fsl,intmux.txt
> new file mode 100644
> index 000000000000..3ebe9cac5f20
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/interrupt-controller/fsl,intmux.txt
> @@ -0,0 +1,36 @@
> +Freescale INTMUX interrupt multiplexer
> +
> +Required properties:
> +
> +- compatible: Should be:
> +   - "fsl,imx-intmux"
> +- reg: Physical base address and size of registers.
> +- interrupts: Should contain the parent interrupt lines (up to 8) used to
> +  multiplex the input interrupts.
> +- clocks: Should contain one clock for entry in clock-names.
> +- clock-names:
> +   - "ipg": main logic clock
> +- interrupt-controller: Identifies the node as an interrupt controller.
> +- #interrupt-cells: Specifies the number of cells needed to encode an
> +  interrupt source. The value must be 2.
> +   - the 1st cell: hardware interrupt number> +   - the 2nd cell: channel index, value must smaller than channels used

As per the xlate function, 1st cell is channel index and 2nd cell is hw
interrupt number no?

Thanks and regards,
Lokesh

> +
> +Optional properties:
> +
> +- fsl,intmux_chans: The number of channels used for interrupt source. The
> +  Maximum value is 8. If this property is not set in DT then driver uses
> +  1 channel by default.
> +
> +Example:
> +
> +	intmux@37400000 {
> +		compatible = "fsl,imx-intmux";
> +		reg = <0x37400000 0x1000>;
> +		interrupts = <GIC_SPI 16 IRQ_TYPE_LEVEL_HIGH>;
> +		clocks = <&clk IMX8QM_CM40_IPG_CLK>;
> +		clock-names = "ipg";
> +		interrupt-controller;
> +		#interrupt-cells = <1>;
> +	};
> +
> 

  parent reply	other threads:[~2019-12-20 11:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20  7:37 [PATCH V3 0/2] irqchip: add NXP INTMUX interrupt controller Joakim Zhang
2019-12-20  7:37 ` [PATCH V3 1/2] dt-bindings/irq: add binding for NXP INTMUX interrupt multiplexer Joakim Zhang
2019-12-20  7:44   ` Joakim Zhang
2019-12-20 11:40   ` Lokesh Vutla [this message]
2019-12-20 12:30     ` Lokesh Vutla
2019-12-20  7:37 ` [PATCH V3 2/2] drivers/irqchip: add NXP INTMUX interrupt multiplexer support Joakim Zhang
2019-12-20 10:49   ` Marc Zyngier
2019-12-20 11:59     ` Joakim Zhang
2019-12-20 11:45   ` Lokesh Vutla
2019-12-20 14:10     ` Joakim Zhang
2019-12-20 14:20       ` Marc Zyngier
2019-12-20 15:26         ` Joakim Zhang
2019-12-20 15:35           ` Joakim Zhang
2019-12-23 10:10           ` Lokesh Vutla
2019-12-23 11:11             ` Joakim Zhang

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=0cecd3af-8bca-c0d3-1312-925624c63dbf@ti.com \
    --to=lokeshvutla@ti.com \
    --cc=fugang.duan@nxp.com \
    --cc=jason@lakedaemon.net \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=qiangqing.zhang@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --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®