18c2ecf20Sopenharmony_ciWhat: /sys/devices/platform/kim/dev_name 28c2ecf20Sopenharmony_ciDate: January 2010 38c2ecf20Sopenharmony_ciKernelVersion: 2.6.38 48c2ecf20Sopenharmony_ciContact: "Pavan Savoy" <pavan_savoy@ti.com> 58c2ecf20Sopenharmony_ciDescription: 68c2ecf20Sopenharmony_ci Name of the UART device at which the WL128x chip 78c2ecf20Sopenharmony_ci is connected. example: "/dev/ttyS0". 88c2ecf20Sopenharmony_ci 98c2ecf20Sopenharmony_ci The device name flows down to architecture specific board 108c2ecf20Sopenharmony_ci initialization file from the SFI/ATAGS bootloader 118c2ecf20Sopenharmony_ci firmware. The name exposed is read from the user-space 128c2ecf20Sopenharmony_ci dameon and opens the device when install is requested. 138c2ecf20Sopenharmony_ci 148c2ecf20Sopenharmony_ciWhat: /sys/devices/platform/kim/baud_rate 158c2ecf20Sopenharmony_ciDate: January 2010 168c2ecf20Sopenharmony_ciKernelVersion: 2.6.38 178c2ecf20Sopenharmony_ciContact: "Pavan Savoy" <pavan_savoy@ti.com> 188c2ecf20Sopenharmony_ciDescription: 198c2ecf20Sopenharmony_ci The maximum reliable baud-rate the host can support. 208c2ecf20Sopenharmony_ci Different platforms tend to have different high-speed 218c2ecf20Sopenharmony_ci UART configurations, so the baud-rate needs to be set 228c2ecf20Sopenharmony_ci locally and also sent across to the WL128x via a HCI-VS 238c2ecf20Sopenharmony_ci command. The entry is read and made use by the user-space 248c2ecf20Sopenharmony_ci daemon when the ldisc install is requested. 258c2ecf20Sopenharmony_ci 268c2ecf20Sopenharmony_ciWhat: /sys/devices/platform/kim/flow_cntrl 278c2ecf20Sopenharmony_ciDate: January 2010 288c2ecf20Sopenharmony_ciKernelVersion: 2.6.38 298c2ecf20Sopenharmony_ciContact: "Pavan Savoy" <pavan_savoy@ti.com> 308c2ecf20Sopenharmony_ciDescription: 318c2ecf20Sopenharmony_ci The WL128x makes use of flow control mechanism, and this 328c2ecf20Sopenharmony_ci entry most often should be 1, the host's UART is required 338c2ecf20Sopenharmony_ci to have the capability of flow-control, or else this 348c2ecf20Sopenharmony_ci entry can be made use of for exceptions. 358c2ecf20Sopenharmony_ci 368c2ecf20Sopenharmony_ciWhat: /sys/devices/platform/kim/install 378c2ecf20Sopenharmony_ciDate: January 2010 388c2ecf20Sopenharmony_ciKernelVersion: 2.6.38 398c2ecf20Sopenharmony_ciContact: "Pavan Savoy" <pavan_savoy@ti.com> 408c2ecf20Sopenharmony_ciDescription: 418c2ecf20Sopenharmony_ci When one of the protocols Bluetooth, FM or GPS wants to make 428c2ecf20Sopenharmony_ci use of the shared UART transport, it registers to the shared 438c2ecf20Sopenharmony_ci transport driver, which will signal the user-space for opening, 448c2ecf20Sopenharmony_ci configuring baud and install line discipline via this sysfs 458c2ecf20Sopenharmony_ci entry. This entry would be polled upon by the user-space 468c2ecf20Sopenharmony_ci daemon managing the UART, and is notified about the change 478c2ecf20Sopenharmony_ci by the sysfs_notify. The value would be '1' when UART needs 488c2ecf20Sopenharmony_ci to be opened/ldisc installed, and would be '0' when UART 498c2ecf20Sopenharmony_ci is no more required and needs to be closed. 50