On Fri, 11 Mar 2011, Paul Bolle wrote: > On a laptop I see these errors on (most) resumes: > hub 3-0:1.0: over-current change on port 1 > hub 3-0:1.0: over-current change on port 2 > > Since over-current conditions can disappear quite quickly it's better to > downgrade that message to debug level, recheck for an over-current > condition a little later and only print and over-current condition error > if that condition (still) exists when it's rechecked. > > Add similar logic to hub over-current changes. (That code is untested, > as those changes do not occur on this laptop.) > > Signed-off-by: Paul Bolle <pebolle@xxxxxxxxxx> > --- > Changes in v2: > - adapted to Alan's and Sergei's comments. I don't get over-current events on my hardware, so I can't really test this. But it looks perfectly sound. Acked-by: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
