LKML Archive on
help / color / mirror / Atom feed
From: Simon Glass <>
To: Vinod Koul <>
Cc: LKML <>,
	C Shapiro <>,
	Aaron Durbin <>,
	Mika Westerberg <>,
	Jonathan Corbet <>,
	Philippe Ombredanne <>,
	Andy Shevchenko <>,
	Alex Hung <>,
	Dmitry Torokhov <>,
	Greg Kroah-Hartman <>,
	Jean Delvare <>,
	sayli karnik <>,
	Sagar Dharia <>
Subject: Re: [PATCH] firmware: dmi: Add access to the SKU ID string
Date: Wed, 25 Apr 2018 15:17:37 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20180425025125.GH6014@localhost>

Hi Vinod,

On 24 April 2018 at 20:51, Vinod Koul <> 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
  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?


  reply	other threads:[~2018-04-25 21:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 21:11 Simon Glass
2018-04-25  2:51 ` Vinod Koul
2018-04-25 21:17   ` Simon Glass [this message]
2018-04-26  9:33     ` Vinod Koul
2018-04-26 11:01       ` Jean Delvare
2018-04-27  7:58 ` Jean Delvare
2018-04-27 19:12   ` Simon Glass

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] firmware: dmi: Add access to the SKU ID string' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).