From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"ACPI Devel Maling List" <linux-acpi@vger.kernel.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
"Len Brown" <lenb@kernel.org>,
"Collabora Kernel ML" <kernel@collabora.com>,
"Guenter Roeck" <groeck@chromium.org>,
"Benson Leung" <bleung@chromium.org>,
"Dmitry Torokhov" <dtor@chromium.org>,
"Gwendal Grignou" <gwendal@chromium.org>,
vbendeb@chromium.org, "Andy Shevchenko" <andy@infradead.org>,
"Ayman Bagabas" <ayman.bagabas@gmail.com>,
"Benjamin Tissoires" <benjamin.tissoires@redhat.com>,
"Blaž Hrastnik" <blaz@mxxn.io>,
"Darren Hart" <dvhart@infradead.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Hans de Goede" <hdegoede@redhat.com>,
"Jeremy Soller" <jeremy@system76.com>,
"Mattias Jacobsson" <2pi@mok.nu>,
"Mauro Carvalho Chehab" <mchehab+samsung@kernel.org>,
"Rajat Jain" <rajatja@google.com>,
"Srinivas Pandruvada" <srinivas.pandruvada@linux.intel.com>,
"Platform Driver" <platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH v4] platform: x86: Add ACPI driver for ChromeOS
Date: Mon, 13 Apr 2020 22:41:51 +0200 [thread overview]
Message-ID: <CAJZ5v0gWZ27_DwWQadsJOUxLo4a0rAMe45d4AWXS2gHJZfgfKg@mail.gmail.com> (raw)
In-Reply-To: <20200413134611.478441-1-enric.balletbo@collabora.com>
On Mon, Apr 13, 2020 at 3:46 PM Enric Balletbo i Serra
<enric.balletbo@collabora.com> wrote:
>
> This driver attaches to the ChromeOS ACPI device and then exports the values
> reported by the ACPI in a sysfs directory. These values are not exported
> via the standard ACPI tables, hence a specific driver is needed to do
> it.
So how exactly are they exported?
> The ACPI values are presented in the string form (numbers as decimal
> values) or binary blobs, and can be accessed as the contents of the
> appropriate read only files in the standard ACPI devices sysfs directory tree.
My understanding based on a cursory look at the patch is that there is
an ACPI device with _HID equal to "GGL0001" and one or more special
methods under it that return values which you want to export over
sysfs as binary attributes. They appear to be read-only.
I guess that these data are to be consubed by user space?
next prev parent reply other threads:[~2020-04-13 20:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 13:46 [PATCH v4] platform: x86: Add ACPI driver for ChromeOS Enric Balletbo i Serra
2020-04-13 14:12 ` Greg Kroah-Hartman
2020-04-24 14:43 ` Enric Balletbo i Serra
2020-06-05 11:03 ` Rafael J. Wysocki
2020-04-13 20:41 ` Rafael J. Wysocki [this message]
2020-04-14 14:35 ` Enric Balletbo i Serra
2020-06-05 11:17 ` Rafael J. Wysocki
2020-06-06 18:04 ` Dmitry Torokhov
2020-06-23 14:46 ` Enric Balletbo i Serra
2020-06-10 21:21 ` Enric Balletbo i Serra
2020-06-10 21:28 ` Mario.Limonciello
2020-06-10 21:40 ` Dmitry Torokhov
2020-06-10 21:52 ` Mario.Limonciello
2020-06-10 22:43 ` Dmitry Torokhov
2020-06-11 11:06 ` Enric Balletbo i Serra
2020-07-09 9:31 ` Enric Balletbo i Serra
2020-07-09 11:57 ` Rafael J. Wysocki
2020-07-09 12:01 ` Rafael J. Wysocki
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=CAJZ5v0gWZ27_DwWQadsJOUxLo4a0rAMe45d4AWXS2gHJZfgfKg@mail.gmail.com \
--to=rafael@kernel.org \
--cc=2pi@mok.nu \
--cc=andy@infradead.org \
--cc=ayman.bagabas@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=blaz@mxxn.io \
--cc=bleung@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@chromium.org \
--cc=dvhart@infradead.org \
--cc=enric.balletbo@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=hdegoede@redhat.com \
--cc=jeremy@system76.com \
--cc=kernel@collabora.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rajatja@google.com \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=vbendeb@chromium.org \
/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).