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 From: Greg [mailto:soapy-sm...@comcast.net] Sent: Thursday, June 16, 2016 6:01 PM To: BeagleBoard Cc: jkrid...@beagleboard.org; Anna, Suman; Reeder, Jason Subject: Re: [beagleboard] Ti's RPMsg Examples Significantly Changed Hi Jason- I'm confused and I hope you can clear up things a bit. I've got the older version of the pru package which works with the mailbox. I was working with this just last week, and it compiled and worked perfectly with the rpmsg device appearing in /dev. This is the example (similar to lab 5) PRU_RPMsg_Echo_Interrupt0. I just updated the kernel to beaglebone 4.4.12-ti-r31. Unfortunately I did not record the former kernel in which everything ran OK. Now it is still compiling OK, but the firmwares do not run, as seen in dmesg. Anyway, the most interesting this is the appearance of a new loadable module. Here is a partial listing from lsmod: pru_rproc 12632 0 pruss_intc 7223 1 pru_rproc pruss 9408 0 This is the first time I have seen pruss_intc. Modinfo indicates that this is the work of Andrew F. Davis. Is this at least a partial release of what you describe as an "upcoming 4.4 kernel from TI"? Regards, Greg On Thursday, June 16, 2016 at 5:40:53 PM UTC-4, Jason Reeder wrote: John, Have you seen our PRU-ICSS landing page: http://processors.wiki.ti.com/index.php/PRU-ICSS and also the Remoteproc/rpmsg sub page on that wiki: http://processors.wiki.ti.com/index.php/PRU-ICSS_Remoteproc_and_RPMsg If so, let me know which parts are unclear/insufficient and I can work to improve those. Of course, all of the work and documentation on that wiki will be geared toward to the TI Processor SDK Linux distribution. Keep in mind that the latest changes to the pru-software-support-package rpmsg examples are tightly coupled to the current work that Suman is doing on an upcoming 4.4 kernel from TI. So the latest examples are not going to work until the Linux drivers are updated to use interrupts instead of mailboxes as well, which is why I revved the major version of the package to v5. I would love to see the pru-software-support-package and rpmsg pick up steam in the community. However, any work that would not benefit the TI Linux distribution directly will have to be done at home on my own time. I'm not opposed to that idea though as my Beaglebone Green Wireless just arrived in the mail this afternoon and I'll be needing to get more familiar with the community distribution anyway. Jason Reeder -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/37C860A02101E749A747FA2D3C1E3C50040B5629%40DLEE11.ent.ti.com. For more options, visit https://groups.google.com/d/optout.
