summaryrefslogtreecommitdiffstats
path: root/drivers/staging/media/bcm2048/TODO
diff options
context:
space:
mode:
authorHans Verkuil <hans.verkuil@cisco.com>2013-11-04 08:37:34 -0300
committerMauro Carvalho Chehab <m.chehab@samsung.com>2013-12-09 10:12:05 -0200
commitd44250fd17de6dea2b16e23d2767ab0eff48f4d8 (patch)
treed591e2890ff6e4eeace6f1bf60aae571e069721f /drivers/staging/media/bcm2048/TODO
parent899127b67df098e6d878f27be05dc91401cc6685 (diff)
downloadop-kernel-dev-d44250fd17de6dea2b16e23d2767ab0eff48f4d8.zip
op-kernel-dev-d44250fd17de6dea2b16e23d2767ab0eff48f4d8.tar.gz
[media] bcm2048: add TODO file for this staging driver
Describe the tasks to be done for this driver to be promoted to a non-staging one. [m.chehab@samsung.com: Add a patch description; add a note about the CodingStyle issues and make sure that the README lines are not bigger than 80 cols.] Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com> Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
Diffstat (limited to 'drivers/staging/media/bcm2048/TODO')
-rw-r--r--drivers/staging/media/bcm2048/TODO24
1 files changed, 24 insertions, 0 deletions
diff --git a/drivers/staging/media/bcm2048/TODO b/drivers/staging/media/bcm2048/TODO
new file mode 100644
index 0000000..051f85d
--- /dev/null
+++ b/drivers/staging/media/bcm2048/TODO
@@ -0,0 +1,24 @@
+TODO:
+
+From the initial code review:
+
+The main thing you need to do is to implement all the controls using the
+control framework (see Documentation/video4linux/v4l2-controls.txt).
+Most drivers are by now converted to the control framework, so you will
+find many examples of how to do this in drivers/media/radio.
+
+The sysfs stuff should be replaced by controls as well. A lot of the RDS
+support is now available as controls (although there may well be some
+missing features, but that is easy enough to add). Since the RDS data is
+actually read() from the device I am not sure whether the RDS
+properties/controls should be there at all.
+
+Correct Coding Style, as this driver also violates several Style
+rules, and do evil tricks, like returning from a function inside a
+macro.
+
+Finally this driver should probably be split up into two parts: one
+v4l2_subdev-based core driver and one platform driver. See e.g.
+radio-si4713/si4713-i2c.c as a good example. But I would wait with that
+until the rest of the driver is cleaned up. Then I have a better idea of
+whether this is necessary or not.
OpenPOWER on IntegriCloud