[RFC] wilink8-bluetooth: reading uart parametrs and enable pin info from device tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



All,

The wl18xx family of chips include a Bluetooth subsystem which uses a UART 
for HCI communication and a gpio as an enable pin.

See the following architecture diagram:
http://www.ti.com/general/docs/datasheetdiagram.tsp?genericPartNumber=WL1837MOD&diagramId=SWRS170H

In case we want to build an image that when it boots up, Bluetooth is enbled 
out of the box we can pass this info to a user space app/script that would pick 
the selected gpio, enable it and launch the bleutooth stack (using hciattach).

The question is what would be the right practice for passing these parameters.
As there is no kernel driver looking for this info and it is needed mainly 
By user space, should we use something like the chosen node?
If yes, would it be right to add a new chosen node entry, or just add additional
Parameters to bootargs?
Any other suggestion?

Best Regards,
Eyal Reizer



--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux