From: Steve Sakoman <sakoman@gmail.com>
To: Alan Ott <alan@signal11.us>
Cc: Keshava Munegowda <keshava_mgowda@ti.com>,
Dmitry Artamonow <mad_soft@inbox.ru>,
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: Mon, 25 Apr 2011 07:16:22 -0700 [thread overview]
Message-ID: <BANLkTinn7C2gVKg4v8dbUxo7yYycdFM8PA@mail.gmail.com> (raw)
In-Reply-To: <4DB58108.4040708@signal11.us>
On Mon, Apr 25, 2011 at 7:11 AM, Alan Ott <alan@signal11.us> wrote:
> On 04/24/2011 02:37 AM, Keshava Munegowda wrote:
>>> -----Original Message-----
>>> From: Alan Ott [mailto:alan@signal11.us]
>>> Sent: Friday, April 22, 2011 6:41 AM
>>> To: Keshava Munegowda
>>> Cc: Dmitry Artamonow; Steve Sakoman; Steve Calfee; Felipe Balbi;
>> linux-usb@vger.kernel.org; linux-
>>> omap@vger.kernel.org; linux-kernel@vger.kernel.org
>>> Subject: Re: [Regression?] Removed regulator support in ehci-omap
>>>
>>> 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
>> I have posted the patches on April 22, 2011.
>> If possible I request you to test this.
>
> Hi Keshava,
>
> If you mean this patch[1], then I tested it against the head and it
> didn't fix my problem. I couldn't convince myself that your patch was
> supposed to be the whole fix to my problem (since it wasn't mentioned on
> this thread) so I didn't reply with my findings. Sorry about that.
Same here. The real issue (at least for Overo) turned out to be:
https://lkml.org/lkml/2011/4/14/45
Steve
next prev parent reply other threads:[~2011-04-25 14:16 UTC|newest]
Thread overview: 16+ 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
2011-04-24 6:37 ` Keshava Munegowda
[not found] ` <8712165194c49f0b4d8c1bd1fe717b8a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-25 14:11 ` Alan Ott
2011-04-25 14:16 ` Steve Sakoman [this message]
2011-04-25 16:41 ` Keshava Munegowda
2011-04-25 17:23 ` Steve Calfee
[not found] ` <4DB5ADFF.5030502-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-04-25 23:21 ` Steve Calfee
2011-04-26 5:57 ` 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=BANLkTinn7C2gVKg4v8dbUxo7yYycdFM8PA@mail.gmail.com \
--to=sakoman@gmail.com \
--cc=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=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;
as well as URLs for NNTP newsgroup(s).