sysfs-platform-kim 1.9 KB

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