From: Alan Ott <alan@signal11.us>
To: Keshava Munegowda <keshava_mgowda@ti.com>
Cc: Dmitry Artamonow <mad_soft@inbox.ru>,
Steve Sakoman <sakoman@gmail.com>,
Steve Calfee <stevecalfee@gmail.com>, Felipe Balbi <balbi@ti.com>,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Regression?] Removed regulator support in ehci-omap
Date: Thu, 21 Apr 2011 21:10:38 -0400 [thread overview]
Message-ID: <4DB0D58E.4030508@signal11.us> (raw)
In-Reply-To: <bcd954a468e6a07bd673b7d0731e9344@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
On 04/12/2011 12:20 PM, Keshava Munegowda wrote:
>> Ah, so EHCI/OHCI common code was moved into drivers/mfd... Good.
>> But seems regulators support was lost somewhere during transition - the
>> only mentioning about regulators in omap-usb-host.c is "#include" :
>>
>> mad@macmini:~/kernel-hack/linux-2.6(master)$ grep -i regulator
> drivers/mfd/omap-usb-host.c
> Thanks ! I will add some time next week!
I have confirmed this on my BeagleBoard-xM. 2.6.38 works, but the
2.6.39-rc4+ head from yesterday did not. It seems that the regulator
does not turn the power on for the USB hub which the ethernet is
attached to.
I connected this issue to bug 33092 in bugzilla[1].
Alan.
[1] https://bugzilla.kernel.org/show_bug.cgi?id=33092
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 554 bytes --]
next prev parent reply other threads:[~2011-04-22 1:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 9:32 [Regression?] Removed regulator support in ehci-omap Dmitry Artamonow
2011-04-11 17:06 ` Steve Calfee
2011-04-11 20:12 ` Steve Sakoman
2011-04-11 20:48 ` Keshava Munegowda
2011-04-12 4:10 ` Dmitry Artamonow
2011-04-12 16:20 ` Keshava Munegowda
2011-04-22 1:10 ` Alan Ott [this message]
2011-04-24 6:37 ` Keshava Munegowda
2011-04-25 14:11 ` Alan Ott
2011-04-25 14:16 ` Steve Sakoman
2011-04-25 16:41 ` Keshava Munegowda
2011-04-27 11:51 ` Dmitry Artamonow
2011-04-27 14:52 ` Munegowda, Keshava
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=4DB0D58E.4030508@signal11.us \
--to=alan@signal11.us \
--cc=balbi@ti.com \
--cc=keshava_mgowda@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mad_soft@inbox.ru \
--cc=sakoman@gmail.com \
--cc=stevecalfee@gmail.com \
/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