mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aleksey Gorelov <dared1st@yahoo.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: David Brownell <david-b@pacbell.net>,
	linux-usb-devel@lists.sourceforge.net,
	Andrew Morton <akpm@osdl.org>,
	gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] [PATCH] Properly unregister reboot notifier in case of failure in ehci hcd
Date: Mon, 31 Jul 2006 12:35:44 -0700 (PDT)	[thread overview]
Message-ID: <20060731193544.71481.qmail@web81206.mail.mud.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0607311450120.8671-100000@iolanthe.rowland.org>



--- Alan Stern <stern@rowland.harvard.edu> wrote:

> On Mon, 31 Jul 2006, Aleksey Gorelov wrote:
> 
> > > Why do you need to change the bus glue?  Wouldn't it be a lot simpler just 
> > > to add ehci_shutdown as a member of ehci_pci_driver, for instance, with 
> > > similar changes to ehci_hcd_au1xxx_driver and ehci_hcd_fsl_driver?
> > > 
> > > Alan Stern
> > 
> >   This avoids code duplication for common for both ehci and ohci code
> 
> What code duplication?  Doing it the way I suggested doesn't require 
> adding any new code at all.  You, on the other hand, added several 
> routines for bus glue that does virtually nothing.

  But you can not use exactly same shutdown function with both pci and platform glue. You need to
convert pci/platform device to hcd anyway, right ? So this will add 2 doing 'virtually nothing'
routines anyway (unless you just want to duplicate the code of shutdown routine for for platform
glue). For ohci, you would need to do the same, hence 2 more routines, 4 total. With bus glue, I
added just 2. Am I missing something here ?

> 
> > (and possibly for uhci, but
> > it currently does not have any notifier/shutdown handler),
> 
> Yes it does.  From uhci-hcd.c:

My bad. I did not find notifier, but shutdown handler is indeed there. However, uhci is different
in a way it does not use platform driver.

Aleks.

  reply	other threads:[~2006-07-31 19:36 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
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 [this message]
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=20060731193544.71481.qmail@web81206.mail.mud.yahoo.com \
    --to=dared1st@yahoo.com \
    --cc=akpm@osdl.org \
    --cc=david-b@pacbell.net \
    --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®