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