From: Dmitry Artamonow <mad_soft@inbox.ru>
To: Keshava Munegowda <keshava_mgowda@ti.com>, Felipe Balbi <balbi@ti.com>
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [Regression?] Removed regulator support in ehci-omap
Date: Mon, 11 Apr 2011 13:32:14 +0400 [thread overview]
Message-ID: <20110411093214.GA18215@rainbow> (raw)
Hi, guys!
Can anyone explain why regulator support has been removed from ehci-omap
driver in commit 19403165 ("usb: host: omap: ehci and ohci simplification")[1]?
In 2.6.37/2.6.38 it was enough to apply simple patch[2] adding regulators
description to board file to make USB work on omap3evm board (because USB PHY
is powered via regulator). But now it won't work anymore in 2.6.39-rc2.
BTW, I suspect that this commit also broke USB on omap3pandora board, as it
defines "hsusb0" regulator supply in its board file:
[mad@madhouse linux-2.6]$ git grep hsusb arch/arm/mach-omap2/board*
arch/arm/mach-omap2/board-omap3pandora.c: REGULATOR_SUPPLY("hsusb0", "ehci
I can't find any clues in commit message on why regulators support was removed
and what should be used instead if this removal was intentional, so I'm a bit
puzzled about what to do now. Any help will be appreciated.
[1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=19403165c272cc4ed00c97973e7271714b009708
[2] http://arago-project.org/git/projects/?p=linux-omap3.git;a=commitdiff;h=2ec611981ad76256d5034ae36708d807142bed1c
--
Best regards,
Dmitry "MAD" Artamonow
next reply other threads:[~2011-04-11 9:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 9:32 Dmitry Artamonow [this message]
2011-04-11 17:06 ` [Regression?] Removed regulator support in ehci-omap 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
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=20110411093214.GA18215@rainbow \
--to=mad_soft@inbox.ru \
--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 \
/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).