LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: icxcnika@mar.tar.cc, linux-usb-devel@lists.sourceforge.net,
	Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] 2.6.20-rc4: usb somehow broken
Date: Mon, 15 Jan 2007 12:10:49 +0100	[thread overview]
Message-ID: <200701151210.49495.oliver@neukum.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0701141945010.14767@server.willdawg>

Am Sonntag, 14. Januar 2007 20:47 schrieb icxcnika@mar.tar.cc:
> > Can anyone suggest another approach?
> >
> > Alan Stern
> 
> Just a thought, you could use both a blacklist approach, and a module 
> paramater, or something in sysfs, to allow specifying devices that won't 
> be suspend and resume compatible.

Upon further thought, a module parameter won't do as the problem
will arise without a driver loaded. A sysfs parameter turns the whole
affair into a race condition. Will you set the guard parameter before the
autosuspend logic strikes?
Unfortunately this leaves only the least attractive solution.

	Regards
		Oliver

  parent reply	other threads:[~2007-01-15 11:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-11 17:20 Prakash Punnoor
2007-01-11 17:28 ` Oliver Neukum
2007-01-14  9:08   ` Prakash Punnoor
2007-01-14  9:28     ` Oliver Neukum
2007-01-14  9:44       ` Prakash Punnoor
2007-01-14 19:23         ` [linux-usb-devel] " Alan Stern
2007-01-14 19:47           ` icxcnika
2007-01-14 21:03             ` Oliver Neukum
2007-01-15 11:10             ` Oliver Neukum [this message]
2007-01-15 16:03               ` Alan Stern
2007-01-15 16:24                 ` Oliver Neukum
2007-01-15 16:36                   ` Alan Stern
2007-01-15 17:56                 ` Greg KH
2007-01-14  9:48       ` Prakash Punnoor
2007-01-14  9:58     ` Adrian Bunk
2007-01-19 11:29 ` [linux-usb-devel] " Oliver Neukum
2007-01-19 13:38   ` Prakash Punnoor
2007-01-19 14:00     ` Prakash Punnoor

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=200701151210.49495.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=icxcnika@mar.tar.cc \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    --subject='Re: [linux-usb-devel] 2.6.20-rc4: usb somehow broken' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).