From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: linux-acpi@vger.kernel.org, lenb@kernel.org
Subject: Re: [PATCH 1/3] Add a generic API for _OSC
Date: Tue, 27 Oct 2009 09:07:18 -0600 [thread overview]
Message-ID: <200910270907.19103.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20091027063637.GA22237@sli10-desk.sh.intel.com>
On Tuesday 27 October 2009 12:36:37 am Shaohua Li wrote:
> Add an API to execute _OSC. A lot of devices can have this method, so add a
> generic API.
> + out_obj = context->ret.pointer;
> + if (out_obj->type != ACPI_TYPE_BUFFER) {
> + printk(KERN_DEBUG "_OSC evaluation returned wrong type\n");
> + status = AE_TYPE;
> + goto out_kfree;
> + }
> + /* Need to ignore the bit0 in result code */
> + errors = *((u32 *)out_obj->buffer.pointer) & ~(1 << 0);
> + if (errors) {
> + if (errors & OSC_REQUEST_ERROR)
> + printk(KERN_DEBUG "_OSC request failed\n");
> + if (errors & OSC_INVALID_UUID_ERROR)
> + printk(KERN_DEBUG "_OSC invalid UUID\n");
> + if (errors & OSC_INVALID_REVISION_ERROR)
> + printk(KERN_DEBUG "_OSC invalid revision\n");
> + if (errors & OSC_CAPABILITIES_MASK_ERROR) {
> + if (((u32 *)context->cap.pointer)[OSC_QUERY_TYPE]
> + & OSC_QUERY_ENABLE)
> + goto out_success;
> + printk(KERN_DEBUG
> + "Firmware did not grant requested _OSC control\n");
On all these printks, it would be very useful to have some indication
of what the OS requested and which specific _OSC method we executed,
e.g., an ACPI device name or a namespace path.
Bjorn
next prev parent reply other threads:[~2009-10-27 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 6:36 [PATCH 1/3] Add a generic API for _OSC Shaohua Li
2009-10-27 7:59 ` Kenji Kaneshige
2009-10-27 15:07 ` Bjorn Helgaas [this message]
2009-10-28 3:02 ` Kenji Kaneshige
2009-10-27 15:52 ` Alexey Starikovskiy
2009-10-28 2:19 ` Shaohua Li
2009-10-28 8:02 ` Alexey Starikovskiy
2009-10-28 8:47 ` Shaohua Li
2009-10-28 10:54 ` Alexey Starikovskiy
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=200910270907.19103.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=shaohua.li@intel.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