lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 30 Mar 2020 10:29:02 -0700 From: Randy Dunlap <rdunlap@...radead.org> To: Enric Balletbo i Serra <enric.balletbo@...labora.com>, linux-kernel@...r.kernel.org Cc: groeck@...omium.org, bleung@...omium.org, dtor@...omium.org, gwendal@...omium.org, Collabora Kernel ML <kernel@...labora.com>, vbendeb@...omium.org, andy@...radead.org, Ayman Bagabas <ayman.bagabas@...il.com>, Darren Hart <dvhart@...radead.org>, Dmitry Torokhov <dmitry.torokhov@...il.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Jeremy Soller <jeremy@...tem76.com>, Jonathan Corbet <corbet@....net>, Krzysztof Kozlowski <krzk@...nel.org>, Mattias Jacobsson <2pi@....nu>, Mauro Carvalho Chehab <mchehab+samsung@...nel.org>, Rajat Jain <rajatja@...gle.com>, Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>, Yauhen Kharuzhy <jekhor@...il.com>, platform-driver-x86@...r.kernel.org Subject: Re: [PATCH v3] platform: x86: Add ACPI driver for ChromeOS Hi-- On 3/30/20 8:06 AM, Enric Balletbo i Serra 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. 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. > > Signed-off-by: Enric Balletbo i Serra <enric.balletbo@...labora.com> > --- > > Thanks, > Enric > > [1] https://lkml.org/lkml/2017/7/31/378 > > Changes in v3: > - Use attribute groups instead of adding files "by hand". > - Add BUILD_TEST to increment build coverage. Where was BUILD_TEST coverage added? Is that the same as COMPILE_TEST? > - Do not use "raw" kobject to create directories. > - Do not abuse of the platform_device interface. Remove it. > > Changes in v2: > - Note that this version is a total rework, with those major changes: > - Use lists to track dinamically allocated attributes and groups. > - Use sysfs binary attributes to store the ACPI contents. > - Remove all the functionalities except the one that creates the sysfs files. > > drivers/platform/x86/Kconfig | 12 + > drivers/platform/x86/Makefile | 1 + > drivers/platform/x86/chromeos_acpi.c | 517 +++++++++++++++++++++++++++ > 3 files changed, 530 insertions(+) > create mode 100644 drivers/platform/x86/chromeos_acpi.c > > diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig > index 587403c44598..917a1c1a0758 100644 > --- a/drivers/platform/x86/Kconfig > +++ b/drivers/platform/x86/Kconfig > @@ -72,6 +72,18 @@ config ACERHDF > If you have an Acer Aspire One netbook, say Y or M > here. > > +config ACPI_CHROMEOS > + tristate "ChromeOS specific ACPI extensions" > + depends on ACPI > + depends on CHROME_PLATFORMS > + help > + This driver provides the firmware interface for the services > + exported through the ChromeOS interfaces when using ChromeOS > + ACPI firmware. > + > + If you have an ACPI-compatible Chromebook, say Y or M > + here. > + > config ALIENWARE_WMI > tristate "Alienware Special feature control" > depends on ACPI thanks. -- ~Randy
Powered by blists - more mailing lists