On Fri, Feb 15, 2019 at 2:00 AM Suman Anna wrote:
> Mark, Linus,
>
> So, I hope it is clear from Roger's responses that above assertions do
> not hold true to this INTC, and so want to confirm that we are good with
> the current non-hierarchical design.
IIUC the 64 lines are latched onto 8 lines
On Thu, 14 Feb 2019 at 12:08, Roger Quadros wrote:
> The beagleboard community is a primary user of this driver and we need to
> find a solution so that PRUSS is usable either via remoteproc or via UIO.
While being able to switch drivers without changing the DT by forcibly
binding a different dri
Hi Tony,
On 2/14/19 9:56 AM, Tony Lindgren wrote:
> * Roger Quadros [190214 11:09]:
>> Suman is mainly concerned about the following changes in v2
>> 1) pruss node does not contain reg property representing entire ICSS.
>> 2) pruss node does not contain interrupts.
>>
>> Both of these are require
Hi Roger,
On 2/14/19 5:08 AM, Roger Quadros wrote:
> +Robert, Dan, Matthijs
>
> Hi Suman,
>
> On 14/02/19 04:52, Suman Anna wrote:
>> Hi Roger,
>>
>> On 2/4/19 8:22 AM, Roger Quadros wrote:
>>> From: Suman Anna
>>>
>>> This patch adds the bindings for the Programmable Real-Time Unit
>>> and Ind
On 2/14/19 9:48 AM, Roger Quadros wrote:
> fixed DTML id.
>
> On 14/02/19 17:44, Roger Quadros wrote:
>> On 14/02/19 14:52, Marc Zyngier wrote:
>>> On Thu, 14 Feb 2019 10:55:10 +,
>>> Roger Quadros wrote:
On 14/02/19 10:37, Linus Walleij wrote:
> On Thu, Feb 14, 2019 at 4:1
On 14/02/19 17:51, Marc Zyngier wrote:
> On 14/02/2019 15:44, Roger Quadros wrote:
>> On 14/02/19 14:52, Marc Zyngier wrote:
>>> On Thu, 14 Feb 2019 10:55:10 +,
>>> Roger Quadros wrote:
On 14/02/19 10:37, Linus Walleij wrote:
> On Thu, Feb 14, 2019 at 4:13 AM Suman Anna
* Roger Quadros [190214 11:09]:
> Suman is mainly concerned about the following changes in v2
> 1) pruss node does not contain reg property representing entire ICSS.
> 2) pruss node does not contain interrupts.
>
> Both of these are required if drivers/uio/uio_pruss.c or in future if
> VFIO is to
On 14/02/2019 15:44, Roger Quadros wrote:
> On 14/02/19 14:52, Marc Zyngier wrote:
>> On Thu, 14 Feb 2019 10:55:10 +,
>> Roger Quadros wrote:
>>>
>>>
>>> On 14/02/19 10:37, Linus Walleij wrote:
On Thu, Feb 14, 2019 at 4:13 AM Suman Anna wrote:
> [Me]
>> To be able to use hie
fixed DTML id.
On 14/02/19 17:44, Roger Quadros wrote:
> On 14/02/19 14:52, Marc Zyngier wrote:
>> On Thu, 14 Feb 2019 10:55:10 +,
>> Roger Quadros wrote:
>>>
>>>
>>> On 14/02/19 10:37, Linus Walleij wrote:
On Thu, Feb 14, 2019 at 4:13 AM Suman Anna wrote:
> [Me]
>> To be a
On 14/02/19 14:52, Marc Zyngier wrote:
> On Thu, 14 Feb 2019 10:55:10 +,
> Roger Quadros wrote:
>>
>>
>> On 14/02/19 10:37, Linus Walleij wrote:
>>> On Thu, Feb 14, 2019 at 4:13 AM Suman Anna wrote:
[Me]
>>>
> To be able to use hierarchical interrupt domain in the kernel, the top
>>>
+Robert, Dan, Matthijs
Hi Suman,
On 14/02/19 04:52, Suman Anna wrote:
> Hi Roger,
>
> On 2/4/19 8:22 AM, Roger Quadros wrote:
>> From: Suman Anna
>>
>> This patch adds the bindings for the Programmable Real-Time Unit
>> and Industrial Communication Subsystem (PRU-ICSS) present on various
>> SoC
On 14/02/19 10:37, Linus Walleij wrote:
> On Thu, Feb 14, 2019 at 4:13 AM Suman Anna wrote:
>> [Me]
>
>>> To be able to use hierarchical interrupt domain in the kernel, the top
>>> interrupt controller must use the hierarchical (v2) irqdomain, so
>>> if this is anything else than the ARM GIC it
On Thu, Feb 14, 2019 at 4:13 AM Suman Anna wrote:
> [Me]
> > To be able to use hierarchical interrupt domain in the kernel, the top
> > interrupt controller must use the hierarchical (v2) irqdomain, so
> > if this is anything else than the ARM GIC it will be an interesting
> > undertaking to hand
On 2/8/19 7:51 AM, Linus Walleij wrote:
> On Mon, Feb 4, 2019 at 3:24 PM Roger Quadros wrote:
>
>> From: Suman Anna
>>
>> This patch adds the bindings for the Programmable Real-Time Unit
>> and Industrial Communication Subsystem (PRU-ICSS) present on various
>> SoCs such as AM33xx, AM437x, AM57x
On 2/5/19 10:41 AM, Tony Lindgren wrote:
> * Roger Quadros [190205 09:40]:
>> On 04/02/19 18:33, Tony Lindgren wrote:
>>>
>>> shrdram2: memory@1 {
>>> device_type = "memory";
>>> reg = <0x1 0x3000>;
>>> };
>>
>> Shared RAM is not so straight forward. Both PR
Hi Roger,
On 2/4/19 8:22 AM, Roger Quadros wrote:
> From: Suman Anna
>
> This patch adds the bindings for the Programmable Real-Time Unit
> and Industrial Communication Subsystem (PRU-ICSS) present on various
> SoCs such as AM33xx, AM437x, AM57xx, Keystone 66AK2G SoC, etc. It is
> present on the
On 2/6/19 9:04 AM, Roger Quadros wrote:
>
>
> On 05/02/19 18:19, Tony Lindgren wrote:
>> * Murali Karicheri [190205 16:13]:
>>> On 02/05/2019 10:41 AM, Roger Quadros wrote:
What I'm suggesting here is that kernel remoteproc driver should have
nothing to do
with the other PRU's da
On Mon, Feb 4, 2019 at 3:24 PM Roger Quadros wrote:
> From: Suman Anna
>
> This patch adds the bindings for the Programmable Real-Time Unit
> and Industrial Communication Subsystem (PRU-ICSS) present on various
> SoCs such as AM33xx, AM437x, AM57xx, Keystone 66AK2G SoC, etc. It is
> present on t
On 05/02/19 18:19, Tony Lindgren wrote:
> * Murali Karicheri [190205 16:13]:
>> On 02/05/2019 10:41 AM, Roger Quadros wrote:
>>> What I'm suggesting here is that kernel remoteproc driver should have
>>> nothing to do
>>> with the other PRU's data RAM.
>>>
>>> The application driver if needs bo
* Roger Quadros [190205 09:40]:
> On 04/02/19 18:33, Tony Lindgren wrote:
> >
> > shrdram2: memory@1 {
> > device_type = "memory";
> > reg = <0x1 0x3000>;
> > };
>
> Shared RAM is not so straight forward. Both PRU firmwares and both
> application drivers
* Murali Karicheri [190205 16:13]:
> On 02/05/2019 10:41 AM, Roger Quadros wrote:
> > What I'm suggesting here is that kernel remoteproc driver should have
> > nothing to do
> > with the other PRU's data RAM.
> >
> > The application driver if needs both PRUs then it can obviously access both
>
Roger,
On 02/05/2019 10:41 AM, Roger Quadros wrote:
Murali,
On 05/02/19 17:08, Murali Karicheri wrote:
Hi Roger,
On 02/05/2019 04:39 AM, Roger Quadros wrote:
Hi Tony & Suman,
On 04/02/19 18:33, Tony Lindgren wrote:
Hi,
* Roger Quadros [190204 14:23]:
From: Suman Anna
...
+Example:
+=
Murali,
On 05/02/19 17:08, Murali Karicheri wrote:
> Hi Roger,
>
> On 02/05/2019 04:39 AM, Roger Quadros wrote:
>> Hi Tony & Suman,
>>
>> On 04/02/19 18:33, Tony Lindgren wrote:
>>> Hi,
>>>
>>> * Roger Quadros [190204 14:23]:
From: Suman Anna
>>> ...
+Example:
+
+1.
Hi Roger,
On 02/05/2019 04:39 AM, Roger Quadros wrote:
Hi Tony & Suman,
On 04/02/19 18:33, Tony Lindgren wrote:
Hi,
* Roger Quadros [190204 14:23]:
From: Suman Anna
...
+Example:
+
+1. /* AM33xx PRU-ICSS */
+
+ pruss: pruss@0 {
+ compatible = "ti,am3356-pr
Hi Tony & Suman,
On 04/02/19 18:33, Tony Lindgren wrote:
> Hi,
>
> * Roger Quadros [190204 14:23]:
>> From: Suman Anna
> ...
>> +Example:
>> +
>> +1. /* AM33xx PRU-ICSS */
>> +
>> +pruss: pruss@0 {
>> +compatible = "ti,am3356-pruss";
>> +reg = <0x0 0x2000>,
Hi,
* Roger Quadros [190204 14:23]:
> From: Suman Anna
...
> +Example:
> +
> +1. /* AM33xx PRU-ICSS */
> +
> + pruss: pruss@0 {
> + compatible = "ti,am3356-pruss";
> + reg = <0x0 0x2000>,
> + <0x2000 0x2000>,
> + <0x1
From: Suman Anna
This patch adds the bindings for the Programmable Real-Time Unit
and Industrial Communication Subsystem (PRU-ICSS) present on various
SoCs such as AM33xx, AM437x, AM57xx, Keystone 66AK2G SoC, etc. It is
present on the Davinci based OMAPL138 SoCs and K3 architecture
based AM65x So
27 matches
Mail list logo
