---

yaml
---
r: 206012
b: refs/heads/master
c: 9f91221
h: refs/heads/master
v: v3

[refs]

@@ -1,2 +1,2 @@
 ---
-refs/heads/master: c1afac1502c4e519e6a1df08a5d9a2391d00388b
+refs/heads/master: 9f912212cd005f9a0a514ae982de915ff94bd765

trunk/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.

trunk/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.
+