Re: [linux-usb-devel] [GIT PATCH] More USB patches for 2.6.18
From: Alan Stern
Date: Fri Sep 29 2006 - 12:02:05 EST
On Thu, 28 Sep 2006, David Brownell wrote:
> On Thursday 28 September 2006 5:20 pm, Andrew Morton wrote:
> > On Thu, 28 Sep 2006 17:08:33 -0700
> > David Brownell <david-b@xxxxxxxxxxx> wrote:
> > > ... reviewing and testing those new OHCI changes is still on my
> > > list;
> > erm, we prefer to do that before code hits mainline.
We are victims of bad timing. This all started with the USB autosuspend
patches, submitted around a month ago. Greg didn't merge all of them
because he experienced some problems (which we still haven't sorted out!),
but the rest went into -mm. But then Greg was away for a while and too
busy to help with debugging.
I hadn't done any testing of OHCI controllers with CONFIG_USB_SUSPEND
turned off, and when problems turned up a couple of weeks ago it became
apparent that some of the existing code in ohci-hcd had to change or be
removed, as it wasn't compatible with the new autosuspend mechanism.
This was done just in the past week, and David hasn't had much of a chance
to go through and review it yet.
As a result, when the autosuspend patches went upstream for 2.6.19-rc1 the
extra ohci-hcd changes had to go with them, even though they have received
very little testing and review. Perhaps things moved too quickly, but
this wasn't obvious at the time, and anyway it's done now.
> Exactly why I mentioned the issue. I trust Alan basically got the
> ohci parts of that new root hub suspend code right, but I probably
> have a lot more variety in OHCI silicon here ... but virtually no
> time to assemble the relevant platform patches and test them with
> new patches from MM/etc, given other ongoing work.
Exactly. The new code works on the one system I have with OHCI
controllers, and a few other people have used it successfully. However
this is hardly a wide sampling, and we know there are controllers out
there with bizarre quirks which might not like the changes.
The problems with last-minute compile errors are symptoms that the new
code has shaken down yet -- compounded by the way different versions of
GCC don't all report the same classes of errors.
> > > all that suspend stuff needs care, things that work on PCs don't
> > > necessarily work on embedded hardware (where OHCI is common, and
> > > PM tends to be more critical).
> > I guess we'll find out.
Hopefully in plenty of time to get straightened out before too many
2.6.19-rc releases have gone by.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/