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