From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Richard Leitner <dev@g0hl1n.net>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, stern@rowland.harvard.edu,
linux@roeck-us.net, mathias.nyman@linux.intel.com,
johan@kernel.org, ekorenevsky@gmail.com, peter.chen@nxp.com,
drake@endlessm.com, joe@perches.com,
Richard Leitner <richard.leitner@skidata.com>
Subject: Re: [PATCH v2] usb: core: introduce per-port over-current counters
Date: Tue, 20 Feb 2018 13:55:54 +0200 [thread overview]
Message-ID: <87k1v7q3hx.fsf@linux.intel.com> (raw)
In-Reply-To: <20180220115033.29496-1-dev@g0hl1n.net>
Hi,
Richard Leitner <dev@g0hl1n.net> writes:
> 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.
why don't you just provide more than one configuration with several
bMaxPower fields? Then host OS should choose correct configuration based
on power budget.
--
balbi
next prev parent reply other threads:[~2018-02-20 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 11:50 [PATCH v2] usb: core: introduce per-port over-current counters Richard Leitner
2018-02-20 11:55 ` Felipe Balbi [this message]
2018-02-20 12:14 ` Richard Leitner
2018-03-09 17:19 ` Greg KH
2018-03-13 10:20 ` 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=87k1v7q3hx.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=dev@g0hl1n.net \
--cc=drake@endlessm.com \
--cc=ekorenevsky@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox