Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit b12d1995 authored by Pavan Savoy's avatar Pavan Savoy Committed by Greg Kroah-Hartman
Browse files

Staging: ti-st: update TODO 



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
36b5aee4 documents locking.

Signed-off-by: default avatarPavan Savoy <pavan_savoy@ti.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
parent 100ca122

drivers/staging/ti-st/TODO

+1 −17
Original line number Original line Diff line number Diff line 
TODO:

TODO:





1. A per-device/tty port context required to support multiple devices

1. Step up and maintain this driver to ensure that it continues

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

to work.  Having the hardware for this is pretty much a

to work.  Having the hardware for this is pretty much a

requirement.  If this does not happen, the will be removed in

requirement.  If this does not happen, the will be removed in

the 2.6.35 kernel release.

the 2.6.35 kernel release.