[RFC] Remaining drivers in RPI github tree/which drivers to submit

Michael Zoran mzoran at crowfest.net
Fri Feb 3 11:31:26 PST 2017


On Fri, 2017-02-03 at 13:15 +0100, Stefan Wahren wrote:
> Am 03.02.2017 um 00:13 schrieb Michael Zoran:
> > On Thu, 2017-02-02 at 19:02 +0100, Stefan Wahren wrote:
> 
> I currently prepare and test OTG/Peripheral support for dwc2 on
> bcm2835
> since the latest changes for 4.11.
> 
> I would be happy if you could verify with RPi 3 / ARM64 that nothing
> is
> broken.

Sure, but I doubt those drivers have any ARM64 dependencies.

> > I think vc_cma, vc_mem, and vc_sm need to go into staging
> > IMHO.  That
> > way all the vchiq based drivers would be in staging, and it would
> > be
> > possible to start stripping out parts of vchiq and simplifying it. 
> > Which IMHO, is the biggest blocker of progress with vchiq.
> > 
> > I was planning to submit vc_cma, vc_mem, and vc_sm tonight if
> > nobody
> > has any objections.
> 
> I unterstand your intention, but this also means that those drivers
> needs to be maintained (in parallel to the downstream drivers).
> 
> Are their any users from kernel perspective of these drivers?
> 

No, not really. The TODO mentions vcdbg.  I loaded it up once, but
didn't find it very useful.



More information about the linux-rpi-kernel mailing list