From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Richard Leitner <dev@g0hl1n.net>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
stern@rowland.harvard.edu, linux@roeck-us.net,
mathias.nyman@linux.intel.com, johan@kernel.org,
felipe.balbi@linux.intel.com, ekorenevsky@gmail.com,
peter.chen@nxp.com, drake@endlessm.com, joe@perches.com,
Richard Leitner <richard.leitner@skidata.com>
Subject: [v3] usb: core: introduce per-port over-current counters
Date: Tue, 20 Mar 2018 09:34:05 +0100 [thread overview]
Message-ID: <20180320083405.GA23588@kroah.com> (raw)
On Wed, Mar 14, 2018 at 10:51:09AM +0100, Richard Leitner wrote:
> From: Richard Leitner <richard.leitner@skidata.com>
>
> For some userspace applications information on the number of
> over-current conditions at specific USB hub ports is relevant.
>
> In our case we have a series of USB hardware (using the cp210x driver)
> which communicates using a proprietary protocol. These devices sometimes
> trigger an over-current situation on some hubs. In case of such an
> over-current situation the USB devices offer an interface for reducing
> the max used power. As these conditions are quite rare and imply
> performance reductions of the device we don't want to reduce the max
> power always.
>
> Therefore give user-space applications the possibility to react
> adequately by introducing an over_current_counter in the usb port struct
> which is exported via sysfs.
>
> Signed-off-by: Richard Leitner <richard.leitner@skidata.com>
> ---
> Documentation/ABI/testing/sysfs-bus-usb | 10 ++++++++++
> drivers/usb/core/hub.c | 4 +++-
> drivers/usb/core/hub.h | 1 +
> drivers/usb/core/port.c | 10 ++++++++++
> 4 files changed, 24 insertions(+), 1 deletion(-)
What changed from the previous versions? Always include that below the
--- line so we have an idea of what is going on here.
v4?
thanks,
greg k-h
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Richard Leitner <dev@g0hl1n.net>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
stern@rowland.harvard.edu, linux@roeck-us.net,
mathias.nyman@linux.intel.com, johan@kernel.org,
felipe.balbi@linux.intel.com, ekorenevsky@gmail.com,
peter.chen@nxp.com, drake@endlessm.com, joe@perches.com,
Richard Leitner <richard.leitner@skidata.com>
Subject: Re: [PATCH v3] usb: core: introduce per-port over-current counters
Date: Tue, 20 Mar 2018 09:34:05 +0100 [thread overview]
Message-ID: <20180320083405.GA23588@kroah.com> (raw)
In-Reply-To: <20180314095109.18260-1-dev@g0hl1n.net>
On Wed, Mar 14, 2018 at 10:51:09AM +0100, Richard Leitner wrote:
> From: Richard Leitner <richard.leitner@skidata.com>
>
> For some userspace applications information on the number of
> over-current conditions at specific USB hub ports is relevant.
>
> In our case we have a series of USB hardware (using the cp210x driver)
> which communicates using a proprietary protocol. These devices sometimes
> trigger an over-current situation on some hubs. In case of such an
> over-current situation the USB devices offer an interface for reducing
> the max used power. As these conditions are quite rare and imply
> performance reductions of the device we don't want to reduce the max
> power always.
>
> Therefore give user-space applications the possibility to react
> adequately by introducing an over_current_counter in the usb port struct
> which is exported via sysfs.
>
> Signed-off-by: Richard Leitner <richard.leitner@skidata.com>
> ---
> Documentation/ABI/testing/sysfs-bus-usb | 10 ++++++++++
> drivers/usb/core/hub.c | 4 +++-
> drivers/usb/core/hub.h | 1 +
> drivers/usb/core/port.c | 10 ++++++++++
> 4 files changed, 24 insertions(+), 1 deletion(-)
What changed from the previous versions? Always include that below the
--- line so we have an idea of what is going on here.
v4?
thanks,
greg k-h
next reply other threads:[~2018-03-20 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 8:34 Greg Kroah-Hartman [this message]
2018-03-20 8:34 ` [PATCH v3] usb: core: introduce per-port over-current counters Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-03-14 9:51 [v3] " Richard Leitner
2018-03-14 9:51 ` [PATCH v3] " Richard Leitner
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=20180320083405.GA23588@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dev@g0hl1n.net \
--cc=drake@endlessm.com \
--cc=ekorenevsky@gmail.com \
--cc=felipe.balbi@linux.intel.com \
--cc=joe@perches.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mathias.nyman@linux.intel.com \
--cc=peter.chen@nxp.com \
--cc=richard.leitner@skidata.com \
--cc=stern@rowland.harvard.edu \
/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.