[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19fbf4f6-ea75-3eb7-7e95-c7c9ce987996@lechnology.com>
Date: Fri, 31 Jul 2020 09:09:49 -0500
From: David Lechner <david@...hnology.com>
To: Grzegorz Jaszczyk <grzegorz.jaszczyk@...aro.org>
Cc: tglx@...utronix.de, jason@...edaemon.net,
Marc Zyngier <maz@...nel.org>, "Anna, Suman" <s-anna@...com>,
robh+dt@...nel.org, Lee Jones <lee.jones@...aro.org>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
"Mills, William" <wmills@...com>,
"Bajjuri, Praneeth" <praneeth@...com>,
"Andrew F . Davis" <afd@...com>, Roger Quadros <rogerq@...com>
Subject: Re: [PATCH v4 1/5] dt-bindings: irqchip: Add PRU-ICSS interrupt
controller bindings
On 7/31/20 6:48 AM, Grzegorz Jaszczyk wrote:
> On Wed, 29 Jul 2020 at 19:34, David Lechner <david@...hnology.com> wrote:
>> It is not clear what the meaning of each cell is. Looking at later patches, it
>> looks like the first cell is the PRU system event number, the second cell is the
>> channel and the third cell is the host event number.
>
> Ok, how about updating above description like this:
> Client users shall use the PRU System event number (the interrupt source
> that the client is interested in) [cell 1], PRU channel [cell 2] and PRU
> host_intr (target) [cell 3] as the value of the interrupts property in their
> node. The system events can be mapped to some output host interrupts through 2
> levels of many-to-one mapping i.e. events to channel mapping and channels to
> host interrupts so through this property entire mapping is provided.
Cell 3 is host_intr0-7? How would we map to other host events?
Powered by blists - more mailing lists