All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Flatley <jflat@chromium.org>
Cc: linux-usb@vger.kernel.org
Subject: [v2] usb: core: added uevent for over-current
Date: Thu, 20 Sep 2018 13:11:37 +0200	[thread overview]
Message-ID: <20180920111137.GA16430@kroah.com> (raw)

On Tue, Sep 11, 2018 at 10:43:10AM -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 solution, fire a udev event from the usb hub device that 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 <jflat@chromium.org>
> ---
>  Documentation/ABI/testing/sysfs-bus-usb |  9 ++++++-
>  drivers/usb/core/hub.c                  | 36 +++++++++++++++++++++++++
>  2 files changed, 44 insertions(+), 1 deletion(-)

This patch doesn't apply against my usb-next branch at the moment.

Can you rebase it and resend?

thanks,

greg k-h

             reply	other threads:[~2018-09-20 11:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20 11:11 Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-09-11 17:43 [v2] usb: core: added uevent for over-current Jon Flatley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180920111137.GA16430@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jflat@chromium.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.