50 lines · plain
1What: /sys/devices/platform/kim/dev_name2Date: January 20103KernelVersion: 2.6.384Contact: "Pavan Savoy" <pavan_savoy@ti.com>5Description:6 Name of the UART device at which the WL128x chip7 is connected. example: "/dev/ttyS0".8 9 The device name flows down to architecture specific board10 initialization file from the ATAGS bootloader11 firmware. The name exposed is read from the user-space12 daemon and opens the device when install is requested.13 14What: /sys/devices/platform/kim/baud_rate15Date: January 201016KernelVersion: 2.6.3817Contact: "Pavan Savoy" <pavan_savoy@ti.com>18Description:19 The maximum reliable baud-rate the host can support.20 Different platforms tend to have different high-speed21 UART configurations, so the baud-rate needs to be set22 locally and also sent across to the WL128x via a HCI-VS23 command. The entry is read and made use by the user-space24 daemon when the ldisc install is requested.25 26What: /sys/devices/platform/kim/flow_cntrl27Date: January 201028KernelVersion: 2.6.3829Contact: "Pavan Savoy" <pavan_savoy@ti.com>30Description:31 The WL128x makes use of flow control mechanism, and this32 entry most often should be 1, the host's UART is required33 to have the capability of flow-control, or else this34 entry can be made use of for exceptions.35 36What: /sys/devices/platform/kim/install37Date: January 201038KernelVersion: 2.6.3839Contact: "Pavan Savoy" <pavan_savoy@ti.com>40Description:41 When one of the protocols Bluetooth, FM or GPS wants to make42 use of the shared UART transport, it registers to the shared43 transport driver, which will signal the user-space for opening,44 configuring baud and install line discipline via this sysfs45 entry. This entry would be polled upon by the user-space46 daemon managing the UART, and is notified about the change47 by the sysfs_notify. The value would be '1' when UART needs48 to be opened/ldisc installed, and would be '0' when UART49 is no more required and needs to be closed.50