From: al.stone@linaro.org (Al Stone)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 8/9] ACPI: arm64: use an arch-specific ACPI _OSI method and ACPI blacklist
Date: Mon, 02 Mar 2015 12:00:21 -0700 [thread overview]
Message-ID: <54F4B345.6020001@linaro.org> (raw)
In-Reply-To: <20150302172939.GC7919@arm.com>
On 03/02/2015 10:29 AM, Will Deacon wrote:
> Hi Al,
>
> On Wed, Feb 25, 2015 at 12:36:24AM +0000, al.stone at linaro.org wrote:
>> diff --git a/arch/arm64/kernel/acpi-blacklist.c b/arch/arm64/kernel/acpi-blacklist.c
>> new file mode 100644
>> index 0000000..1be6a56
>> --- /dev/null
>> +++ b/arch/arm64/kernel/acpi-blacklist.c
>> @@ -0,0 +1,20 @@
>> +/*
>> + * ARM64 Specific ACPI Blacklist Support
>> + *
>> + * Copyright (C) 2015, Linaro Ltd.
>> + * Author: Al Stone <al.stone@linaro.org>
>> + *
>> + * This program is free software; you can redistribute it and/or modify
>> + * it under the terms of the GNU General Public License version 2 as
>> + * published by the Free Software Foundation.
>> + */
>> +
>> +#define pr_fmt(fmt) "ACPI: " fmt
>> +
>> +#include <linux/acpi.h>
>> +
>> +/* The arm64 ACPI blacklist is currently empty. */
>> +int __init acpi_blacklisted(void)
>> +{
>> + return 0;
>> +}
>> diff --git a/arch/arm64/kernel/acpi-osi.c b/arch/arm64/kernel/acpi-osi.c
>> new file mode 100644
>> index 0000000..bb351f4
>> --- /dev/null
>> +++ b/arch/arm64/kernel/acpi-osi.c
>> @@ -0,0 +1,25 @@
>> +/*
>> + * ARM64 Specific ACPI _OSI Support
>> + *
>> + * Copyright (C) 2015, Linaro Ltd.
>> + * Author: Al Stone <al.stone@linaro.org>
>> + *
>> + * This program is free software; you can redistribute it and/or modify
>> + * it under the terms of the GNU General Public License version 2 as
>> + * published by the Free Software Foundation.
>> + */
>> +
>> +#define pr_fmt(fmt) "ACPI: " fmt
>> +
>> +#include <linux/acpi.h>
>> +
>> +/*
>> + * Consensus is to deprecate _OSI for all new ACPI-supported architectures.
>> + * So, for arm64, reduce _OSI to a warning message, and tell the firmware
>> + * nothing of value.
>> + */
>> +u32 acpi_osi_handler(acpi_string interface, u32 supported)
>> +{
>> + pr_warn("_OSI was called, but is deprecated for this architecture.\n");
>> + return false;
>> +}
>
> This kinda feels backwards to me. If _OSI is going away, then the default
> should be "the architecture doesn't need to do anything", rather than have
> new architectures defining a bunch of empty, useless stub code.
>
> Anyway we could make this the default in core code and have architectures
> that *do* want _OSI override that behaviour, instead of the other way around?
>
> Cheers,
>
> Will
>
We could do that; I personally don't have a strong preference either way,
so I'm inclined to make it whatever structure Rafael thinks is proper since
it affects ACPI code most. That being said, the current patch structure
made sense to me since it wasn't distorting existing code much -- and given
the pure number of x86/ia64 machines vs ARM machines using ACPI, that seemed
the more cautious approach.
@Rafael: do you have an opinion/preference?
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Linaro Enterprise Group
al.stone at linaro.org
-----------------------------------
next prev parent reply other threads:[~2015-03-02 19:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 0:36 [PATCH v3 0/9] Start deprecating _OSI on new architectures al.stone at linaro.org
2015-02-25 0:36 ` [PATCH v3 1/9] ACPI: fix all errors reported by cleanpatch.pl in osl.c al.stone at linaro.org
2015-02-25 12:47 ` Hanjun Guo
2015-03-04 23:04 ` Rafael J. Wysocki
2015-03-04 23:56 ` Al Stone
2015-03-05 0:25 ` Rafael J. Wysocki
2015-03-05 0:06 ` Al Stone
2015-02-25 0:36 ` [PATCH v3 2/9] ACPI: clear up warnings on use of printk reported by checkpatch.pl al.stone at linaro.org
2015-02-25 12:55 ` Hanjun Guo
2015-02-25 20:56 ` Al Stone
2015-02-25 0:36 ` [PATCH v3 3/9] ACPI: clean up checkpatch warnings for various bits of syntax al.stone at linaro.org
2015-02-25 12:59 ` [Linaro-acpi] " Hanjun Guo
2015-02-25 0:36 ` [PATCH v3 4/9] ACPI: clean up checkpatch warnings for items with possible semantic value al.stone at linaro.org
2015-02-25 13:08 ` [Linaro-acpi] " Hanjun Guo
2015-02-25 20:57 ` Al Stone
2015-02-25 0:36 ` [PATCH v3 5/9] ACPI: move acpi_os_handler() so it can be made arch-dependent later al.stone at linaro.org
2015-02-25 13:47 ` [Linaro-acpi] " Hanjun Guo
2015-02-25 0:36 ` [PATCH v3 6/9] ACPI: move _OSI support functions to allow arch-dependent implementation al.stone at linaro.org
2015-03-04 23:09 ` Rafael J. Wysocki
2015-02-25 0:36 ` [PATCH v3 7/9] ACPI: enable arch-specific compilation for _OSI and the blacklist al.stone at linaro.org
2015-03-04 23:11 ` Rafael J. Wysocki
2015-02-25 0:36 ` [PATCH v3 8/9] ACPI: arm64: use an arch-specific ACPI _OSI method and ACPI blacklist al.stone at linaro.org
2015-03-02 17:29 ` Will Deacon
2015-03-02 19:00 ` Al Stone [this message]
2015-03-04 23:14 ` Rafael J. Wysocki
2015-03-05 10:17 ` Will Deacon
2015-03-05 12:56 ` Rafael J. Wysocki
2015-03-04 23:16 ` Rafael J. Wysocki
2015-02-25 0:36 ` [PATCH v3 9/9] ACPI: arm64: use "Linux" as ACPI_OS_NAME for _OS on arm64 al.stone at linaro.org
2015-03-04 23:17 ` 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=54F4B345.6020001@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).