From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mario.Limonciello@dell.com
Cc: enric.balletbo@collabora.com, rjw@rjwysocki.net,
rafael@kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, lenb@kernel.org,
kernel@collabora.com, groeck@chromium.org, bleung@chromium.org,
dtor@chromium.org, gwendal@chromium.org, vbendeb@chromium.org,
andy@infradead.org, ayman.bagabas@gmail.com,
benjamin.tissoires@redhat.com, blaz@mxxn.io,
dvhart@infradead.org, gregkh@linuxfoundation.org,
hdegoede@redhat.com, jeremy@system76.com, 2pi@mok.nu,
mchehab+samsung@kernel.org, rajatja@google.com,
srinivas.pandruvada@linux.intel.com,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v4] platform: x86: Add ACPI driver for ChromeOS
Date: Wed, 10 Jun 2020 14:40:33 -0700 [thread overview]
Message-ID: <20200610214033.GB248110@dtor-ws> (raw)
In-Reply-To: <59771d3689da41a5bbc67541aa6f4777@AUSX13MPC105.AMER.DELL.COM>
On Wed, Jun 10, 2020 at 09:28:36PM +0000, Mario.Limonciello@dell.com wrote:
> >
> > To give you some references, if I'm not wrong, this prefix is used in all
> > or
> > almost all Intel Chromebook devices (auron, cyan, eve, fizz, hatch,
> > octopus,
> > poppy, strago ...) The ACPI source for this device can be found here [1],
> > and,
> > if not all, almost all Intel based Chromebooks are shipped with the
> > firmware
> > that supports this.
>
> You can potentially carry a small patch in your downstream kernel for the
> legacy stuff until it reaches EOL. At least for the new stuff you could
> enact a process that properly reserves unique numbers and changes the driver
> when the interface provided by the ACPI device has changed.
If we use this prefix for hatch EOL is ~7 years from now.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2020-06-10 21:40 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
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 [this message]
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=20200610214033.GB248110@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=2pi@mok.nu \
--cc=Mario.Limonciello@dell.com \
--cc=andy@infradead.org \
--cc=ayman.bagabas@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=blaz@mxxn.io \
--cc=bleung@chromium.org \
--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=rafael@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).