1*4882a593SmuzhiyunWhat: /sys/devices/platform/kim/dev_name 2*4882a593SmuzhiyunDate: January 2010 3*4882a593SmuzhiyunKernelVersion: 2.6.38 4*4882a593SmuzhiyunContact: "Pavan Savoy" <pavan_savoy@ti.com> 5*4882a593SmuzhiyunDescription: 6*4882a593Smuzhiyun Name of the UART device at which the WL128x chip 7*4882a593Smuzhiyun is connected. example: "/dev/ttyS0". 8*4882a593Smuzhiyun 9*4882a593Smuzhiyun The device name flows down to architecture specific board 10*4882a593Smuzhiyun initialization file from the SFI/ATAGS bootloader 11*4882a593Smuzhiyun firmware. The name exposed is read from the user-space 12*4882a593Smuzhiyun dameon and opens the device when install is requested. 13*4882a593Smuzhiyun 14*4882a593SmuzhiyunWhat: /sys/devices/platform/kim/baud_rate 15*4882a593SmuzhiyunDate: January 2010 16*4882a593SmuzhiyunKernelVersion: 2.6.38 17*4882a593SmuzhiyunContact: "Pavan Savoy" <pavan_savoy@ti.com> 18*4882a593SmuzhiyunDescription: 19*4882a593Smuzhiyun The maximum reliable baud-rate the host can support. 20*4882a593Smuzhiyun Different platforms tend to have different high-speed 21*4882a593Smuzhiyun UART configurations, so the baud-rate needs to be set 22*4882a593Smuzhiyun locally and also sent across to the WL128x via a HCI-VS 23*4882a593Smuzhiyun command. The entry is read and made use by the user-space 24*4882a593Smuzhiyun daemon when the ldisc install is requested. 25*4882a593Smuzhiyun 26*4882a593SmuzhiyunWhat: /sys/devices/platform/kim/flow_cntrl 27*4882a593SmuzhiyunDate: January 2010 28*4882a593SmuzhiyunKernelVersion: 2.6.38 29*4882a593SmuzhiyunContact: "Pavan Savoy" <pavan_savoy@ti.com> 30*4882a593SmuzhiyunDescription: 31*4882a593Smuzhiyun The WL128x makes use of flow control mechanism, and this 32*4882a593Smuzhiyun entry most often should be 1, the host's UART is required 33*4882a593Smuzhiyun to have the capability of flow-control, or else this 34*4882a593Smuzhiyun entry can be made use of for exceptions. 35*4882a593Smuzhiyun 36*4882a593SmuzhiyunWhat: /sys/devices/platform/kim/install 37*4882a593SmuzhiyunDate: January 2010 38*4882a593SmuzhiyunKernelVersion: 2.6.38 39*4882a593SmuzhiyunContact: "Pavan Savoy" <pavan_savoy@ti.com> 40*4882a593SmuzhiyunDescription: 41*4882a593Smuzhiyun When one of the protocols Bluetooth, FM or GPS wants to make 42*4882a593Smuzhiyun use of the shared UART transport, it registers to the shared 43*4882a593Smuzhiyun transport driver, which will signal the user-space for opening, 44*4882a593Smuzhiyun configuring baud and install line discipline via this sysfs 45*4882a593Smuzhiyun entry. This entry would be polled upon by the user-space 46*4882a593Smuzhiyun daemon managing the UART, and is notified about the change 47*4882a593Smuzhiyun by the sysfs_notify. The value would be '1' when UART needs 48*4882a593Smuzhiyun to be opened/ldisc installed, and would be '0' when UART 49*4882a593Smuzhiyun is no more required and needs to be closed. 50