From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Al Stone <al.stone@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Olof Johansson <olof@lixom.net>,
Rob Herring <robherring2@gmail.com>,
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
Subject: Re: [PATCH v2 4/6] ACPI: ARM: exclude DMI calls
Date: Sat, 23 Nov 2013 16:38:54 +0000 [thread overview]
Message-ID: <20131123163854.GA1817@srcf.ucam.org> (raw)
In-Reply-To: <528FF15C.4060300@linaro.org>
On Fri, Nov 22, 2013 at 05:05:48PM -0700, Al Stone wrote:
> For reduced hardware mode, however, I have to rely on the underlying
> ACPICA reference implementation to behave properly. Right now, ACPICA
> relies on compile time changes to implement either reduced HW mode or
> legacy mode so I have to follow suit. When I looked at making ACPICA
> change behavior at runtime, the changes became more and more invasive.
> Since x86/ia64 depend on ACPICA to behave also, that seemed a far
> more dangerous approach to me.
Ugh. Really? People have been fairly careful about making sure that the
x86 SoC code is selected correctly at runtime, and losing that because
ACPICA is broken would be a shame. I think this is something that needs
to support runtime switching even if there's also support for building
kernels that only implement the reduced hardware profile.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2013-11-23 16:39 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 [this message]
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
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=20131123163854.GA1817@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=al.stone@linaro.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-acpi@vger.kernel.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).