From: Marc Zyngier <maz@kernel.org>
To: Joakim Zhang <qiangqing.zhang@nxp.com>
Cc: Lokesh Vutla <lokeshvutla@ti.com>, <tglx@linutronix.de>,
<jason@lakedaemon.net>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <shawnguo@kernel.org>,
<s.hauer@pengutronix.de>, Andy Duan <fugang.duan@nxp.com>,
"S.j. Wang" <shengjiu.wang@nxp.com>,
<linux-kernel@vger.kernel.org>, dl-linux-imx <linux-imx@nxp.com>,
<kernel@pengutronix.de>, <linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH V3 2/2] drivers/irqchip: add NXP INTMUX interrupt multiplexer support
Date: Fri, 20 Dec 2019 14:20:07 +0000 [thread overview]
Message-ID: <8bc6bcf113cce13816c62c166f091785@www.loen.fr> (raw)
In-Reply-To: <DB7PR04MB4618B9A227807CCF884910C6E62D0@DB7PR04MB4618.eurprd04.prod.outlook.com>
On 2019-12-20 14:10, Joakim Zhang wrote:
>> -----Original Message-----
>> From: Lokesh Vutla <lokeshvutla@ti.com>
[...]
>> Does the user care to which channel does the interrupt source goes
>> to? If not,
>> interrupt-cells in DT can just be a single entry and the channel
>> selection can be
>> controlled by the driver no? I am trying to understand why user
>> should specify
>> the channel no.
> Hi Lokesh,
>
> If a fixed channel is specified in the driver, all interrupt sources
> will be connected to this channel, affecting the interrupt priority
> to
> some extent.
>
> From my point of view, a fixed channel could be enough if don't care
> interrupt priority.
Hold on a sec:
Is the channel to which an interrupt is routed to programmable? What
has
the priority of the interrupt to do with this? How does this affect
interrupt delivery?
It looks like this HW does more that you initially explained...
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2019-12-20 14:20 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
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 [this message]
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=8bc6bcf113cce13816c62c166f091785@www.loen.fr \
--to=maz@kernel.org \
--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=lokeshvutla@ti.com \
--cc=mark.rutland@arm.com \
--cc=qiangqing.zhang@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shengjiu.wang@nxp.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®