diff options
| author | Michael Zoran <mzoran@crowfest.net> | 2017-03-09 23:41:10 -0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-03-10 10:13:33 +0100 |
| commit | 82c41a994c1f4313ec595387a60d2360e42fdf3b (patch) | |
| tree | ae6ff45b98aeae6aedba1d319c049969fe270fb7 /drivers/staging/vc04_services | |
| parent | b8f93267628b22e452251a5f1913b069544b29f7 (diff) | |
staging: vchi: Remove ARM64 from TODO list
ARM64 for core vchiq which is the core of vc04_services should
now be work complete. The driver compiles without any errors
or warnings, and works just as well as 32 bit mode. The
necessary compatibility wrappers for the 32 bit ioctls have been
written and merged.
Since no more ARM64 specific changes should be needed, perhaps
it's best to remove it from the TODO list.
Signed-off-by: Michael Zoran <mzoran@crowfest.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/vc04_services')
| -rw-r--r-- | drivers/staging/vc04_services/interface/vchi/TODO | 21 |
1 files changed, 3 insertions, 18 deletions
diff --git a/drivers/staging/vc04_services/interface/vchi/TODO b/drivers/staging/vc04_services/interface/vchi/TODO index 03aa65183b25..df93154b1aa6 100644 --- a/drivers/staging/vc04_services/interface/vchi/TODO +++ b/drivers/staging/vc04_services/interface/vchi/TODO @@ -1,24 +1,9 @@ -1) Port to aarch64 - -This driver won't be very useful unless we also have it working on -Raspberry Pi 3. This requires, at least: - - - Figure out an alternative to the dmac_map_area() hack. - - - Decide what to use instead of dsb(). - - - Do something about (int) cast of bulk->data in - vchiq_bulk_transfer(). - - bulk->data is a bus address going across to the firmware. We know - our bus addresses are <32bit. - -2) Write a DT binding doc and get the corresponding DT node merged to +1) Write a DT binding doc and get the corresponding DT node merged to bcm2835. This will let the driver probe when enabled. -3) Import drivers using VCHI. +2) Import drivers using VCHI. VCHI is just a tool to let drivers talk to the firmware. Here are some of the ones we want: @@ -41,7 +26,7 @@ some of the ones we want: to manage these buffers as dmabufs so that we can zero-copy import camera images into vc4 for rendering/display. -4) Garbage-collect unused code +3) Garbage-collect unused code One of the reasons this driver wasn't upstreamed previously was that there's a lot code that got built that's probably unnecessary these |