From: matthieu.castet@parrot•com (Matthieu CASTET)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/3] at91-ohci: support overcurrent notification
Date: Tue, 5 Jul 2011 14:18:14 +0200 [thread overview]
Message-ID: <4E130106.9070703@parrot.com> (raw)
In-Reply-To: <20110705121858.411b183e@skate>
Hello,
Thomas Petazzoni a ?crit :
> Hello,
>
> Le Tue, 5 Jul 2011 12:12:54 +0200,
> Matthieu CASTET <matthieu.castet@parrot•com> a ?crit :
>
>> Why don't you forward the overcurrent notification to the usb stack ?
>> A printk is quite useless.
>
> Do you have a pointer to the appropriate functions/mechanisms of the
> USB stack about this ?
For ohci you have to override hub_status_data and hub_control callback.
You can look how it is done in ohci-da8xx.c / ohci-s3c2410.c driver.
May be (or not) it could be useful to introduce a generic function to do all the
parsing stuff.
Matthieu
PS : Add linux-usb to CC
next prev parent reply other threads:[~2011-07-05 12:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 9:05 [PATCH 1/3] ohci-at91: add vbus_pin_inverted platform attribute Thomas Petazzoni
2011-07-05 9:05 ` [PATCH 2/3] at91-ohci: support overcurrent notification Thomas Petazzoni
2011-07-05 10:12 ` Matthieu CASTET
2011-07-05 10:18 ` Thomas Petazzoni
2011-07-05 12:18 ` Matthieu CASTET [this message]
2011-07-05 14:23 ` Jean-Christophe PLAGNIOL-VILLARD
2011-07-05 9:05 ` [PATCH 3/3] at91-ohci: configure overcurrent pins as GPIOs Thomas Petazzoni
2011-07-05 11:39 ` [PATCH 1/3] ohci-at91: add vbus_pin_inverted platform attribute Sergei Shtylyov
2011-07-05 11:54 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2011-07-13 9:29 [PATCH v2] AT91 OHCI active-high vbus and overcurrent handling Thomas Petazzoni
2011-07-13 9:29 ` [PATCH 2/3] at91-ohci: support overcurrent notification Thomas Petazzoni
2011-07-13 14:28 ` Thomas Petazzoni
2011-07-13 15:54 ` Alan Stern
2011-07-13 16:43 ` Thomas Petazzoni
2011-07-13 17:17 ` Alan Stern
2011-09-07 10:47 ` Nicolas Ferre
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=4E130106.9070703@parrot.com \
--to=matthieu.castet@parrot$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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