[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPnjgZ1ExEQHL8W2+k=+wS98O3CCX25dKngv_PFNvgAKVBD4Hw@mail.gmail.com>
Date: Wed, 25 Apr 2018 15:17:37 -0600
From: Simon Glass <sjg@...omium.org>
To: Vinod Koul <vinod.koul@...el.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
C Shapiro <shapiroc@...omium.org>,
Aaron Durbin <adurbin@...omium.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Jonathan Corbet <corbet@....net>,
Philippe Ombredanne <pombredanne@...b.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Alex Hung <alex.hung@...onical.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jean Delvare <jdelvare@...e.com>,
sayli karnik <karniksayli1995@...il.com>,
Sagar Dharia <sdharia@...eaurora.org>
Subject: Re: [PATCH] firmware: dmi: Add access to the SKU ID string
Hi Vinod,
On 24 April 2018 at 20:51, Vinod Koul <vinod.koul@...el.com> wrote:
> On Tue, Apr 24, 2018 at 03:11:11PM -0600, Simon Glass wrote:
>> This is used in some systems from user space for determining the identity
>> of the device.
>>
>> Expose this as a file so that that user-space tools don't need to read
>> from /sys/firmware/dmi/tables/DMI
>
> sysfs is an ABI and needs to be documented, I don't see that in this patch,
> pls add.
Thanks for taking a look. The only mention of the dmi/id I can find is
in Kconfig:
config DMIID
bool "Export DMI identification via sysfs to userspace"
depends on DMI
default y
help
Say Y here if you want to query SMBIOS/DMI system identification
information from userspace through /sys/class/dmi/id/ or if you want
DMI-based module auto-loading.
Are you suggesting that I create a list of the things in the /id node,
or something else?
Regards,
Simon
Powered by blists - more mailing lists