mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Aleksey Gorelov <dared1st@yahoo.com>,
	Andrew Morton <akpm@osdl.org>,
	gregkh@suse.de, stern@rowland.harvard.edu,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] [PATCH] Properly unregister reboot notifier in case of failure in ehci hcd
Date: Fri, 14 Jul 2006 14:33:47 -0700	[thread overview]
Message-ID: <200607141433.48695.david-b@pacbell.net> (raw)
In-Reply-To: <20060714164637.79842.qmail@web81212.mail.mud.yahoo.com>

On Friday 14 July 2006 9:46 am, Aleksey Gorelov wrote:

> David, Alan,
> 
> Do you think it is Ok to unregister reboot notifier in ehci_run before registering one to make
> sure there is no 'double registering' of notifier, or is it better to move register/unregister
> reboot notifier from ehci_run/ehci_stop completely to some other place ?

Probably the best way is to stop using the notifier, and brute force it
by making every EHCI subdriver get its own shutdown() method.  That'd be
obvious enough for PCI bus glue, and due to recent patches probably even
for the non-PCI ones ... since they all use "platform_bus" now, they can
all share the same method.  Though I could imagine some platforms might
want to do extra stuff like clk_disable() after the root hub reset.

I could see the tail end of ehci-hcd.c with a forward decl for a method
like ehci_platform_shutdown(), updating the subdrivers to reference that,
and then #ifdef PLATFORM_DRIVER provide the definition of that routine
(doing what the reboot notifier does) for use by the non-PCI subdrivers.

- Dave


  parent reply	other threads:[~2006-07-14 21:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12  6:38 Aleksey Gorelov
2006-07-13  4:55 ` [linux-usb-devel] " David Brownell
2006-07-14  2:15 ` Andrew Morton
2006-07-14 16:46   ` Aleksey Gorelov
2006-07-14 18:37     ` [linux-usb-devel] " Alan Stern
2006-07-14 21:33     ` David Brownell [this message]
2006-07-31 17:23       ` Aleksey Gorelov
2006-07-31 18:18         ` Alan Stern
2006-07-31 18:28           ` Aleksey Gorelov
2006-07-31 18:58             ` Alan Stern
2006-07-31 19:35               ` Aleksey Gorelov
2006-07-31 19:46                 ` Alan Stern
2006-07-31 21:30                   ` David Brownell

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=200607141433.48695.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=akpm@osdl.org \
    --cc=dared1st@yahoo.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /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

all inboxes | Powered by JetHome®