linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Keshava Munegowda <keshava_mgowda@ti.com>
To: Steve Sakoman <sakoman@gmail.com>, Steve Calfee <stevecalfee@gmail.com>
Cc: Dmitry Artamonow <mad_soft@inbox.ru>, 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: Tue, 12 Apr 2011 02:18:28 +0530	[thread overview]
Message-ID: <112ef82aebc719ef25cde126f2014ebc@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinDMZ+CyGCmzZu8cSz1L_yFXxm+vg@mail.gmail.com>

> -----Original Message-----
> From: Steve Sakoman [mailto:sakoman@gmail.com]
> Sent: Tuesday, April 12, 2011 1:43 AM
> To: Steve Calfee
> Cc: Dmitry Artamonow; Keshava Munegowda; 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 Mon, Apr 11, 2011 at 10:06 AM, Steve Calfee <stevecalfee@gmail.com>
wrote:
> > On 04/11/11 02:32, Dmitry Artamonow wrote:
> >> 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:
> >>
> > Yes, And Beagleboard xm (and I suspect other beagleboard versions) has
> > been broken in 2.6.39rc1+.
>
> FWIW, EHCI is also broken on Overo in both rc1 and rc2.
>
> Steve

Sorry guys! I will work on it coming week; currently I am in travel.

Well, regulator is not removed, its moved to usbhs core driver in
/driver/mfd/omap xx usb xxx host.c

Regards
Keshava Munegowda

  reply	other threads:[~2011-04-11 20:48 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 [this message]
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=112ef82aebc719ef25cde126f2014ebc@mail.gmail.com \
    --to=keshava_mgowda@ti.com \
    --cc=balbi@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;
as well as URLs for NNTP newsgroup(s).