[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bcd89c7e-ab26-f84f-9fe9-8a4958437c04@arm.com>
Date: Mon, 11 Mar 2019 10:51:04 +0000
From: Marc Zyngier <marc.zyngier@....com>
To: Lina Iyer <ilina@...eaurora.org>, swboyd@...omium.org,
evgreen@...omium.org
Cc: linux-kernel@...r.kernel.org, rplsssn@...eaurora.org,
linux-arm-msm@...r.kernel.org, thierry.reding@...il.com,
bjorn.andersson@...aro.org, dianders@...omium.org,
linus.walleij@...aro.org
Subject: Re: [PATCH v3 3/9] of: irq: add helper to remap interrupts to another
irqdomain
On 22/02/2019 22:18, Lina Iyer wrote:
> From: Stephen Boyd <swboyd@...omium.org>
>
> Sometimes interrupts are routed from an interrupt controller to another
> in no specific order. Having these in the drives makes it difficult to
s/drives/driver/ ?
> maintain when the same drivers supports multiple variants with different
> mapping. Also, specifying them in DT makes little sense with a
> bunch of numbers like -
> <0, 13>, <5, 32>,
> It makes more sense when we can have the parent handle along with
> interrupt specificers for the incoming interrupt as well as that of the
specifiers
> outgoing interrupt like -
> <22 0 &intc 36 0>,
> <24 0 &intc 37 0>,
> <26 0 &intc 38 0>,
> And the interrupt specifiers can be interpred using these properties -
interpreted
> irqdomain-map-mask = <0xff 0>;
> irqdomain-map-pass-thru = <0 0xff>;
Talking about interpretation, can you please expand on how these should
be used? You definitely want to have this documented as a generic
binding somewhere.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
Powered by blists - more mailing lists