From: Andrew Murray <andrew.murray@arm.com>
To: linux-pci@vger.kernel.org
Cc: bhelgaas@google.com, thierry.reding@avionic-design.de,
thomas.petazzoni@free-electrons.com, rjw@sisk.pl,
jbarnes@virtuousgeek.org
Subject: PME and dependency on ACPI
Date: Thu, 31 Jan 2013 14:23:03 +0000 [thread overview]
Message-ID: <20130131142303.GA29628@arm.com> (raw)
I think that PME may place an unnecessary dependency on ACPI...
in drivers/pci/pcie/Kconfig:
config PCIE_PME
def_bool y
depends on PCIEPORTBUS && PM_RUNTIME && ACPI
and drivers/pci/pcie/pme.c:
#include <linux/acpi.h>
#include <linux/pci-acpi.h>
On an ARM platform I can remove the #include's and remove the Kconfig
dependency on ACPI and PME springs into life.
Is there any other reason why ACPI may be needed here?
Andrew Murray
next reply other threads:[~2013-01-31 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 14:23 Andrew Murray [this message]
2013-01-31 20:59 ` PME and dependency on ACPI Rafael J. Wysocki
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=20130131142303.GA29628@arm.com \
--to=andrew.murray@arm.com \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=thierry.reding@avionic-design.de \
--cc=thomas.petazzoni@free-electrons.com \
/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).