Back to home page

OSCL-LXR

 
 

    


0001 What:           /sys/devices/platform/kim/dev_name
0002 Date:           January 2010
0003 KernelVersion:  2.6.38
0004 Contact:        "Pavan Savoy" <pavan_savoy@ti.com>
0005 Description:
0006                 Name of the UART device at which the WL128x chip
0007                 is connected. example: "/dev/ttyS0".
0008 
0009                 The device name flows down to architecture specific board
0010                 initialization file from the ATAGS bootloader
0011                 firmware. The name exposed is read from the user-space
0012                 dameon and opens the device when install is requested.
0013 
0014 What:           /sys/devices/platform/kim/baud_rate
0015 Date:           January 2010
0016 KernelVersion:  2.6.38
0017 Contact:        "Pavan Savoy" <pavan_savoy@ti.com>
0018 Description:
0019                 The maximum reliable baud-rate the host can support.
0020                 Different platforms tend to have different high-speed
0021                 UART configurations, so the baud-rate needs to be set
0022                 locally and also sent across to the WL128x via a HCI-VS
0023                 command. The entry is read and made use by the user-space
0024                 daemon when the ldisc install is requested.
0025 
0026 What:           /sys/devices/platform/kim/flow_cntrl
0027 Date:           January 2010
0028 KernelVersion:  2.6.38
0029 Contact:        "Pavan Savoy" <pavan_savoy@ti.com>
0030 Description:
0031                 The WL128x makes use of flow control mechanism, and this
0032                 entry most often should be 1, the host's UART is required
0033                 to have the capability of flow-control, or else this
0034                 entry can be made use of for exceptions.
0035 
0036 What:           /sys/devices/platform/kim/install
0037 Date:           January 2010
0038 KernelVersion:  2.6.38
0039 Contact:        "Pavan Savoy" <pavan_savoy@ti.com>
0040 Description:
0041                 When one of the protocols Bluetooth, FM or GPS wants to make
0042                 use of the shared UART transport, it registers to the shared
0043                 transport driver, which will signal the user-space for opening,
0044                 configuring baud and install line discipline via this sysfs
0045                 entry. This entry would be polled upon by the user-space
0046                 daemon managing the UART, and is notified about the change
0047                 by the sysfs_notify. The value would be '1' when UART needs
0048                 to be opened/ldisc installed, and would be '0' when UART
0049                 is no more required and needs to be closed.