a new problem with the hso driver
Subsystems (2)
Hi Greg/Andrew,
I've a minor problem.
If you put the hso driver into powersave mode
by going into /sysfs
cd /sys/
find . -name idVendor | xargs -n 1 | grep -H af0
cd ./devices/pci0000:00/0000:00:1d.7/usb5/5-4/
or wherever the idVendor is at.
cd power/
echo auto > level
Then let the driver sleep for about 2 minutes.a
It can't be woken up, it appears that the
usb layer is looking for a reset_resume
function to be implemented.
We get the following messages from the kernel
[12518.790072] hso 2-2:1.0: no reset_resume for driver hso? [12518.790081] hso 2-2:1.1: no reset_resume for driver hso? [12518.790085] hso 2-2:1.2: no reset_resume for driver hso?
How do I implement a reset resume function?
could somebody tell me & put in a few comments in include/linux/usb.h Our customer says the device has gone into an S3 sleep whatever the difference between this & the reduced power mode it goes into after 2 seconds when it calls hso_suspend I don't know.
On a slightly related issue
we get an error -22 ie -EINVAL from usb_submit_urb
this though I haven't investigated properly appears to happen when the device is suspended but appears to have no adverse effect on the driver
it still seems to work, I haven't really investigated this, whats happening? but would greatly appreciate being pointed in the right direction.
Signature · 2 lines
best regards, D.J. Barrow
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 18 lines · Denis Joseph Barrow
Hi Greg/Andrew,
I've a minor problem.
If you put the hso driver into powersave mode
by going into /sysfscd
/sys/
find . -name idVendor | xargs -n 1 | grep -H af0
cd ./devices/pci0000:00/0000:00:1d.7/usb5/5-4/
or wherever the idVendor is at.
cd power/
echo auto > levelThen let the driver sleep for about 2 minutes.a
It can't be woken up, it appears that the
usb layer is looking for areset_resume
function to be implemented.
Quoted 7 lines
We get the following messages from the kernel
[12518.790072] hso 2-2:1.0: no reset_resume for driver hso? [12518.790081] hso 2-2:1.1: no reset_resume for driver hso? [12518.790085] hso 2-2:1.2: no reset_resume for driver hso?How do I implement a reset resume function?
could somebody tell me & put in a few comments ininclude/linux/usb.h
See Documentation/usb/power-management.txt.
Quoted 10 lines
Our customer says the device has gone into an S3 sleep whatever the difference between this & the reduced power mode it goes into after 2 seconds when it calls
hso_suspendI don't know.On a slightly related issue
we get an error -22 ie-EINVALfromusb_submit_urb
this though I haven't investigated properly appears to happen when the device is suspended but appears to have no adverse effect on the driver
it still seems to work, I haven't really investigated this, whats happening? but would greatly appreciate being pointed in the right direction.
-EINVAL can indicate several possible errors, but as far as I remember, none of them are associated with the device being suspended. If you try to submit an URB to a suspended device, you'll get -EHOSTUNREACH.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): Pine.LNX.4.44L0.0809111835350.3949-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org
Quoted 4 lines
Quoted 4 lines
On a slightly related issue
we get an error -22 ie-EINVALfromusb_submit_urb
this though I haven't investigated properly appears to happen when the device is suspended
suspend? Are you sure it doesn't come from resume?
BTW:
if (serial->shared_int) {
mutex_lock(&serial->shared_int->shared_int_lock);
if (serial->shared_int->use_count &&
(--serial->shared_int->use_count == 0)) {This code deserves a honourable mentioning in the obfuscated C contest.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Thank you Alan
Quoted 46 lines · Alan Stern
Quoted 18 lines · Denis Joseph Barrow
Hi Greg/Andrew,
I've a minor problem.
If you put the hso driver into powersave mode
by going into /sysfscd
/sys/
find . -name idVendor | xargs -n 1 | grep -H af0
cd ./devices/pci0000:00/0000:00:1d.7/usb5/5-4/
or wherever the idVendor is at.
cd power/
echo auto > levelThen let the driver sleep for about 2 minutes.a
It can't be woken up, it appears that the
usb layer is looking for areset_resume
function to be implemented.Quoted 7 lines
We get the following messages from the kernel
[12518.790072] hso 2-2:1.0: no reset_resume for driver hso? [12518.790081] hso 2-2:1.1: no reset_resume for driver hso? [12518.790085] hso 2-2:1.2: no reset_resume for driver hso?How do I implement a reset resume function?
could somebody tell me & put in a few comments ininclude/linux/usb.hSee
Documentation/usb/power-management.txt.Quoted 10 lines
Our customer says the device has gone into an S3 sleep whatever the difference between this & the reduced power mode it goes into after 2 seconds when it calls
hso_suspendI don't know.On a slightly related issue
we get an error -22 ie-EINVALfromusb_submit_urb
this though I haven't investigated properly appears to happen when the device is suspended but appears to have no adverse effect on the driver
it still seems to work, I haven't really investigated this, whats happening? but would greatly appreciate being pointed in the right direction.
-EINVALcan indicate several possible errors, but as far as I remember, none of them are associated with the device being suspended. If you try to submit an URB to a suspended device, you'll get-EHOSTUNREACH.Alan Stern
Signature · 6 lines
best regards, D.J. Barrow -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html