From: Feng Tang <feng.tang@intel.com>
To: Lan Tianyu <tianyu.lan@intel.com>
Cc: len.brown@intel.com, linux-acpi@vger.kernel.org, mjg@redhat.com,
gregkh@linuxfoundation.org, Bob Moore <robert.moore@intel.com>
Subject: Re: [PATCH 1/2] ACPI: Use ACPICA native way to decode the PLD buffer
Date: Wed, 22 Aug 2012 15:16:18 +0800 [thread overview]
Message-ID: <20120822151618.1625d9c7@feng-i7> (raw)
In-Reply-To: <503484C2.8070106@intel.com>
Hi Tianyu,
On Wed, 22 Aug 2012 15:05:38 +0800
Lan Tianyu <tianyu.lan@intel.com> wrote:
> On 2012年08月22日 14:24, Feng Tang wrote:
> > This patch is on top of the ACPICA 20120816 release, which implemented
> > a native way to decode PLD buffer, so use it instead of leting upper
> > level users do the decoding.
> >
> > Signed-off-by: Feng Tang <feng.tang@intel.com>
> > Signed-off-by: Bob Moore <robert.moore@intel.com>
> > ---
> > drivers/acpi/utils.c | 11 +++++++----
> > include/acpi/acpi_bus.h | 31 +------------------------------
> > 2 files changed, 8 insertions(+), 34 deletions(-)
> >
> > diff --git a/drivers/acpi/utils.c b/drivers/acpi/utils.c
> > index 3e87c9c..e697bf2 100644
> > --- a/drivers/acpi/utils.c
> > +++ b/drivers/acpi/utils.c
> > @@ -384,7 +384,7 @@ acpi_evaluate_reference(acpi_handle handle,
> > EXPORT_SYMBOL(acpi_evaluate_reference);
> >
> > acpi_status
> > -acpi_get_physical_device_location(acpi_handle handle, struct acpi_pld *pld)
> > +acpi_get_physical_device_location(acpi_handle handle, struct acpi_pld_info **pld)
> Sorry. I have not found the definition of struct acpi_pld_info or is
> there something I have missed?
The definition is in the ACPICA 20120816 patch sets I just posted to linux-acpi list.
Let me copy it here
+
+/*
+ * Note: C bitfields are not used for this reason:
+ *
+ * "Bitfields are great and easy to read, but unfortunately the C language
+ * does not specify the layout of bitfields in memory, which means they are
+ * essentially useless for dealing with packed data in on-disk formats or
+ * binary wire protocols." (Or ACPI tables and buffers.) "If you ask me,
+ * this decision was a design error in C. Ritchie could have picked an order
+ * and stuck with it." Norman Ramsey.
+ * See http://stackoverflow.com/a/1053662/41661
+ */
+
+/*
+ * Formatted _PLD return value. The minimum size is a package containing
+ * one buffer.
+ * Revision 1: Buffer is 16 bytes (128 bits)
+ * Revision 2: Buffer is 20 bytes (160 bits)
+ *
+ * Note: This structure is returned from the acpi_decode_pld_buffer
+ * interface.
+ */
+struct acpi_pld_info {
+ u8 revision;
+ u8 ignore_color;
+ u32 color;
+ u16 width;
+ u16 height;
+ u8 user_visible;
+ u8 dock;
+ u8 lid;
+ u8 panel;
+ u8 vertical_position;
+ u8 horizontal_position;
+ u8 shape;
+ u8 group_orientation;
+ u8 group_token;
+ u8 group_position;
+ u8 bay;
+ u8 ejectable;
+ u8 ospm_eject_required;
+ u8 cabinet_number;
+ u8 card_cage_number;
+ u8 reference;
+ u8 rotation;
+ u8 order;
+ u8 reserved;
+ u16 vertical_offset;
+ u16 horizontal_offset;
+};
+
+/*
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-08-22 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 6:24 [PATCH 1/2] ACPI: Use ACPICA native way to decode the PLD buffer Feng Tang
2012-08-22 6:24 ` [PATCH 2/2] usb-acpi: Comply with the ACPI API change Feng Tang
2012-08-22 7:05 ` [PATCH 1/2] ACPI: Use ACPICA native way to decode the PLD buffer Lan Tianyu
2012-08-22 7:16 ` Feng Tang [this message]
2012-08-22 8:35 ` [PATCH V2 " Feng Tang
2012-09-21 4:32 ` Len Brown
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=20120822151618.1625d9c7@feng-i7 \
--to=feng.tang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=robert.moore@intel.com \
--cc=tianyu.lan@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;
as well as URLs for NNTP newsgroup(s).