From: Huang Ying <ying.huang@intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH RESEND] ACPI/PCI: Make PCI devices notified when its power resource turned on
Date: Tue, 06 Nov 2012 08:33:11 +0800 [thread overview]
Message-ID: <1352161991.31033.122.camel@yhuang-dev> (raw)
In-Reply-To: <CAErSpo5zZdxeUFtsKjfb+FcLvAWD-MBorSwTppge9HQ5GCL7_g@mail.gmail.com>
On Mon, 2012-11-05 at 17:02 -0700, Bjorn Helgaas wrote:
> On Wed, Sep 26, 2012 at 7:59 AM, Huang Ying <ying.huang@intel.com> wrote:
> > Sorry for bothering. It appears that this patch should go through ACPI
> > tree because code changed are under drivers/acpi.
> >
> > A set of power resources may be shared by multiple devices. When all
> > devices share one set of power resources is put into D3_COLD state,
> > the power resources will be turned off. When one of the device is
> > waked, the power resource will be turned on and all devices share it
> > will be powered on to D0uninitialized state. These devices should be
> > resumed, so that they can get opportunity to go to low power state
> > later.
> >
> > Signed-off-by: Huang Ying <ying.huang@intel.com>
> > Acked-by: Rafael J. Wysocki <rjw@sisk.pl>
> > Cc: Bjorn Helgaas <bhelgaas@google.com>
>
> I had applied this to my for-linus branch, headed for v3.7, but had to
> drop it because it introduced these warnings:
>
> drivers/acpi/pci_bind.c: In function 'acpi_pci_unbind':
> drivers/acpi/pci_bind.c:48:2: warning: passing argument 1 of
> 'acpi_power_resource_unregister_device' from incompatible pointer type
> [enabled by default]
> include/acpi/acpi_bus.h:346:6: note: expected 'struct device *' but
> argument is of type 'struct pci_dev *'
> drivers/acpi/pci_bind.c: In function 'acpi_pci_bind':
> drivers/acpi/pci_bind.c:75:2: warning: passing argument 1 of
> 'acpi_power_resource_register_device' from incompatible pointer type
> [enabled by default]
> include/acpi/acpi_bus.h:345:5: note: expected 'struct device *' but
> argument is of type 'struct pci_dev *'
>
> Apparently this wasn't tested :-(
It's my fault. I apologize for that. It appear that I turn a RFC to
PATCH without testing. Will be more careful for next time.
Best Regards,
Huang Ying
> > ---
> > drivers/acpi/pci_bind.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > --- a/drivers/acpi/pci_bind.c
> > +++ b/drivers/acpi/pci_bind.c
> > @@ -45,6 +45,7 @@ static int acpi_pci_unbind(struct acpi_d
> >
> > device_set_run_wake(&dev->dev, false);
> > pci_acpi_remove_pm_notifier(device);
> > + acpi_power_resource_unregister_device(dev, device->handle);
> >
> > if (!dev->subordinate)
> > goto out;
> > @@ -71,6 +72,7 @@ static int acpi_pci_bind(struct acpi_dev
> > return 0;
> >
> > pci_acpi_add_pm_notifier(device, dev);
> > + acpi_power_resource_register_device(dev, device->handle);
> > if (device->wakeup.flags.run_wake)
> > device_set_run_wake(&dev->dev, true);
> >
prev parent reply other threads:[~2012-11-06 0:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 13:59 [PATCH RESEND] ACPI/PCI: Make PCI devices notified when its power resource turned on Huang Ying
2012-11-06 0:02 ` Bjorn Helgaas
2012-11-06 0:33 ` Huang Ying [this message]
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=1352161991.31033.122.camel@yhuang-dev \
--to=ying.huang@intel.com \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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).