From: manjunatha_halli@ti.com
To: mchehab@infradead.org, hverkuil@xs4all.nl
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
Manjunatha Halli <manjunatha_halli@ti.com>
Subject: [RFC v5 9/9] driver:staging:ti-st: Update TODO for FM V4L2 driver.
Date: Mon, 29 Nov 2010 09:18:43 -0500 [thread overview]
Message-ID: <1291040323-2641-10-git-send-email-manjunatha_halli@ti.com> (raw)
In-Reply-To: <1291040323-2641-9-git-send-email-manjunatha_halli@ti.com>
From: Manjunatha Halli <manjunatha_halli@ti.com>
Signed-off-by: Manjunatha Halli <manjunatha_halli@ti.com>
---
drivers/staging/ti-st/TODO | 17 ++++++++++++++++-
1 files changed, 16 insertions(+), 1 deletions(-)
diff --git a/drivers/staging/ti-st/TODO b/drivers/staging/ti-st/TODO
index ebfd6bb..1d004cb 100644
--- a/drivers/staging/ti-st/TODO
+++ b/drivers/staging/ti-st/TODO
@@ -1,6 +1,21 @@
TODO:
-1. Step up and maintain this driver to ensure that it continues
+1. Upstreaming BT driver
+
+2. Upstreaming FM driver
+
+ a. Use the new V4L2 control framework for all the V4L2 controls supported.
+
+ b. Change the interrupt handling mechanism as per comments by 'Hans Verkuil'.
+
+ c. Remove use of new V4L2 CID to set the BAND (US/JAPAN). Instead handle it
+ in driver.
+
+ d. Remove the new private CID defined for channel spacing instead handle it
+ in ioctl VIDIOC_S_HW_FREQ_SEEK.
+
+
+3. Step up and maintain this driver to ensure that it continues
to work. Having the hardware for this is pretty much a
requirement. If this does not happen, the will be removed in
the 2.6.35 kernel release.
--
1.5.6.3
prev parent reply other threads:[~2010-11-29 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 14:18 [RFC v5 0/9] FM V4L2 drivers for WL128x manjunatha_halli
2010-11-29 14:18 ` [RFC v5 1/9] include:linux: videodev2.h: FM Rx control class manjunatha_halli
2010-11-29 14:18 ` [RFC v5 2/9] Documentation:DocBook:v4l: Update the controls.xml for TI FM driver manjunatha_halli
2010-11-29 14:18 ` [RFC v5 3/9] drivers:staging: ti-st: fmdrv common header file manjunatha_halli
2010-11-29 14:18 ` [RFC v5 4/9] drivers:staging: ti-st: fmdrv_v4l2 sources manjunatha_halli
2010-11-29 14:18 ` [RFC v5 5/9] drivers:staging: ti-st: fmdrv_common sources manjunatha_halli
2010-11-29 14:18 ` [RFC v5 6/9] drivers:staging: ti-st: fmdrv_rx sources manjunatha_halli
2010-11-29 14:18 ` [RFC v5 7/9] drivers:staging: ti-st: fmdrv_tx sources manjunatha_halli
2010-11-29 14:18 ` [RFC v5 8/9] drivers:staging: ti-st: Kconfig & Makefile change manjunatha_halli
2010-11-29 14:18 ` manjunatha_halli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1291040323-2641-10-git-send-email-manjunatha_halli@ti.com \
--to=manjunatha_halli@ti.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®