diff options
author | Michael Zoran <mzoran@crowfest.net> | 2017-02-27 15:35:13 -0800 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-03-06 09:17:07 +0100 |
commit | 212afb97efe15b5b1b596a746fb6042e6f9b36a9 (patch) | |
tree | 1f9c126b399bc0dd104afda959e16c5e99a712c9 /drivers/staging/vc04_services/bcm2835-camera/TODO | |
parent | 051420a997a58fcf87fd71650ffe2e4d89f6757e (diff) | |
download | op-kernel-dev-212afb97efe15b5b1b596a746fb6042e6f9b36a9.zip op-kernel-dev-212afb97efe15b5b1b596a746fb6042e6f9b36a9.tar.gz |
staging: bcm2835-camera: Move driver under vc04_services
The bcm2835-camera driver is part of v04_services, so it makes
sense for it to be located under vc04_services to make
configuration clearer.
Signed-off-by: Michael Zoran <mzoran@crowfest.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/vc04_services/bcm2835-camera/TODO')
-rw-r--r-- | drivers/staging/vc04_services/bcm2835-camera/TODO | 39 |
1 files changed, 39 insertions, 0 deletions
diff --git a/drivers/staging/vc04_services/bcm2835-camera/TODO b/drivers/staging/vc04_services/bcm2835-camera/TODO new file mode 100644 index 0000000..61a5099 --- /dev/null +++ b/drivers/staging/vc04_services/bcm2835-camera/TODO @@ -0,0 +1,39 @@ +1) Support dma-buf memory management. + +In order to zero-copy import camera images into the 3D or display +pipelines, we need to export our buffers through dma-buf so that the +vc4 driver can import them. This may involve bringing in the VCSM +driver (which allows long-term management of regions of memory in the +space that the VPU reserved and Linux otherwise doesn't have access +to), or building some new protocol that allows VCSM-style management +of Linux's CMA memory. + +2) Avoid extra copies for padding of images. + +We expose V4L2_PIX_FMT_* formats that have a specified stride/height +padding in the V4L2 spec, but that padding doesn't match what the +hardware can do. If we exposed the native padding requirements +through the V4L2 "multiplanar" formats, the firmware would have one +less copy it needed to do. + +3) Port to ARM64 + +The bulk_receive() does some manual cache flushing that are 32-bit ARM +only, which we should convert to proper cross-platform APIs. + +4) Convert to be a platform driver. + +Right now when the module probes, it tries to initialize VCHI and +errors out if it wasn't ready yet. If bcm2835-v4l2 was built in, then +VCHI generally isn't ready because it depends on both the firmware and +mailbox drivers having already loaded. + +We should have VCHI create a platform device once it's initialized, +and have this driver bind to it, so that we automatically load the +v4l2 module after VCHI loads. + +5) Drop the gstreamer workaround. + +This was a temporary workaround for a bug that was fixed mid-2014, and +we should remove it before stabilizing the driver. + |