leandrof/linux
1
0
Fork 0
forked from Minki/linux
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Staging: ti-st: update TODO

Browse Source 
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
36b5aee46b documents locking.

Signed-off-by: Pavan Savoy <pavan_savoy@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
This commit is contained in:
Pavan Savoy 2010-08-02 02:43:17 -05:00 committed by Greg Kroah-Hartman
parent 100ca12287
commit b12d1995f6
1 changed files with 1 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
drivers/staging/ti-st/TODO
View File

@ -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.