Home
last modified time | relevance | path

Searched hist:"02303 f73373aa1da19dbec510ec5a4e2576f9610" (Results 1 – 4 of 4) sorted by relevance

/openbmc/linux/drivers/usb/serial/
H A Dusb-wwan.hdiff 02303f73373aa1da19dbec510ec5a4e2576f9610 Fri Nov 19 16:04:00 CST 2010 Dan Williams <dcbw@redhat.com> usb-wwan: implement TIOCGSERIAL and TIOCSSERIAL to avoid blocking close(2)

Some devices (ex ZTE 2726) simply don't respond at all when data is sent
to some of their USB interfaces. The data gets stuck in the TTYs queue
and sits there until close(2), which them blocks because closing_wait
defaults to 30 seconds (even though the fd is O_NONBLOCK). This is
rarely desired. Implement the standard mechanism to adjust closing_wait
and let applications handle it how they want to.

Signed-off-by: Dan Williams <dcbw@redhat.com>
H A Dusb_wwan.cdiff 02303f73373aa1da19dbec510ec5a4e2576f9610 Fri Nov 19 16:04:00 CST 2010 Dan Williams <dcbw@redhat.com> usb-wwan: implement TIOCGSERIAL and TIOCSSERIAL to avoid blocking close(2)

Some devices (ex ZTE 2726) simply don't respond at all when data is sent
to some of their USB interfaces. The data gets stuck in the TTYs queue
and sits there until close(2), which them blocks because closing_wait
defaults to 30 seconds (even though the fd is O_NONBLOCK). This is
rarely desired. Implement the standard mechanism to adjust closing_wait
and let applications handle it how they want to.

Signed-off-by: Dan Williams <dcbw@redhat.com>
H A Doption.cdiff 02303f73373aa1da19dbec510ec5a4e2576f9610 Fri Nov 19 16:04:00 CST 2010 Dan Williams <dcbw@redhat.com> usb-wwan: implement TIOCGSERIAL and TIOCSSERIAL to avoid blocking close(2)

Some devices (ex ZTE 2726) simply don't respond at all when data is sent
to some of their USB interfaces. The data gets stuck in the TTYs queue
and sits there until close(2), which them blocks because closing_wait
defaults to 30 seconds (even though the fd is O_NONBLOCK). This is
rarely desired. Implement the standard mechanism to adjust closing_wait
and let applications handle it how they want to.

Signed-off-by: Dan Williams <dcbw@redhat.com>
/openbmc/linux/drivers/usb/class/
H A Dcdc-acm.cdiff ba2d8ce9db0a61505362bb17b8899df3d3326146 Thu Nov 08 12:47:41 CST 2012 Dan Williams <dcbw@redhat.com> cdc-acm: implement TIOCSSERIAL to avoid blocking close(2)

Some devices (ex Nokia C7) simply don't respond at all when data is sent
to some of their USB interfaces. The data gets stuck in the TTYs queue
and sits there until close(2), which them blocks because closing_wait
defaults to 30 seconds (even though the fd is O_NONBLOCK). This is
rarely desired. Implement the standard mechanism to adjust closing_wait
and let applications handle it how they want to.

See also 02303f73373aa1da19dbec510ec5a4e2576f9610 for usb_wwan.c.

Signed-off-by: Dan Williams <dcbw@redhat.com>
Cc: stable <stable@vger.kernel.org>
Acked-by: Oliver Neukum <oneukum@suse.de>
Tested-by: Aleksander Morgado <aleksander@gnu.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>