From: Ondrej Zary <linux@rainbow-software.org>
To: Oliver Neukum <oliver@neukum.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
Daniel Ritz <daniel.ritz@gmx.ch>
Subject: Re: [0000/0003]full power management for usb touchscreens
Date: Tue, 22 Jun 2010 13:06:12 +0200 [thread overview]
Message-ID: <201006221306.13420.linux@rainbow-software.org> (raw)
In-Reply-To: <201006182041.54115.oliver@neukum.org>
On Friday 18 June 2010, Oliver Neukum wrote:
> Am Freitag, 18. Juni 2010 20:34:03 schrieb Ondrej Zary:
> > On Friday 18 June 2010 20:22:07 Oliver Neukum wrote:
> > > Am Donnerstag, 10. Juni 2010 16:13:51 schrieb Ondrej Zary:
> > > > > > I haven't tested the patches before. Now I tested them and the
> > > > > > Nexio touchscreen does not play well with suspend. It always
> > > > > > reconnects after resume from STR or hibernation. Autosuspend is
> > > > > > probably never activated at the URBs are submitted continuously.
> > > > >
> > > > > I see. Can you compile with CONFIG_USB_DEBUG and send me the log?
> > > >
> > > > This can't be fixed - no matter what you do, the device reconnects if
> > > > you stop talking to it.
> > >
> > > Have you tried setting it back to config 0?
> >
> > No, I haven't. It reconnects even if there's no driver loaded (e.g. older
> > kernel). I don't know if kernel sets configuration on all USB devices
> > upon connect (even if there's no driver).
>
> Yes, the kernel sets a configuration if the power budget allows it.
> You can set it back to 0 through sysfs and see what happens.
It disconnects and reconnects after bConfigurationValue is set to 0.
--
Ondrej Zary
next prev parent reply other threads:[~2010-06-22 11:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 13:13 [0000/0003]full power management for usb touchscreens Oliver Neukum
[not found] ` <201006071513.29478.oneukum-l3A5Bk7waGM@public.gmane.org>
2010-06-07 16:19 ` Dmitry Torokhov
[not found] ` <20100607161920.GA7706-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2010-06-08 12:49 ` Ondrej Zary
2010-06-09 13:40 ` Ondrej Zary
2010-06-09 16:36 ` Oliver Neukum
[not found] ` <201006091836.14136.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2010-06-10 11:33 ` Ondrej Zary
2010-06-10 13:46 ` Oliver Neukum
[not found] ` <201006101546.55460.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2010-06-10 14:13 ` Ondrej Zary
[not found] ` <201006101613.52736.linux-ZCIryABCsrmttCpgsWEBFmD2FQJk+8+b@public.gmane.org>
2010-06-10 14:25 ` Oliver Neukum
2010-06-18 18:22 ` Oliver Neukum
2010-06-18 18:34 ` Ondrej Zary
[not found] ` <201006182034.05793.linux-ZCIryABCsrmttCpgsWEBFmD2FQJk+8+b@public.gmane.org>
2010-06-18 18:41 ` Oliver Neukum
2010-06-22 11:06 ` Ondrej Zary [this message]
2010-06-22 13:24 ` Oliver Neukum
[not found] ` <201006221524.25084.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2010-06-22 13:43 ` Ondrej Zary
[not found] ` <201006221543.27169.linux-ZCIryABCsrmttCpgsWEBFmD2FQJk+8+b@public.gmane.org>
2010-06-24 6:56 ` Oliver Neukum
2010-06-29 13:51 ` Ondrej Zary
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=201006221306.13420.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=daniel.ritz@gmx.ch \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
/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;
as well as URLs for NNTP newsgroup(s).