From: Al Stone <al.stone@linaro.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Zheng, Lv" <lv.zheng@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Olof Johansson <olof@lixom.net>,
Rob Herring <robherring2@gmail.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Linaro Patches <patches@linaro.org>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
"linaro-acpi@lists.linaro.org" <linaro-acpi@lists.linaro.org>
Subject: Re: [PATCH v2 4/6] ACPI: ARM: exclude DMI calls
Date: Mon, 25 Nov 2013 11:01:08 -0700 [thread overview]
Message-ID: <52939064.6090803@linaro.org> (raw)
In-Reply-To: <20131125174552.GA7417@srcf.ucam.org>
On 11/25/2013 10:45 AM, Matthew Garrett wrote:
> On Mon, Nov 25, 2013 at 10:43:27AM -0700, Al Stone wrote:
>> On 11/25/2013 08:30 AM, Matthew Garrett wrote:
>>> Is ACPI_REDUCED_HARDWARE supposed to indicate support for the reduced
>>> hardware profile, or that the platform *only* implements the reduced
>>> hardware profile?
>>
>> From what I can see in ACPICA, ACPI_REDUCED_HARDWARE indicates the
>> platform *only* implements the reduced hardware profile. This *seems*
>> to be consistent with the specification -- see 3.11.1, second bullet,
>> for example:
>
> Ok, so a kernel built without ACPI_REDUCED_HARDWARE would still support
> the reduced hardware profile?
Let me check on that. The reduced hardware profile is a pretty
strict subset, and I think I can see a way where I could force
selecting the reduced HW profile on boot if the kernel has been
built *without* ACPI_REDUCED_HARDWARE. What I am not convinced
of is that all of the proper guards are in place in ACPICA -- I
trust that they have been, but I would like to double check.
If I can get that to work properly, I'll add it to this patch set.
>> ...if by "not supported" one takes that to mean "does not exist when
>> compiled." I can look at the ACPICA code again, just the same; perhaps
>> there is some reasonable way to at least select one or the other at boot
>> as the first step, and then allow switching between modes as a later
>> step.
>
> I don't think you'd ever want to switch after init time. There's a flag
> in the FADT that indicates whether a system is implementing the reduced
> hardware profile or not.
>
Agreed. I could see it as something to use when experimenting perhaps,
but I think just allowing the switch at boot would cover the majority
of the use cases.
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Linaro Enterprise Group
al.stone@linaro.org
-----------------------------------
next prev parent reply other threads:[~2013-11-25 18:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 0:41 [PATCH v2 0/6] Hardware Reduced Mode cleanup for ACPI al.stone
[not found] ` < 528F9C65.7010302@linaro.org>
[not found] ` < CAOesGMgFBRjO++JSP0ddKKQ2RfG8V4fb97Hd+Oqwixi_Tt7Qwg@mail.gmail.com>
2013-11-22 0:41 ` [PATCH v2 1/6] ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE to enable this ACPI mode al.stone
2013-11-22 0:41 ` [PATCH v2 2/6] ACPI: bus master reload not supported in reduced HW mode al.stone
2013-11-22 3:06 ` Hanjun Guo
2013-11-27 22:35 ` Al Stone
2013-11-22 0:41 ` [PATCH v2 3/6] ACPI: HW reduced mode does not allow use of the FADT sci_interrupt field al.stone
2013-11-22 0:41 ` [PATCH v2 4/6] ACPI: ARM: exclude DMI calls al.stone
2013-11-22 13:25 ` Rob Herring
2013-11-22 18:03 ` Al Stone
2013-11-22 18:53 ` Olof Johansson
2013-11-22 23:15 ` Rafael J. Wysocki
2013-11-23 0:05 ` Al Stone
2013-11-23 16:38 ` Matthew Garrett
2013-11-25 5:10 ` Zheng, Lv
2013-11-25 15:30 ` Matthew Garrett
2013-11-25 17:43 ` Al Stone
2013-11-25 17:45 ` Matthew Garrett
2013-11-25 18:01 ` Al Stone [this message]
2013-12-04 1:30 ` Al Stone
2013-12-04 1:34 ` Matthew Garrett
2013-12-10 12:45 ` Grant Likely
2013-11-22 0:41 ` [PATCH v2 5/6] ACPI: do not reserve memory regions for some FADT entries in HW reduced mode al.stone
2013-11-22 0:41 ` [PATCH v2 6/6] ACPI: in HW reduced mode, using FADT PM information is not allowed al.stone
2013-11-22 23:18 ` [PATCH v2 0/6] Hardware Reduced Mode cleanup for ACPI Rafael J. Wysocki
2013-11-22 23:33 ` Al Stone
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=52939064.6090803@linaro.org \
--to=al.stone@linaro.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=mjg59@srcf.ucam.org \
--cc=olof@lixom.net \
--cc=patches@linaro.org \
--cc=rjw@rjwysocki.net \
--cc=robherring2@gmail.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).