linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hanjun.guo@linaro.org (Hanjun Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [Linaro-acpi] [PATCH v3 1/5] ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE to enable this ACPI mode
Date: Tue, 10 Dec 2013 23:05:03 +0800	[thread overview]
Message-ID: <52A72D9F.1070004@linaro.org> (raw)
In-Reply-To: <20131210123717.59493C40A27@trevor.secretlab.ca>

On 2013?12?10? 20:37, Grant Likely wrote:
> On Wed,  4 Dec 2013 14:22:03 -0700, al.stone at linaro.org wrote:
>> From: Al Stone <al.stone@linaro.org>
>>
>> To enable the hardware reduced mode of ACPI on some platforms (such as
>> ARM), we need to modify the kernel code and set ACPI_REDUCED_HARDWARE
>> to TRUE in the ACPICA source.
>>
>> This can be done more resonably by introducing a kernel config item
>> to enable/disable ACPI_REDUCED_HARDWARE.  We can then change the kernel
>> config instead of having to modify the kernel source directly to enable
>> the reduced hardware mode of ACPI.
>>
>> Lv Zheng suggested that this configuration item does not belong in ACPICA,
>> the upstream source for much of the ACPI internals, but rather to the
>> Linux kernel itself.  Hence, we introduce this flag so that we can make
>> ACPI_REDUCED_HARDWARE configurable.  For the details of the discussion,
>> please refer to: http://www.spinics.net/lists/linux-acpi/msg46369.html
>>
>> Support for X86 in hardware reduced mode is also provided to make it
>> simpler to debug this mode, and to provide for probable use in such
>> products.  Hardware reduced mode, despite the name, exists primarily
>> to allow newer platforms to use a much simpler form of ACPI that does
>> not require supporting the legacy of previous versions of the specification,
>> and is likely to be used more often in the near future as a result.
>>
>> Signed-off-by: Hanjun Guo <hanjun.guo@linaro.org>
>> Signed-off-by: Al Stone <al.stone@linaro.org>
>> ---
>>   drivers/acpi/Kconfig            | 8 ++++++++
>>   include/acpi/platform/aclinux.h | 6 ++++++
>>   2 files changed, 14 insertions(+)
>>
>> diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
>> index 5d92485..66e6bb2 100644
>> --- a/drivers/acpi/Kconfig
>> +++ b/drivers/acpi/Kconfig
>> @@ -343,6 +343,14 @@ config ACPI_BGRT
>>   	  data from the firmware boot splash. It will appear under
>>   	  /sys/firmware/acpi/bgrt/ .
>>   
>> +config ACPI_REDUCED_HARDWARE
>> +	bool "Hardware-reduced ACPI support"
>> +	depends on X86 || ARM || ARM64
>> +	help
>> +	This config adds support for Hardware-reduced ACPI. When this option
>> +	is selected, will generate a specialized version of ACPICA that ONLY
>> +	supports the ACPI "reduced hardware".
>> +
>>   source "drivers/acpi/apei/Kconfig"
>>   
>>   config ACPI_EXTLOG
>> diff --git a/include/acpi/platform/aclinux.h b/include/acpi/platform/aclinux.h
>> index 28f4f4d..a33f502 100644
>> --- a/include/acpi/platform/aclinux.h
>> +++ b/include/acpi/platform/aclinux.h
>> @@ -52,6 +52,12 @@
>>   
>>   #ifdef __KERNEL__
>>   
>> +/* Compile for reduced hardware mode if requested for this kernel config */
>> +
>> +#ifdef CONFIG_ACPI_REDUCED_HARDWARE
>> +#define ACPI_REDUCED_HARDWARE 1
>> +#endif
> Will this change the way ACPICA is compiled? Will it disable
> non-hardware-reduced mode?

Both yes. ACPICA supports reduced hardware mode when
ACPI_REDUCED_HARWARE is TRUE at compile time. There is
no way to support both normal ACPI and hardware reduced
ACPI with single binary image for now.

> If so, then this is a big problem. Enabling
> the hardware reduced feature should *not* break normal ACPI usage.

It will break normal ACPI usage but it is ok I think. Since
lots of features are not supported in the hardware in hardware
reduced mode, and normal ACPI will not run probably such as
leading kernel panic when refer to some registers which are not
exist on reduced hardware, we should introduce this kernel
config and modify the ACPI drivers to avoid such failures.

Thanks
Hanjun

  reply	other threads:[~2013-12-10 15:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 21:22 [PATCH v3 0/5] Hardware Reduced Mode Cleanup for ACPI al.stone at linaro.org
     [not found] ` < 1386192127-28564-2-git-send-email-al.stone@linaro.org>
2013-12-04 21:22 ` [PATCH v3 1/5] ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE to enable this ACPI mode al.stone at linaro.org
2013-12-10 12:35   ` [Linaro-acpi] " Grant Likely
2013-12-10 12:37   ` Grant Likely
2013-12-10 15:05     ` Hanjun Guo [this message]
2013-12-10 22:49       ` Grant Likely
2013-12-11  2:06         ` Rob Herring
2013-12-11  8:33           ` Graeme Gregory
2013-12-12 20:31         ` Al Stone
2013-12-04 21:22 ` [PATCH v3 2/5] ACPI: bus master reload not supported in reduced HW mode al.stone at linaro.org
2013-12-10 12:38   ` [Linaro-acpi] " Grant Likely
2013-12-04 21:22 ` [PATCH v3 3/5] ACPI: HW reduced mode does not allow use of the FADT sci_interrupt field al.stone at linaro.org
2013-12-04 21:22 ` [PATCH v3 4/5] ACPI: in HW reduced mode, using FADT PM information is not allowed al.stone at linaro.org
2013-12-04 21:22 ` [PATCH v3 5/5] ACPI: do not map/unmap memory regions for FADT entries in reduced HW mode al.stone at linaro.org
2013-12-10 12:40   ` [Linaro-acpi] " Grant Likely

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=52A72D9F.1070004@linaro.org \
    --to=hanjun.guo@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).