public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org, bhelgaas@google.com,
	shuahkhan@gmail.com, liuj97@gmail.com, andi@firstfloor.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 5/6] ACPI: Add _OST support for ACPI container hotplug
Date: Tue, 05 Jun 2012 13:39:49 +0900	[thread overview]
Message-ID: <4FCD8D95.1060700@jp.fujitsu.com> (raw)
In-Reply-To: <1337826324-16802-6-git-send-email-toshi.kani@hp.com>

Hi Toshi,

2012/05/24 11:25, Toshi Kani wrote:
> Changed container_notify_cb() to call ACPI _OST method when ACPI
> container hotplug operation has completed. Slightly restructured
> the code with the same logic. The function sets eject_pending bit
> for an eject request since it does not initiate hot-remove operation.
> This bit is checked by the sysfs eject handler to determine if the
> request is originated from an ACPI eject notification.
> 
> Signed-off-by: Toshi Kani<toshi.kani@hp.com>
> ---
>   drivers/acpi/container.c |   43 ++++++++++++++++++++++++++++---------------
>   1 files changed, 28 insertions(+), 15 deletions(-)
> 
> diff --git a/drivers/acpi/container.c b/drivers/acpi/container.c
> index 45cd03b..1f9f7d7 100644
> --- a/drivers/acpi/container.c
> +++ b/drivers/acpi/container.c
> @@ -158,9 +158,7 @@ static void container_notify_cb(acpi_handle handle, u32 type, void *context)
>   	int result;
>   	int present;
>   	acpi_status status;
> -
> -
> -	present = is_device_present(handle);
> +	u32 ost_code = ACPI_OST_SC_NON_SPECIFIC_FAILURE; /* default */
> 
>   	switch (type) {
>   	case ACPI_NOTIFY_BUS_CHECK:
> @@ -169,32 +167,47 @@ static void container_notify_cb(acpi_handle handle, u32 type, void *context)
>   		printk(KERN_WARNING "Container driver received %s event\n",
>   		       (type == ACPI_NOTIFY_BUS_CHECK) ?
>   		       "ACPI_NOTIFY_BUS_CHECK" : "ACPI_NOTIFY_DEVICE_CHECK");
> +
> +		present = is_device_present(handle);
>   		status = acpi_bus_get_device(handle,&device);
> -		if (present) {
> -			if (ACPI_FAILURE(status) || !device) {
> -				result = container_device_add(&device, handle);
> -				if (!result)
> -					kobject_uevent(&device->dev.kobj,
> -						       KOBJ_ONLINE);
> -				else
> -					printk(KERN_WARNING
> -					       "Failed to add container\n");
> -			}
> -		} else {
> +		if (!present) {
>   			if (ACPI_SUCCESS(status)) {
>   				/* device exist and this is a remove request */
> +				device->flags.eject_pending = 1;
>   				kobject_uevent(&device->dev.kobj, KOBJ_OFFLINE);
> +				return;
>   			}
> +			break;
> +		}
> +

> +		if (!ACPI_FAILURE(status) || device)
> +			break;

The logic is not same as previous logic.
I think the following logic is correct.

		if (!ACPI_FAILURE(status) && device)
			break;
Thanks,
Yasuaki Ishimatsu

> +
> +		result = container_device_add(&device, handle);
> +		if (result) {
> +			printk(KERN_WARNING "Failed to add container\n");
> +			break;
>   		}
> +
> +		kobject_uevent(&device->dev.kobj, KOBJ_ONLINE);
> +		ost_code = ACPI_OST_SC_SUCCESS;
>   		break;
> +
>   	case ACPI_NOTIFY_EJECT_REQUEST:
>   		if (!acpi_bus_get_device(handle,&device)&&  device) {
> +			device->flags.eject_pending = 1;
>   			kobject_uevent(&device->dev.kobj, KOBJ_OFFLINE);
> +			return;
>   		}
>   		break;
> +
>   	default:
> -		break;
> +		/* non-hotplug event; possibly handled by other handler */
> +		return;
>   	}
> +
> +	/* Inform firmware that the hotplug operation has completed */
> +	(void) acpi_evaluate_hotplug_ost(handle, type, ost_code, NULL);
>   	return;
>   }
> 



  reply	other threads:[~2012-06-05  4:40 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 [this message]
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
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=4FCD8D95.1060700@jp.fujitsu.com \
    --to=isimatu.yasuaki@jp.fujitsu.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=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