Re: [PATCH] usb: core: added uevent for over-current

2018-09-11 Thread Greg KH
On Mon, Sep 10, 2018 at 03:12:22PM -0700, Jon Flatley wrote: > On Mon, Sep 10, 2018 at 11:14 AM Greg KH wrote: > > > > On Fri, Aug 31, 2018 at 10:14:19AM -0700, Jon Flatley wrote: > > > After commit 1cbd53c8cd85 ("usb: core: introduce per-port over-current > > > counters") usb ports expose a sysfs

Re: [PATCH] usb: core: added uevent for over-current

2018-09-10 Thread Jon Flatley
On Mon, Sep 10, 2018 at 11:14 AM Greg KH wrote: > > On Fri, Aug 31, 2018 at 10:14:19AM -0700, Jon Flatley wrote: > > After commit 1cbd53c8cd85 ("usb: core: introduce per-port over-current > > counters") usb ports expose a sysfs value 'over_current_count' > > to user space. This value on its own is

Re: [PATCH] usb: core: added uevent for over-current

2018-09-10 Thread Greg KH
On Fri, Aug 31, 2018 at 10:14:19AM -0700, Jon Flatley wrote: > After commit 1cbd53c8cd85 ("usb: core: introduce per-port over-current > counters") usb ports expose a sysfs value 'over_current_count' > to user space. This value on its own is not very useful as it requires > manual polling. > > As a

[PATCH] usb: core: added uevent for over-current

2018-08-31 Thread Jon Flatley
After commit 1cbd53c8cd85 ("usb: core: introduce per-port over-current counters") usb ports expose a sysfs value 'over_current_count' to user space. This value on its own is not very useful as it requires manual polling. As a solution, fire a udev event from the usb hub device that specifies the v