summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorDmitry Torokhov <dmitry.torokhov@gmail.com>2010-10-04 16:13:20 +0000
committerHenrik Rydberg <rydberg@euromail.se>2010-10-15 15:13:41 +0200
commit2c06b47c113544965a8d99078ae2c8bda883f72b (patch)
treed3132226a41526064c5bede37bcff416d4b8e5a1 /scripts
parentb869fda960cc2eba37aa42678c42f378c626c34c (diff)
wacom + runtime PM = AA deadlock
On Tue, Sep 14, 2010 at 08:07:39AM +0200, Oliver Neukum wrote: > Am Dienstag, 14. September 2010, 02:52:10 schrieb Dmitry Torokhov: > > On Mon, Sep 13, 2010 at 09:20:23PM +0200, Oliver Neukum wrote: > > > Am Montag, 13. September 2010, 19:10:47 schrieb Dmitry Torokhov: > > > > > > > I think this introduces significant change in behavior though - before > > > > we did not do usb_autopm_put_interface() on successful open, basically > > > > disabling autopm facilities, right? > > > > > > Right. Which makes no sense at all. You'd better remove anything related > > > to runtime PM and not set supports_autosuspend for that. > > > > > > > That not what I meant, I do not want to remove autopm, it's just it was > > effectively disabled and if we fix it we might start getting some > > regression reports ;) > > True. So currently we have > > - a deadlock > - disabled runtime power management > > We need to fix the deadlock. We can fix it retaining a disabled > runtime power management. Or we can fix it fixing the runtime > power management at the same time. However this opens > the door to regressions. So for now I really suggest removing > it from the driver and reintroduce it properly for the next merge > window. > Lost track of this issue for a while. So I think we still need to fix the deadlock for .36 and I think that the following will do that. Then we'll adjust the driver to actually enable runtime PM for .37. Thanks. Acked-by: Oliver Neukum <oneukum@suse.de>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions