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