From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Richard Leitner <richard.leitner@skidata.com>
Cc: Richard Leitner <dev@g0hl1n.net>,
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
Subject: usb: core: introduce per-port over-current counters
Date: Mon, 19 Feb 2018 17:38:56 +0100 [thread overview]
Message-ID: <20180219163856.GA6171@kroah.com> (raw)
On Mon, Feb 19, 2018 at 05:05:34PM +0100, Richard Leitner wrote:
>
> On 02/19/2018 04:59 PM, Greg KH wrote:
> > On Mon, Feb 19, 2018 at 01:01:07PM +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. Therefore
> >> introduce a oc_counter in the usb port struct which is exported via
> >> sysfs.
> >>
> >> Signed-off-by: Richard Leitner <richard.leitner@skidata.com>
> >> ---
> >> Tested on an i.MX6DL based board.
> >> ---
> >> drivers/usb/core/hub.c | 4 +++-
> >> drivers/usb/core/hub.h | 1 +
> >> drivers/usb/core/port.c | 10 ++++++++++
> >> 3 files changed, 14 insertions(+), 1 deletion(-)
> >
> > When you add/remove/modify a sysfs attribute, you always have to
> > document in Documentation/ABI/
>
> Ok. Thank you. Seems I missed that, Sorry!
>
> >>
> >> diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
> >> index c5c1f6cf3228..448fba1e1827 100644
> >> --- a/drivers/usb/core/hub.c
> >> +++ b/drivers/usb/core/hub.c
> >> @@ -5104,8 +5104,10 @@ static void port_event(struct usb_hub *hub, int port1)
> >>
> >> if (portchange & USB_PORT_STAT_C_OVERCURRENT) {
> >> u16 status = 0, unused;
> >> + port_dev->oc_count++;
> >>
> >> - dev_dbg(&port_dev->dev, "over-current change\n");
> >> + dev_dbg(&port_dev->dev, "over-current change #%u\n",
> >> + port_dev->oc_count);
> >> usb_clear_port_feature(hdev, port1,
> >> USB_PORT_FEAT_C_OVER_CURRENT);
> >> msleep(100); /* Cool down */
> >> diff --git a/drivers/usb/core/hub.h b/drivers/usb/core/hub.h
> >> index 2a700ccc868c..b5cf567bf9e2 100644
> >> --- a/drivers/usb/core/hub.h
> >> +++ b/drivers/usb/core/hub.h
> >> @@ -100,6 +100,7 @@ struct usb_port {
> >> unsigned int is_superspeed:1;
> >> unsigned int usb3_lpm_u1_permit:1;
> >> unsigned int usb3_lpm_u2_permit:1;
> >> + unsigned int oc_count;
> >> };
> >>
> >> #define to_usb_port(_dev) \
> >> diff --git a/drivers/usb/core/port.c b/drivers/usb/core/port.c
> >> index 1a01e9ad3804..0bfe410eb8a7 100644
> >> --- a/drivers/usb/core/port.c
> >> +++ b/drivers/usb/core/port.c
> >> @@ -41,6 +41,15 @@ static ssize_t connect_type_show(struct device *dev,
> >> }
> >> static DEVICE_ATTR_RO(connect_type);
> >>
> >> +static ssize_t oc_count_show(struct device *dev, struct device_attribute *attr,
> >> + char *buf)
> >> +{
> >> + struct usb_port *port_dev = to_usb_port(dev);
> >> +
> >> + return sprintf(buf, "%u\n", port_dev->oc_count);
> >> +}
> >> +static DEVICE_ATTR_RO(oc_count);
> >
> > I don't see what userspace can do with this number, as there's not much
> > it can do with it.
>
> I've answered this question to Felipe already:
<snip>
It's not described in the patch changelog, which is where it is required
:)
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
next reply other threads:[~2018-02-19 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 16:38 Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-19 16:05 usb: core: introduce per-port over-current counters Richard Leitner
2018-02-19 15:59 Greg Kroah-Hartman
2018-02-19 14:12 Richard Leitner
2018-02-19 13:53 Felipe Balbi
2018-02-19 12:01 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=20180219163856.GA6171@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).