linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Stone <al.stone@linaro.org>
To: Rob Herring <robherring2@gmail.com>
Cc: 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: Fri, 22 Nov 2013 11:03:17 -0700	[thread overview]
Message-ID: <528F9C65.7010302@linaro.org> (raw)
In-Reply-To: <CAL_JsqKbL2Zhpbg8wp4qZekZwJO20njUO4nCzzz1KZexmK9tLQ@mail.gmail.com>

On 11/22/2013 06:25 AM, Rob Herring wrote:
> On Thu, Nov 21, 2013 at 6:41 PM,  <al.stone@linaro.org> wrote:
>> From: Al Stone <al.stone@linaro.org>
>>
>> Modified #ifdef so that DMI is not used on ARM platforms which
>> are currently implementing ACPI reduced HW mode.
>
> It is really not allowed or is optional? There are various people that
> want DMI tables on ARM.
>
> Rob

True.  DMI is optional.  I see it as orthogonal to
reduced HW mode; I have to hope that when DMI patches
are forthcoming they'll do the right thing here.

Is there a better way to do this in the #if ?

>> Signed-off-by: Al Stone <al.stone@linaro.org>
>> ---
>>   include/linux/dmi.h | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/include/linux/dmi.h b/include/linux/dmi.h
>> index f820f0a..a03deb8 100644
>> --- a/include/linux/dmi.h
>> +++ b/include/linux/dmi.h
>> @@ -83,7 +83,7 @@ struct dmi_device {
>>          void *device_data;      /* Type specific data */
>>   };
>>
>> -#ifdef CONFIG_DMI
>> +#if IS_ENABLED(CONFIG_DMI) && !IS_ENABLED(CONFIG_ACPI_REDUCED_HARDWARE)
>>
>>   struct dmi_dev_onboard {
>>          struct dmi_device dev;
>> --
>> 1.8.3.1
>>
>>
>> _______________________________________________
>> linaro-kernel mailing list
>> linaro-kernel@lists.linaro.org
>> http://lists.linaro.org/mailman/listinfo/linaro-kernel


-- 
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Linaro Enterprise Group
al.stone@linaro.org
-----------------------------------

  reply	other threads:[~2013-11-22 18:03 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 [this message]
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
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=528F9C65.7010302@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=patches@linaro.org \
    --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).