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

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

2018-08-31 Thread Jon Flatley
specifies the values 'OVER_CURRENT_PORT' and 'OVER_CURRENT_COUNT' that indicate the path of the usb port where the over-current event occurred and the value of 'over_current_count' in sysfs. Additionally, call sysfs_notify() so the sysfs value supports poll(). Signed-off-by: Jon Flatley --- driver

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

2018-09-20 Thread Jon Flatley
On Thu, Sep 20, 2018 at 10:58 AM Greg KH wrote: > > On Thu, Sep 20, 2018 at 10:17:54AM -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

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

2018-09-20 Thread Jon Flatley
specifies the values 'OVER_CURRENT_PORT' and 'OVER_CURRENT_COUNT' that indicate the path of the usb port where the over-current event occurred and the value of 'over_current_count' in sysfs. Additionally, call sysfs_notify() so the sysfs value supports poll(). Signed-off-by: Jon Flatley --- Documen

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

2018-09-11 Thread Jon Flatley
specifies the values 'OVER_CURRENT_PORT' and 'OVER_CURRENT_COUNT' that indicate the path of the usb port where the over-current event occurred and the value of 'over_current_count' in sysfs. Additionally, call sysfs_notify() so the sysfs value supports poll(). Signed-off-by: Jon Flatley --- Documen