From: Shuah Khan <shuahkhan@gmail.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: shuahkhan@gmail.com, lenb@kernel.org, linux-acpi@vger.kernel.org,
bhelgaas@google.com, liuj97@gmail.com, andi@firstfloor.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 6/6] ACPI: Set hotplug _OST support bit to _OSC
Date: Thu, 24 May 2012 12:27:00 -0600 [thread overview]
Message-ID: <1337884020.2718.89.camel@lorien2> (raw)
In-Reply-To: <1337826324-16802-7-git-send-email-toshi.kani@hp.com>
On Wed, 2012-05-23 at 20:25 -0600, Toshi Kani wrote:
> When ACPI_HOTPLUG_OST is defined, set hotplug _OST support bit
> OSC_SB_HOTPLUG_OST_SUPPORT to indicate that the OS supports hotplug
> _OST by calling the platform-wide ACPI Operating System Capabilities
> (_OSC).
>
> Signed-off-by: Toshi Kani <toshi.kani@hp.com>
> ---
> drivers/acpi/bus.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
> index 3188da3..3d4fc7a 100644
> --- a/drivers/acpi/bus.c
> +++ b/drivers/acpi/bus.c
> @@ -548,6 +548,10 @@ static void acpi_bus_osc_support(void)
> capbuf[OSC_SUPPORT_TYPE] |= OSC_SB_PPC_OST_SUPPORT;
> #endif
>
> +#ifdef ACPI_HOTPLUG_OST
> + capbuf[OSC_SUPPORT_TYPE] |= OSC_SB_HOTPLUG_OST_SUPPORT;
> +#endif
Why isn't firmware response to _OSC checked to make sure firmware also
supports _OST? My general comments about compile time switch that is
enabled only a few cases _OST Ejection/Insertion is intended to be used
are applicable here.
-- Shuah
> +
> if (!ghes_disable)
> capbuf[OSC_SUPPORT_TYPE] |= OSC_SB_APEI_SUPPORT;
> if (ACPI_FAILURE(acpi_get_handle(NULL, "\\_SB", &handle)))
next prev parent reply other threads:[~2012-05-24 18:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 2:25 [PATCH v4 0/6] ACPI: Add _OST support for ACPI hotplug Toshi Kani
2012-05-24 2:25 ` [PATCH v4 1/6] ACPI: Add an interface to evaluate _OST Toshi Kani
2012-05-24 18:09 ` Shuah Khan
2012-05-24 20:40 ` Toshi Kani
2012-05-24 2:25 ` [PATCH v4 2/6] ACPI: Add _OST support for sysfs eject Toshi Kani
2012-05-24 2:25 ` [PATCH v4 3/6] ACPI: Add _OST support for ACPI CPU hotplug Toshi Kani
2012-05-24 2:25 ` [PATCH v4 4/6] ACPI: Add _OST support for ACPI memory hotplug Toshi Kani
2012-05-24 18:21 ` Shuah Khan
2012-05-24 20:25 ` Toshi Kani
2012-05-24 2:25 ` [PATCH v4 5/6] ACPI: Add _OST support for ACPI container hotplug Toshi Kani
2012-06-05 4:39 ` Yasuaki Ishimatsu
2012-06-05 15:36 ` Kani, Toshimitsu
2012-06-11 1:55 ` Yasuaki Ishimatsu
2012-06-11 7:12 ` Kani, Toshimitsu
2012-05-24 2:25 ` [PATCH v4 6/6] ACPI: Set hotplug _OST support bit to _OSC Toshi Kani
2012-05-24 18:27 ` Shuah Khan [this message]
2012-05-24 20:53 ` Toshi Kani
2012-05-24 17:34 ` [PATCH v4 0/6] ACPI: Add _OST support for ACPI hotplug Shuah Khan
2012-05-24 19:48 ` Toshi Kani
2012-05-29 22:27 ` Moore, Robert
2012-05-29 22:44 ` Shuah Khan
2012-05-29 23:43 ` Toshi Kani
2012-05-30 2:56 ` Moore, Robert
2012-05-30 14:11 ` Toshi Kani
2012-05-30 15:24 ` Shuah Khan
2012-05-30 17:19 ` Toshi Kani
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=1337884020.2718.89.camel@lorien2 \
--to=shuahkhan@gmail.com \
--cc=andi@firstfloor.org \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=toshi.kani@hp.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).