+David, Tony, Suman. Robert, Matthijs, Daniel,
On 28/01/19 21:15, Robert Nelson wrote: > On Mon, Jan 28, 2019 at 12:58 PM Daniel Kulp <d...@kulp.com> wrote: >> >> >> I tried to update our app image from the 4.14 bone kernel to the 4.19 bone >> kernel and ran into a big problem: uio_pruss is not configured in as it is >> with 4.14. Is this an oversight? Is there anyone I need to contact to try >> and convince them to re-enable uio_pruss? I'd like to get >> CONFIG_SND_DUMMY also enabled (module) as that would allow us to use some >> same configuration between Pi's and BBB's, but that's really minor. >> uio_pruss is a must-have. >> >> The ti kernels also don't have it, but I cannot use the ti kernels due to >> other timing reasons. Mostly concerned about the bone kernels right now. > > Actually, uio_pruss broke in v4.18.x... Congrats's your the first to > notice and mention it! ;) > > Roger @ TI with comments from David posted an RFC for ti's remotproc > for mainline.. That's what i have in v4.19.x-bone "today" (and > v4.20.x-bone/v5.0.x-bone).. This is the latest series that I posted for pruss remoteproc https://lkml.org/lkml/2019/2/4/677 I have been mostly focussing on remoteproc framework and PRU ethernet driver use case. I see that uio_pruss is important for the bone community. We will need to work together to make sure that it continues to operate when the PRUSS remoteproc stuff gets merged to kernel.org. I will keep you all in cc when I post v3 of the series so you can test uio_pruss.c and review the patches. Meanwhile, I'd like to understand what must be done to ensure uio_pruss.c is supported. We might need to make some changes to uio_pruss.c so that it can understand the device tree node (interrupts, memory regions) and do runtime_pm etc. It will be great if we don't have to make any device tree changes when switching between pruss_remoteproc and uio_pruss drivers. Just unbinding the current driver and binding the alternate driver should work. > > Last i looked at v4.19.x-bone and uio_pruss, you'll need to revert all > uio changes in v4.18.x/v4.19.x/etc.. (essentially revert that module > to v4.17.x) and it should work fine.. > > Regards, > cheers, -roger -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki -- 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/5C63FD64.8030205%40ti.com. For more options, visit https://groups.google.com/d/optout.
