linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gregkh@suse.de (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1 v2] ehci-mxc: Fix mx31 OTG host initialisation
Date: Wed, 12 May 2010 11:50:05 -0700	[thread overview]
Message-ID: <20100512185005.GA28990@suse.de> (raw)
In-Reply-To: <201005120923.48568.philippe.retornaz@epfl.ch>

On Wed, May 12, 2010 at 09:23:48AM +0200, Philippe R?tornaz wrote:
> Le mercredi, 12 mai 2010 01.38:12, Greg KH a ?crit :
> > On Tue, May 11, 2010 at 04:14:34PM +0200, Philippe R?tornaz wrote:
> > > On mx31 the OTG host initialisation fails if you need to have
> > > an ULPI transfert to initialize the PHY.
> > >
> > > In order to be able to communicate with the PHY a complete reset
> > > of the usb host is needed. After the PHY initialization the host
> > > usb configuration registers need to be rewritten to avoid a host
> > > controller lockup.
> > >
> > > Signed-off-by: Philippe R?tornaz <philippe.retornaz@epfl.ch>
> > > ---
> > >  drivers/usb/host/ehci-mxc.c |   98
> > > ++++++++++++++++++++++++++++++++++++++-----
> > 
> > This patch doesn't apply anymore, can you redo it against the linux-next
> > tree?
> > 
> 
> It apply cleanly on next-20100512. 
> 
> It needs commit 5a25ad84e01173bb225285eb50f9af48ed1a7598 to apply, but this 
> one is in linux-next now.

Where is that patch from?  Some other tree?

confused,

greg k-h

  reply	other threads:[~2010-05-12 18:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11 14:14 [PATCH 0/1 v2] mx31: Fix usb otg host initialisation Philippe Rétornaz
2010-05-11 14:14 ` [PATCH 1/1 v2] ehci-mxc: Fix mx31 OTG " Philippe Rétornaz
2010-05-11 23:38   ` Greg KH
2010-05-12  7:23     ` Philippe Rétornaz
2010-05-12 18:50       ` Greg KH [this message]
2010-05-13 17:04         ` Philippe Rétornaz
2010-05-20 17:32       ` Philippe Rétornaz
2010-05-20 18:18         ` Greg KH
2010-05-20 18:29           ` Philippe Rétornaz

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=20100512185005.GA28990@suse.de \
    --to=gregkh@suse.de \
    --cc=linux-arm-kernel@lists.infradead.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).