Greg,

A quick test would be to revert the following patch (assuming you are using a 
BeagleBone variant) in your tree, if you continue to use your old firmware
https://github.com/beagleboard/linux/commit/620cab817e7a06065452d4c119c3066061ad5f03

regards
Suman


From: Greg [mailto:[email protected]]
Sent: Thursday, June 16, 2016 8:07 PM
To: BeagleBoard
Cc: [email protected]; [email protected]; Reeder, Jason; Anna, 
Suman
Subject: Re: [beagleboard] Ti's RPMsg Examples Significantly Changed

Hi Suman, that confirms what I suspected about this new module pruss_intc.
I am going to continue to experiment with the old and new PRU package and see 
if I can determine the problem.
I think I need to look at the device tree I am using and see if it has the 
required properties.

Regards,
Greg

On Thursday, June 16, 2016 at 8:02:08 PM UTC-4, Anna, Suman wrote:
Hi Greg,

Yes, we have introduced pruss_intc new on 4.4 kernel and this module now 
manages the PRUSS INTC. It provides the irqchip/irqdomain which will allow 
client users to use standard DT properties for listing the PRU system events as 
interrupts and use standard Linux APIs. There is still some more work to be 
done there (ability to add system event to PRU channel mapping to host 
interrupt from DT) rather than having to provide that mapping data in firmware 
resource table, so the MPU-side clients can be cleanly separated and depend on 
Linux infrastructure alone.

I am not sure how much the kernel you are using has caught up to the changes I 
have been doing on my tree, but there are a few changes over the last week 
where we added and switched over to PRU system events instead of mailboxes for 
scalability purposes (mailboxes would work too provided you choose mailboxes in 
DT over interrupts). This is what Jason was referring to as v5.0.0.

Regards
Suman

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/37C860A02101E749A747FA2D3C1E3C50040B7AF6%40DLEE11.ent.ti.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to