All of lore.kernel.org
 help / color / mirror / Atom feed
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 4/6] ACPI: Add _OST support for ACPI memory hotplug
Date: Thu, 24 May 2012 12:21:50 -0600	[thread overview]
Message-ID: <1337883710.2718.85.camel@lorien2> (raw)
In-Reply-To: <1337826324-16802-5-git-send-email-toshi.kani@hp.com>

On Wed, 2012-05-23 at 20:25 -0600, Toshi Kani wrote:
> Changed acpi_memory_device_notify() to call ACPI _OST method
> when ACPI memory hotplug operation has completed.
> 
> Signed-off-by: Toshi Kani <toshi.kani@hp.com>
> ---
>  drivers/acpi/acpi_memhotplug.c |   43 +++++++++++++++++++++++++++++----------
>  1 files changed, 32 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
> index d985713..24c807f 100644
> --- a/drivers/acpi/acpi_memhotplug.c
> +++ b/drivers/acpi/acpi_memhotplug.c
> @@ -341,7 +341,7 @@ static void acpi_memory_device_notify(acpi_handle handle, u32 event, void *data)
>  {
>  	struct acpi_memory_device *mem_device;
>  	struct acpi_device *device;
> -
> +	u32 ost_code = ACPI_OST_SC_NON_SPECIFIC_FAILURE; /* default */
>  
>  	switch (event) {
>  	case ACPI_NOTIFY_BUS_CHECK:
> @@ -354,15 +354,20 @@ static void acpi_memory_device_notify(acpi_handle handle, u32 event, void *data)
>  					  "\nReceived DEVICE CHECK notification for device\n"));
>  		if (acpi_memory_get_device(handle, &mem_device)) {
>  			printk(KERN_ERR PREFIX "Cannot find driver data\n");
> -			return;
> +			break;
>  		}
>  
> -		if (!acpi_memory_check_device(mem_device)) {
> -			if (acpi_memory_enable_device(mem_device))
> -				printk(KERN_ERR PREFIX
> -					    "Cannot enable memory device\n");
> +		if (acpi_memory_check_device(mem_device))
> +			break;
> +
> +		if (acpi_memory_enable_device(mem_device)) {
> +			printk(KERN_ERR PREFIX "Cannot enable memory device\n");
> +			break;
>  		}
> +
> +		ost_code = ACPI_OST_SC_SUCCESS;
>  		break;
> +
>  	case ACPI_NOTIFY_EJECT_REQUEST:
>  		ACPI_DEBUG_PRINT((ACPI_DB_INFO,
>  				  "\nReceived EJECT REQUEST notification for device\n"));
> @@ -383,19 +388,35 @@ static void acpi_memory_device_notify(acpi_handle handle, u32 event, void *data)
>  		 * TBD: Can also be disabled by Callback registration
>  		 *      with generic sysfs driver
>  		 */
> -		if (acpi_memory_disable_device(mem_device))
> -			printk(KERN_ERR PREFIX
> -				    "Disable memory device\n");
> +		if (acpi_memory_disable_device(mem_device)) {
> +			printk(KERN_ERR PREFIX "Disable memory device\n");
> +			/*
> +			 * If _EJ0 was called but failed, _OST is not
> +			 * necessary.
> +			 */
> +			if (mem_device->state == MEMORY_INVALID_STATE)
> +				return;
> +
> +			break;
> +		}

Why isn't _OST called in this case to report failure? Isn't this one of
the cases Spec talks about. Reference: 6.3.5 _OST (OSPM Status
Indication) page 302.

-- Shuah

> +
>  		/*
>  		 * TBD: Invoke acpi_bus_remove to cleanup data structures
>  		 */
> -		break;
> +
> +		/* _EJ0 succeeded; _OST is not necessary */
> +		return;
> +
>  	default:
>  		ACPI_DEBUG_PRINT((ACPI_DB_INFO,
>  				  "Unsupported event [0x%x]\n", event));
> -		break;
> +
> +		/* non-hotplug event; possibly handled by other handler */
> +		return;
>  	}
>  
> +	/* Inform firmware that the hotplug operation has completed */
> +	(void) acpi_evaluate_hotplug_ost(handle, event, ost_code, NULL);
>  	return;
>  }
>  



  reply	other threads:[~2012-05-24 18:21 UTC|newest]

Thread overview: 27+ 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 [this message]
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
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: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=1337883710.2718.85.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.