diff options
| author | Pavan Savoy <pavan_savoy@ti.com> | 2010-08-02 03:43:17 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2010-08-02 21:28:40 -0400 |
| commit | b12d1995f650e92f26184afd28e6cf40bf64467a (patch) | |
| tree | 063761deeb146f5132ceab2f4dbfe26ae925ce6d | |
| parent | 100ca122870844d6c001d5d0532b885c707b6ea9 (diff) | |
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
36b5aee46b5e4788758409829926c631de0a64a3 documents locking.
Signed-off-by: Pavan Savoy <pavan_savoy@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| -rw-r--r-- | 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 6a105ed1c384..ebfd6bb60176 100644 --- a/drivers/staging/ti-st/TODO +++ b/drivers/staging/ti-st/TODO | |||
| @@ -1,22 +1,6 @@ | |||
| 1 | TODO: | 1 | TODO: |
| 2 | 2 | ||
| 3 | 1. A per-device/tty port context required to support multiple devices | 3 | 1. Step up and maintain this driver to ensure that it continues |
| 4 | on same platform. | ||
| 5 | Plan: Each BT, FM and GPS device would be a platform-device with its platform-data | ||
| 6 | mentioning which of the ST device it wants to attach itself onto. | ||
| 7 | |||
| 8 | There by each of the ST device which is also a platform device upon receiving | ||
| 9 | a st_register() would know whether the registration from BT/FM or GPS was intended for it. | ||
| 10 | |||
| 11 | 2. Improve upon the way requirement of line discipline is communicated to | ||
| 12 | user-space, The current user-space application which open/installs ldisc | ||
| 13 | as and when required can be found at, | ||
| 14 | http://dev.omapzoom.org/pub/scm/jsistla/L23-btfm.git | ||
| 15 | branch: UIM | ||
| 16 | |||
| 17 | 3. Re-view/Re-work on the locking. | ||
| 18 | |||
| 19 | 4. Step up and maintain this driver to ensure that it continues | ||
| 20 | to work. Having the hardware for this is pretty much a | 4 | to work. Having the hardware for this is pretty much a |
| 21 | requirement. If this does not happen, the will be removed in | 5 | requirement. If this does not happen, the will be removed in |
| 22 | the 2.6.35 kernel release. | 6 | the 2.6.35 kernel release. |