From: al.stone@linaro.org (al.stone at linaro.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/5] ACPI: arm64: use the arch-specific ACPI _OSI method and ACPI blacklist
Date: Tue, 3 Feb 2015 17:21:43 -0700 [thread overview]
Message-ID: <1423009304-5007-5-git-send-email-al.stone@linaro.org> (raw)
In-Reply-To: <1423009304-5007-1-git-send-email-al.stone@linaro.org>
From: Al Stone <al.stone@linaro.org>
Set the defaults for the arm64 kernel so that the arch-specific _OSI
method and blacklist are always used for ACPI.
Signed-off-by: Al Stone <al.stone@linaro.org>
---
arch/arm64/Kconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 915aa16..d01d3f7 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -1,5 +1,7 @@
config ARM64
def_bool y
+ select ACPI_ARCH_SPECIFIC_OSI if ACPI
+ select ACPI_ARCH_SPECIFIC_BLACKLIST if ACPI
select ACPI_REDUCED_HARDWARE_ONLY if ACPI
select ARCH_BINFMT_ELF_RANDOMIZE_PIE
select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
--
2.1.0
next prev parent reply other threads:[~2015-02-04 0:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 0:21 [PATCH v2 0/5] Start deprecating _OSI on new architectures al.stone at linaro.org
2015-02-04 0:21 ` [PATCH v2 1/5] ACPI: move acpi_os_handler() so it can be made arch-dependent later al.stone at linaro.org
2015-02-04 13:50 ` Rafael J. Wysocki
2015-02-04 22:44 ` Al Stone
2015-02-04 23:21 ` Rafael J. Wysocki
2015-02-04 23:49 ` Al Stone
2015-02-04 0:21 ` [PATCH v2 2/5] ACPI: move _OSI support functions to allow arch-dependent implementation al.stone at linaro.org
2015-02-04 0:21 ` [PATCH v2 3/5] ACPI: add arch-specific compilation for _OSI and the blacklist al.stone at linaro.org
2015-02-04 14:00 ` Rafael J. Wysocki
2015-02-04 14:03 ` Rafael J. Wysocki
2015-02-04 22:46 ` Al Stone
2015-02-04 0:21 ` al.stone at linaro.org [this message]
2015-02-04 0:21 ` [PATCH v2 5/5] ACPI: arm64: use "Linux" as ACPI_OS_NAME for _OS on arm64 al.stone at linaro.org
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=1423009304-5007-5-git-send-email-al.stone@linaro.org \
--to=al.stone@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).