summaryrefslogtreecommitdiffstats
path: root/drivers/staging/ti-st
diff options
context:
space:
mode:
authorPavan Savoy <pavan_savoy@ti.com>2010-07-28 02:26:00 -0500
committerGreg Kroah-Hartman <gregkh@suse.de>2010-07-28 08:20:56 -0700
commit9f912212cd005f9a0a514ae982de915ff94bd765 (patch)
tree2d627c9026e92c1130e66336790e542231f71dcc /drivers/staging/ti-st
parentc1afac1502c4e519e6a1df08a5d9a2391d00388b (diff)
downloadop-kernel-dev-9f912212cd005f9a0a514ae982de915ff94bd765.zip
op-kernel-dev-9f912212cd005f9a0a514ae982de915ff94bd765.tar.gz
Staging: ti-st: update ABI and TODO
update TODO to reflect the items taken care of, update ABI to reflect the new debugfs entries exposed. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/staging/ti-st')
-rw-r--r--drivers/staging/ti-st/TODO10
-rw-r--r--drivers/staging/ti-st/sysfs-uim12
2 files changed, 15 insertions, 7 deletions
diff --git a/drivers/staging/ti-st/TODO b/drivers/staging/ti-st/TODO
index 3f68ea1..6a105ed 100644
--- a/drivers/staging/ti-st/TODO
+++ b/drivers/staging/ti-st/TODO
@@ -11,16 +11,12 @@ a st_register() would know whether the registration from BT/FM or GPS was intend
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://git.omapzoom.org/?p˙atform/hardware/ti/omap3.git;a˙ob;f˙_st/uim/uim.c;ha16c2c2b5085eb54a1bbc7096d779d7594eb11;hbělair
+http://dev.omapzoom.org/pub/scm/jsistla/L23-btfm.git
+branch: UIM
3. Re-view/Re-work on the locking.
-4. Re-structure to make the ldisc driver more generic for chipsets which mux
-multiple connectivity (BT, FM, GPS) upon 1 TTY port.
-
-5. Remove global references by providing a context which can be moved around the driver like the other ldisc drivers. (ldiscs tend to use tty's disc_data and platform devices use the device's driver data)
-
-6. Step up and maintain this driver to ensure that it continues
+4. 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.
diff --git a/drivers/staging/ti-st/sysfs-uim b/drivers/staging/ti-st/sysfs-uim
index 10311af..626bda5 100644
--- a/drivers/staging/ti-st/sysfs-uim
+++ b/drivers/staging/ti-st/sysfs-uim
@@ -14,3 +14,15 @@ Description:
uninstallation would be ppolling on this device and listening
on events which would suggest either to install or un-install
line discipline
+
+What: /sys/kernel/debug/ti-st/version
+Contact: Pavan Savoy <pavan_savoy@ti.com>
+Description:
+ WiLink chip's ROM version exposed to user-space for some
+ proprietary protocol stacks to make use of.
+
+What: /sys/kernel/debug/ti-st/protocols
+Contact: Pavan Savoy <pavan_savoy@ti.com>
+Description:
+ The reason for chip being ON, the list of protocols registered.
+
OpenPOWER on IntegriCloud