[ +cc GregKH, JiriS ]
On 03/04/2015 12:54, Peter Hurley wrote:
On 04/02/2015 10:37 AM, Frederic Danis wrote:
This allows user space application to set final speed requested for UART
device. UART port is open at init speed by user space application.
If userspace opened the tty and knows this is a UART, why can it not
use the for-purpose tty ioctls to change the line rate?
The purpose of this Bluetooth set of patches is to move device setup for
Bluetooth UART devices into the kernel.
The idea is that userspace only needs to open the tty at initial speed
and set correct line discipline, then userspace has no more to do, its
up to HCI UART driver to manage the device (including firmware loading,
bluetooth address and device speed setup).
However the driver may want to modify device speed (by using vendor
specific HCI commands) to operate at full speed. Moreover, in case of
firmware loading, some devices reset their speed to the default one,
which will imply to change UART host speed to be able to continue
communication.
Userspace can not know when all those speed changes occur.
Regards
Fred
--
Frederic Danis Open Source Technology Center
frederic.danis@xxxxxxxxx Intel Corporation
--
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
