public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] usb: ehci: remember init mode
Date: Thu, 27 Aug 2015 12:45:23 +0200	[thread overview]
Message-ID: <201508271245.23095.marex@denx.de> (raw)
In-Reply-To: <55DB68FE.6020002@wwwdotorg.org>

On Monday, August 24, 2015 at 08:57:02 PM, Stephen Warren wrote:
> On 08/23/2015 09:47 PM, Marek Vasut wrote:
> > On Friday, August 21, 2015 at 11:58:55 PM, Stephen Warren wrote:
> >> On 08/20/2015 11:34 PM, Marek Vasut wrote:
> >>> On Friday, August 21, 2015 at 01:38:05 AM, Stephen Warren wrote:
> >>>> From: Stephen Warren <swarren@nvidia.com>
> >>>> 
> >>>> When an EHCI device is registered in device mode, the HW isn't
> >>>> actually initialized at all, and hence isn't left in a running state.
> >>>> Consequently, when the device is deregistered, ehci_shutdown() will
> >>>> fail, since the HW bits it expects to see set in response to its
> >>>> shutdown requests will not be sent, and the message "EHCI failed to
> >>>> shut down host controller." will be printed.
> >>>> 
> >>>> Fix ehci-hcd.c to remember whether the device was registered in host
> >>>> or device mode, and only call ehci_shutdown() for host mode
> >>>> registrations.
> >>> 
> >>> Hi,
> >>> 
> >>> Shouldn't you instead check if the controller is running or not and
> >>> shut it down based on that ?
> >> 
> >> Why would the two states be different? How can the code check if the
> >> controller is running; is there some HW bit that should be checked for
> >> that?
> > 
> > Hi,
> > 
> > Hrm, I am not aware of any, sorry :-( But the driver can track whether
> > the controller was previously inited or not, right ? I mean, this is DM,
> > so we should be able to have a private data bit for that, no ?
> 
> I believe that's exactly what this patch is doing. I added a variable to
> the driver's data structure indicating whether the last initialization
> call was for host mode (-> EHCI is running, and should be shut down in
> remove()) or device mode (-> EHCI is not running, so should not be shut
> down in remove()).

Uh, right, sorry. Applied.

Best regards,
Marek Vasut

      reply	other threads:[~2015-08-27 10:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 23:38 [U-Boot] [PATCH] usb: ehci: remember init mode Stephen Warren
2015-08-21  5:34 ` Marek Vasut
2015-08-21 21:58   ` Stephen Warren
2015-08-24  3:47     ` Marek Vasut
2015-08-24 18:57       ` Stephen Warren
2015-08-27 10:45         ` Marek Vasut [this message]

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=201508271245.23095.marex@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    /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