From: Jiang Liu <liuj97@gmail.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org, bhelgaas@google.com,
shuahkhan@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/7] ACPI: Add CONFIG_HOTPLUG_OST option
Date: Fri, 11 May 2012 00:40:48 +0800 [thread overview]
Message-ID: <4FABEF90.4040602@gmail.com> (raw)
In-Reply-To: <1336507944-10219-2-git-send-email-toshi.kani@hp.com>
On 05/09/2012 04:12 AM, Toshi Kani wrote:
> Added CONFIG_ACPI_HOTPLUG_OPT option. When this config option is disabled,
> this patchset has no effect on the platform. This option is disabled by
> default. The dependency list assures consistent behavior among CPU, memory
> and container hotplug operations with regarding the _OST support.
Seems also need to enhance the acpiphp driver for PCI hotplug operations too.
acpiphp driver is also based on the ACPI device hotplug model.
>
> Signed-off-by: Toshi Kani <toshi.kani@hp.com>
> ---
> drivers/acpi/Kconfig | 14 ++++++++++++++
> 1 files changed, 14 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
> index 47768ff..1e3a756 100644
> --- a/drivers/acpi/Kconfig
> +++ b/drivers/acpi/Kconfig
> @@ -351,6 +351,20 @@ config ACPI_HOTPLUG_MEMORY
> To compile this driver as a module, choose M here:
> the module will be called acpi_memhotplug.
>
> +config ACPI_HOTPLUG_OST
> + bool "Hotplug Status Indication Support"
> + depends on ACPI_HOTPLUG_CPU
> + depends on ACPI_HOTPLUG_MEMORY
> + depends on ACPI_CONTAINER
> + default n
> + help
> + This option enables the use of the ACPI OSPM Status Indication
> + (_OST), if available, for the platform to determine the status
> + of various hotplug operations. Some platforms may require this
> + option be enabled to track the status of hotplug operations.
> + This option has no effect when the platform does not support
> + _OST.
> +
> config ACPI_SBS
> tristate "Smart Battery System"
> depends on X86
next prev parent reply other threads:[~2012-05-10 16:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 20:12 [PATCH v2 0/7] ACPI: Add _OST support for ACPI hotplug Toshi Kani
2012-05-08 20:12 ` [PATCH v2 1/7] ACPI: Add CONFIG_HOTPLUG_OST option Toshi Kani
2012-05-10 16:40 ` Jiang Liu [this message]
2012-05-10 17:26 ` Toshi Kani
2012-05-10 17:43 ` Jiang Liu
2012-05-10 18:20 ` Toshi Kani
2012-05-11 0:15 ` Jiang Liu
2012-05-08 20:12 ` [PATCH v2 2/7] ACPI: Add an interface to evaluate _OST Toshi Kani
2012-05-08 20:12 ` [PATCH v2 3/7] ACPI: Add _OST support for sysfs eject Toshi Kani
2012-05-09 16:46 ` Shuah Khan
2012-05-09 18:16 ` Toshi Kani
2012-05-10 15:40 ` Shuah Khan
2012-05-10 16:34 ` Toshi Kani
2012-05-10 16:55 ` Shuah Khan
2012-05-10 17:41 ` Toshi Kani
2012-05-08 20:12 ` [PATCH v2 4/7] ACPI: Add _OST support for ACPI CPU hotplug Toshi Kani
2012-05-08 20:12 ` [PATCH v2 5/7] ACPI: Add _OST support for ACPI memory hotplug Toshi Kani
2012-05-08 20:12 ` [PATCH v2 6/7] ACPI: Add _OST support for ACPI container hotplug Toshi Kani
2012-05-08 20:12 ` [PATCH v2 7/7] ACPI: Set hotplug _OST support bit to _OSC Toshi Kani
2012-05-09 17:36 ` [PATCH v2 0/7] ACPI: Add _OST support for ACPI hotplug Shuah Khan
2012-05-09 18:44 ` 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=4FABEF90.4040602@gmail.com \
--to=liuj97@gmail.com \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuahkhan@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).