All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org
Subject: Re: [RFC] Wakeup for PNP
Date: Tue, 2 Mar 2010 16:08:23 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.1003021606310.1326-100000__10368.6162656688$1267564179$gmane$org@iolanthe.rowland.org> (raw)
In-Reply-To: <201003021341.58988.bjorn.helgaas@hp.com>

On Tue, 2 Mar 2010, Bjorn Helgaas wrote:

> > Does this look reasonable?  I don't know anything about PNPBIOS or 
> > ISAPNP, so it handles only PNPACPI.  But at least it's a starting 
> > point -- and it does enable my system to wake up in response to 
> > hitting a key.
> 
> I don't know much about power management, but your patch looks
> reasonable to me.

Thanks.

> > --- usb-2.6.orig/drivers/pnp/pnpacpi/core.c
> > +++ usb-2.6/drivers/pnp/pnpacpi/core.c
> > @@ -121,12 +121,27 @@ static int pnpacpi_disable_resources(str
> >  }
> >  
> >  #ifdef CONFIG_ACPI_SLEEP
> > +static bool pnpacpi_can_wakeup(struct pnp_dev *dev)
> > +{
> > +	acpi_handle handle = DEVICE_ACPI_HANDLE(&dev->dev);
> 
> I would have used:
> 
> 	struct acpi_device *acpi_dev = dev->data;
> 	acpi_handle handle = acpi_dev->handle;
> 
> here because that's what the rest of the PNPACPI code does.

Ah yes.  I just copied the code from the corresponding PCI function 
without thinking about it very much.  I'll update the patch and wait to 
hear from other people.

Alan Stern

  parent reply	other threads:[~2010-03-02 21:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201002212139.39746.rjw@sisk.pl>
2010-02-22 16:33 ` Two problems with system sleep Alan Stern
2010-02-22 18:45   ` Rafael J. Wysocki
2010-02-22 18:45   ` Rafael J. Wysocki
2010-02-22 21:33     ` Alan Stern
2010-02-22 22:00       ` Rafael J. Wysocki
2010-02-22 22:17         ` Alan Stern
2010-02-22 22:35           ` Rafael J. Wysocki
2010-02-22 22:35           ` Rafael J. Wysocki
2010-02-23 16:12             ` Alan Stern
2010-02-23 21:02               ` Rafael J. Wysocki
2010-02-23 21:35                 ` Alan Stern
2010-02-23 23:08                   ` Rafael J. Wysocki
2010-02-24 16:59                     ` Alan Stern
2010-02-23 21:49                 ` Dmitry Torokhov
2010-02-24 15:39                   ` Alan Stern
2010-03-02 20:13                   ` [RFC] Wakeup for PNP Alan Stern
2010-03-02 20:41                     ` Bjorn Helgaas
2010-03-02 20:41                     ` Bjorn Helgaas
2010-03-02 21:08                       ` Alan Stern
2010-03-02 21:08                       ` Alan Stern [this message]
2010-03-02 21:31                     ` Dmitry Torokhov
2010-03-03 15:29                       ` Alan Stern
2010-03-03 15:29                       ` Alan Stern
2010-03-09  7:45                         ` Dmitry Torokhov
2010-03-09  7:45                         ` Dmitry Torokhov
2010-03-02 21:31                     ` Dmitry Torokhov
2010-02-22 16:33 ` Two problems with system sleep Alan Stern

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='Pine.LNX.4.44L0.1003021606310.1326-100000__10368.6162656688$1267564179$gmane$org@iolanthe.rowland.org' \
    --to=stern@rowland.harvard.edu \
    --cc=bjorn.helgaas@hp.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.