mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: pavan_savoy@ti.com
To: gregkh@suse.de, linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk, pavan_savoy@sify.com,
	Pavan Savoy <pavan_savoy@ti.com>
Subject: [PATCH] drivers:staging:ti-st: update TODO
Date: Mon,  2 Aug 2010 02:43:17 -0500	[thread overview]
Message-ID: <1280734997-602-1-git-send-email-pavan_savoy@ti.com> (raw)

From: Pavan Savoy <pavan_savoy@ti.com>

Removed TODO item 2 :
Current UIM/KIM communicate via the rfkill device and identified by the unique idx
assisgned by the rfkill sub-system to each of these rfkill entries.

Removed TODO item 1 :
Since there is no way we can test existance of multiple connectivity
devices on  platform.
However the basic infrastructure as in providing a context to ST driver
exist.
If multiple devices have to exist on a given platform, multiple ST
platform devices need to be registered and each of the protocol drivers
have to mention which platform device they want to bind to/make use of.

Removed TODO item 3:
Locking have been reviewed and commit
36b5aee46b5e4788758409829926c631de0a64a3 documents locking.

Signed-off-by: Pavan Savoy <pavan_savoy@ti.com>
---
 drivers/staging/ti-st/TODO |   18 +-----------------
 1 files changed, 1 insertions(+), 17 deletions(-)

diff --git a/drivers/staging/ti-st/TODO b/drivers/staging/ti-st/TODO
index 6a105ed..ebfd6bb 100644
--- a/drivers/staging/ti-st/TODO
+++ b/drivers/staging/ti-st/TODO
@@ -1,22 +1,6 @@
 TODO:
 
-1. A per-device/tty port context required to support multiple devices
-on same platform.
-Plan: Each BT, FM and GPS device would be a platform-device with its platform-data
-mentioning which of the ST device it wants to attach itself onto.
-
-There by each of the ST device which is also a platform device upon receiving
-a st_register() would know whether the registration from BT/FM or GPS was intended for it.
-
-2. Improve upon the way requirement of line discipline is communicated to
-user-space, The current user-space application which open/installs ldisc
-as and when required can be found at,
-http://dev.omapzoom.org/pub/scm/jsistla/L23-btfm.git
-branch: UIM
-
-3. Re-view/Re-work on the locking.
-
-4. Step up and maintain this driver to ensure that it continues
+1. 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


                 reply	other threads:[~2010-08-02  7:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1280734997-602-1-git-send-email-pavan_savoy@ti.com \
    --to=pavan_savoy@ti.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavan_savoy@sify.com \
    /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®