[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

2006-04-26 Thread Patrick Mochel
On Mon, Apr 24, 2006 at 02:29:51PM -0700, David Brownell wrote: > I recently observed this myself and tracked down one problem. The solution > involves what kexec() does in much the same situation: before starting a > new kernel, most hardware needs to be reset. Today, swsusp will suspend it >

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

2006-04-26 Thread Rafael J. Wysocki
On Wednesday 26 April 2006 23:31, David Brownell wrote: > On Wednesday 26 April 2006 4:26 am, Rafael J. Wysocki wrote: > > On Wednesday 26 April 2006 00:56, David Brownell wrote: > > > > But it's not the root cause of the problem either. The same problem > > > appears if > > > the device holding

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

2006-04-26 Thread David Brownell
On Wednesday 26 April 2006 4:26 am, Rafael J. Wysocki wrote: > On Wednesday 26 April 2006 00:56, David Brownell wrote: > > But it's not the root cause of the problem either. The same problem > > appears if > > the device holding the resume partition gets forced into this "broken > > suspend" >

[linux-usb-devel] Correct transfer buffer size and struct usb_class_driver questions

2006-04-26 Thread Alisdair Davey
I have 3 quick questions I hope someone can clarify for me. Development is being done on Linux Mandrake 10.2 Laptop running kernel 2.6.11-6mddsmp. First up: I've been using usb_bulk_msg to get data from EP 2 of my CCD camera. Endpoint Descriptor: bLength 7 bDescriptorType

[linux-usb-devel] [PATCH] usbcore: always turn on hub port power

2006-04-26 Thread Alan Stern
Greg: Some hubs claim not to support port-power switching, and right now the hub driver believes them and does not enable power to their ports. However it turns out that even though they don't actually switch power, they do ignore all events on a port until told to turn on the power! This pro

Re: [linux-usb-devel] [RFC] usbcore: enable port power even when hub doesn't support it

2006-04-26 Thread Alan Stern
On Wed, 26 Apr 2006, Greg KH wrote: > > These are not USB 1.0 hubs; they are more recent than that! > > Ah, ok, I thought you were referring to 1.0 hubs above. The way I phrased it was a little ambiguous. > > In fact, lots of hubs don't implement port power switching. Even when > > they say th

Re: [linux-usb-devel] [RFC] usbcore: enable port power even when hub doesn't support it

2006-04-26 Thread Greg KH
On Wed, Apr 26, 2006 at 04:07:29PM -0400, Alan Stern wrote: > On Wed, 26 Apr 2006, Greg KH wrote: > > > On Wed, Apr 26, 2006 at 11:32:06AM -0400, Alan Stern wrote: > > > I've seen a couple of bug reports which boiled down to the fact that the > > > hub driver doesn't enable port power if the hub d

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

2006-04-26 Thread Rafael J. Wysocki
On Wednesday 26 April 2006 21:06, Alan Stern wrote: > On Wed, 26 Apr 2006, Rafael J. Wysocki wrote: > > > > > It just shouldn't be necessary. Actually I think the resume device > > > > shouldn't > > > > be frozen too. > > > > > > Well, you wouldn't want it doing DMA to unknown memory areas while

Re: [linux-usb-devel] [RFC] usbcore: enable port power even when hub doesn't support it

2006-04-26 Thread Alan Stern
On Wed, 26 Apr 2006, Greg KH wrote: > On Wed, Apr 26, 2006 at 11:32:06AM -0400, Alan Stern wrote: > > I've seen a couple of bug reports which boiled down to the fact that the > > hub driver doesn't enable port power if the hub descriptor indicates the > > port power isn't switchable (a la USB 1.0)

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

2006-04-26 Thread Nigel Cunningham
Hi. On Thursday 27 April 2006 00:24, Alan Stern wrote: > A little behind the current head of the thread, but better late than > never... :) > On Wed, 26 Apr 2006, Nigel Cunningham wrote: > > > (7) (without your change) swsusp calls .suspend() for all device > > > drivers that are present at that

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

2006-04-26 Thread Alan Stern
On Wed, 26 Apr 2006, Rafael J. Wysocki wrote: > > > It just shouldn't be necessary. Actually I think the resume device > > > shouldn't > > > be frozen too. > > > > Well, you wouldn't want it doing DMA to unknown memory areas while you're > > trying to place the image data in those same areas, wo

Re: [linux-usb-devel] [RFC] usbcore: enable port power even when hub doesn't support it

2006-04-26 Thread Greg KH
On Wed, Apr 26, 2006 at 11:32:06AM -0400, Alan Stern wrote: > I've seen a couple of bug reports which boiled down to the fact that the > hub driver doesn't enable port power if the hub descriptor indicates the > port power isn't switchable (a la USB 1.0). 1.0 USB Hubs? They should be thrown away,

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

2006-04-26 Thread Rafael J. Wysocki
On Wednesday 26 April 2006 17:38, Alan Stern wrote: > On Wed, 26 Apr 2006, Rafael J. Wysocki wrote: > > > > So under these circumstances, how does it hurt anything to reset the > > > resume device rather than to freeze it? > > > > It just shouldn't be necessary. Actually I think the resume devi

Re: [linux-usb-devel] Support for ADATA MyFlash FP1

2006-04-26 Thread Nickolay V. Shmyrev
>On Wed, 2006-04-26 at 16:28 +0400, Nickolay V. Shmyrev wrote: >> Hello all >> >> I've unfortunately bought one interesting device - A-DATA MyFlash FP1 >> memory stick with fingerprint protection. It looks pretty, much like >> iPod :) >> >> http://www.adata.com.tw/adata_en/product_detail.php?Pro

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

2006-04-26 Thread Alan Stern
On Wed, 26 Apr 2006, Rafael J. Wysocki wrote: > > So under these circumstances, how does it hurt anything to reset the > > resume device rather than to freeze it? > > It just shouldn't be necessary. Actually I think the resume device shouldn't > be frozen too. Well, you wouldn't want it doing

Re: [linux-usb-devel] Support for ADATA MyFlash FP1

2006-04-26 Thread gerard klaver
On Wed, 2006-04-26 at 16:28 +0400, Nickolay V. Shmyrev wrote: > Hello all > > I've unfortunately bought one interesting device - A-DATA MyFlash FP1 > memory stick with fingerprint protection. It looks pretty, much like > iPod :) > > http://www.adata.com.tw/adata_en/product_detail.php?ProductNo=1

[linux-usb-devel] [RFC] usbcore: enable port power even when hub doesn't support it

2006-04-26 Thread Alan Stern
I've seen a couple of bug reports which boiled down to the fact that the hub driver doesn't enable port power if the hub descriptor indicates the port power isn't switchable (a la USB 1.0). Apparently a bunch of devices have bad data in their descriptors, and by believing them we render them non-u

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

2006-04-26 Thread Rafael J. Wysocki
On Wednesday 26 April 2006 16:38, Alan Stern wrote: > On Wed, 26 Apr 2006, Rafael J. Wysocki wrote: > > > > Now, if you have specific examples of things that shouldn't be reset, that > > > could be interesting. > > > > The resume device and friends (ie. controller, bus, etc.). > > I presume the

Re: [linux-usb-devel] Support for ADATA MyFlash FP1

2006-04-26 Thread Alan Stern
On Wed, 26 Apr 2006, Nickolay V. Shmyrev wrote: > Hello all > > I've unfortunately bought one interesting device - A-DATA MyFlash FP1 > memory stick with fingerprint protection. It looks pretty, much like > iPod :) > > http://www.adata.com.tw/adata_en/product_detail.php?ProductNo=138 > > It id

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

2006-04-26 Thread Alan Stern
On Wed, 26 Apr 2006, Rafael J. Wysocki wrote: > > Now, if you have specific examples of things that shouldn't be reset, that > > could be interesting. > > The resume device and friends (ie. controller, bus, etc.). I presume the freeze/reset we're talking about occurs immediately after the memor

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

2006-04-26 Thread Alan Stern
A little behind the current head of the thread, but better late than never... On Wed, 26 Apr 2006, Nigel Cunningham wrote: > > (7) (without your change) swsusp calls .suspend() for all device drivers > > that are present at that time, but our driver is not there, so its > > .suspend() _won't_ be

[linux-usb-devel] Support for ADATA MyFlash FP1

2006-04-26 Thread Nickolay V. Shmyrev
Hello all I've unfortunately bought one interesting device - A-DATA MyFlash FP1 memory stick with fingerprint protection. It looks pretty, much like iPod :) http://www.adata.com.tw/adata_en/product_detail.php?ProductNo=138 It identifies itself on bus as 0x1307:0x1169 I say unfortunately becau

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

2006-04-26 Thread Rafael J. Wysocki
On Wednesday 26 April 2006 00:56, David Brownell wrote: > On Tuesday 25 April 2006 2:55 pm, Rafael J. Wysocki wrote: > > On Tuesday 25 April 2006 23:04, David Brownell wrote: > > > > > The third state is the problem scenario, kicking in when the driver was > > > statically linked (or modprobed fr

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

2006-04-26 Thread Nigel Cunningham
Hi. On Wednesday 26 April 2006 13:32, David Brownell wrote: > On Tuesday 25 April 2006 6:16 pm, Nigel Cunningham wrote: > > Hi. > > > > On Wednesday 26 April 2006 09:55, David Brownell wrote: > > > On Tuesday 25 April 2006 3:18 pm, Nigel Cunningham wrote: > > > > I saw the 2 suspends, 1 resume com

[linux-usb-devel] Re: [linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

2006-04-26 Thread Pavel Machek
On Út 25-04-06 16:13:41, David Brownell wrote: > On Tuesday 25 April 2006 2:41 pm, Pavel Machek wrote: > > > > Well, if we had a pm_should_I_spin_down_drives() it would make sense to me > > > that it return FALSE during kernel_restart_prepare() too ... surely kexec > > > users have the same issues