1 1) Write a DT binding doc and get the corresponding DT node merged to
4 This will let the driver probe when enabled.
6 2) Import drivers using VCHI.
8 VCHI is just a tool to let drivers talk to the firmware. Here are
9 some of the ones we want:
11 - vc_mem (https://github.com/raspberrypi/linux/blob/rpi-4.4.y/drivers/char/broadcom/vc_mem.c)
13 This driver is what the vcdbg userspace program uses to set up its
14 requests to the firmware, which are transmitted across VCHIQ. vcdbg
15 is really useful for debugging firmware interactions.
17 - bcm2835-camera (https://github.com/raspberrypi/linux/tree/rpi-4.4.y/drivers/media/platform/bcm2835)
19 This driver will let us get images from the camera using the MMAL
22 - VCSM (https://github.com/raspberrypi/linux/tree/rpi-4.4.y/drivers/char/broadcom/vc_sm)
24 This driver is used for talking about regions of VC memory across
25 firmware protocols including VCHI. We'll want to extend this driver
26 to manage these buffers as dmabufs so that we can zero-copy import
27 camera images into vc4 for rendering/display.
29 3) Garbage-collect unused code
31 One of the reasons this driver wasn't upstreamed previously was that
32 there's a lot code that got built that's probably unnecessary these
33 days. Once we have the set of VCHI-using drivers we want in tree, we
34 should be able to do a sweep of the code to see what's left that's