Re: [RFC] usbhid: fix error handling of not enough bandwidth

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

 



On Wed, 28 Mar 2012, Oliver Neukum wrote:

> From 22569602350f8992f2d2b321cf195e633e74574a Mon Sep 17 00:00:00 2001
> From: Oliver Neukum <oliver@xxxxxxxxxx>
> Date: Wed, 28 Mar 2012 10:37:05 +0200
> Subject: [PATCH] usbhid: fix error handling of not enough bandwidth
> 
> In case IO cannot be started because there is a lack of bandwidth
> on the bus, it makes no sense to reset the device. If IO is requested
> because the device is opened, user space should be notified with
> an error right away. If the lack of bandwidth arises later, for
> example after resume, there's no other choice but to retry in the
> hope that bandwidth will be freed.
> 
> Signed-off-by: Oliver Neukum <oneukum@xxxxxxx>
> ---
> 
> Unfortunately only XHCI implements check_bandwidth()
> I've seen this trigger on UHCI due to an error, but still, it can happen.

Ok, makes sense. I have applied it now. 

(not considering it important enough to trigger merge with Linus in 
current merge window though solely for the purpose of this patch though 
-- I have already flushed my merge window queue to Linus).

Thanks,

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


[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux