[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1012231104060.5617-100000@netrider.rowland.org>
Date: Thu, 23 Dec 2010 11:08:36 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: Anoop P A <anoop.pa@...il.com>
cc: Ralf Baechle <ralf@...ux-mips.org>,
Greg Kroah-Hartman <gregkh@...e.de>,
Anatolij Gustschin <agust@...x.de>,
Anand Gadiyar <gadiyar@...com>, <linux-mips@...ux-mips.org>,
<linux-kernel@...r.kernel.org>, <linux-usb@...r.kernel.org>,
Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
Oliver Neukum <oneukum@...e.de>,
Hans de Goede <hdegoede@...hat.com>,
Paul Mortier <mortier@...nternet.com>,
Andiry Xu <andiry.xu@....com>
Subject: Re: [PATCH V2 2/2] MSP onchip root hub over current quirk.
On Thu, 23 Dec 2010, Anoop P A wrote:
> > > + usb_detect_quirks(hdev);
> >
> > This line is wrong. usb_detect_quirks() gets called only once per
> > device, when the device is initialized. Besides, you probably want to
> > use a hub-specific flag for this rather than a device-specific flag.
>
> Can you point me to an example for the recommended way of doing the
> hack. I don't have much exposure to USB subsystem.
One example, suitable for PCI devices, can be found in
drivers/usb/host/ehci-pci.c:ehci_pci_setup().
However the best approach would be for you to avoid adding any
special-purpose code at all. Is it possible to handle
overcurrent-change events in a way that will work just as well for
normal hubs as for your MSP root hub?
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists