public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	USB development list <linux-usb-devel@lists.sourceforge.net>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [Bulk] Re: [linux-usb-devel] 2.6.19-rc5 regression: can't disable OHCI wakeup via sysfs
Date: Tue, 14 Nov 2006 12:54:09 -0800	[thread overview]
Message-ID: <200611141254.09474.david-b@pacbell.net> (raw)
In-Reply-To: <200611142348.30082.arvidjaar@mail.ru>

On Tuesday 14 November 2006 12:48 pm, Andrey Borzenkov wrote:
> On Monday 13 November 2006 22:58, Alan Stern wrote:
> > Andrey:
> >
> > Try this patch for 2.6.19-rc5.  Although it doesn't make all the changes
> > Dave and I have discussed, it ought to fix your problem.
> >
> 
> It did. Thank you

Then this should get merged into 2.6.19-rc ASAP ...

- Dave


> -andrey
> 
> > Alan Stern
> >
> >
> > Index: 2.6.19-rc5/drivers/usb/host/ohci-hub.c
> > ===================================================================
> > --- 2.6.19-rc5.orig/drivers/usb/host/ohci-hub.c
> > +++ 2.6.19-rc5/drivers/usb/host/ohci-hub.c
> > @@ -422,7 +422,8 @@ ohci_hub_status_data (struct usb_hcd *hc
> >  				ohci->autostop = 0;
> >  				ohci->next_statechange = jiffies +
> >  						STATECHANGE_DELAY;
> > -			} else if (time_after_eq (jiffies,
> > +			} else if (device_may_wakeup(&hcd->self.root_hub->dev)
> > +					&& time_after_eq(jiffies,
> >  						ohci->next_statechange)
> >  					&& !ohci->ed_rm_list
> >  					&& !(ohci->hc_control &
> 

  reply	other threads:[~2006-11-14 20:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-18 15:19 2.6.17: dmesg flooded with "ohci_hcd 0000:00:02.0: wakeup" Andrey Borzenkov
2006-06-18 16:29 ` [linux-usb-devel] " David Brownell
2006-06-18 17:29   ` Andrey Borzenkov
2006-06-18 18:16     ` David Brownell
2006-06-18 19:22       ` Andrey Borzenkov
2006-06-19 18:39       ` Andrey Borzenkov
2006-06-19 20:12         ` David Brownell
2006-11-11 11:29           ` 2.6.19-rc5 regression: can't disable OHCI wakeup via sysfs Andrey Borzenkov
2006-11-12 16:31             ` [linux-usb-devel] " Alan Stern
2006-11-12 18:00               ` David Brownell
2006-11-12 21:59                 ` Alan Stern
2006-11-12 23:21                   ` David Brownell
2006-11-13 15:57                     ` Alan Stern
2006-11-13 16:39                       ` David Brownell
2006-11-13 17:15                         ` Alan Stern
2006-11-14 21:18                           ` David Brownell
2006-11-14 21:42                             ` Alan Stern
2006-11-14 22:56                               ` David Brownell
2006-11-13 19:58                         ` Alan Stern
2006-11-14 20:48                           ` Andrey Borzenkov
2006-11-14 20:54                             ` David Brownell [this message]
2006-09-22 18:53       ` [linux-usb-devel] 2.6.17: dmesg flooded with "ohci_hcd 0000:00:02.0: wakeup" Andrey Borzenkov
2006-09-22 20:52         ` Alan Stern
2006-11-11 11:27       ` Andrey Borzenkov

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=200611141254.09474.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=arvidjaar@mail.ru \
    --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