From: Alex Hung <alex.hung@canonical.com>
To: rjw@rjwysocki.net, lenb@kernel.org, jdelvare@suse.com,
gregkh@linuxfoundation.org, davem@davemloft.net,
mika.westerberg@linux.intel.com,
andriy.shevchenko@linux.intel.com, f.fainelli@gmail.com,
dmitry.torokhov@gmail.com, kishon@ti.com,
karniksayli1995@gmail.com, linux-acpi@vger.kernel.org,
alex.hung@canonical.com, Mario.Limonciello@dell.com
Subject: [PATCH 1/2] firmware: dmi_scan: add DMI_OEM_STRING support to dmi_matches
Date: Wed, 31 Jan 2018 00:40:04 -0800 [thread overview]
Message-ID: <1517388005-14852-1-git-send-email-alex.hung@canonical.com> (raw)
OEM strings are defined by each OEM and they contain customized and
useful OEM information. Supporting it provides more flexible uses of
the dmi_matches function.
Signed-off-by: Alex Hung <alex.hung@canonical.com>
---
drivers/firmware/dmi_scan.c | 8 ++++++++
include/linux/mod_devicetable.h | 1 +
2 files changed, 9 insertions(+)
diff --git a/drivers/firmware/dmi_scan.c b/drivers/firmware/dmi_scan.c
index 7830419..e534d1b 100644
--- a/drivers/firmware/dmi_scan.c
+++ b/drivers/firmware/dmi_scan.c
@@ -797,11 +797,19 @@ static bool dmi_matches(const struct dmi_system_id *dmi)
else if (dmi->matches[i].exact_match &&
!strcmp(dmi_ident[s], dmi->matches[i].substr))
continue;
+ } else if (s == DMI_OEM_STRING) {
+ const struct dmi_device *valid;
+
+ valid = dmi_find_device(DMI_DEV_TYPE_OEM_STRING,
+ dmi->matches[i].substr, NULL);
+ if (valid)
+ continue;
}
/* No match */
return false;
}
+
return true;
}
diff --git a/include/linux/mod_devicetable.h b/include/linux/mod_devicetable.h
index abb6dc2..5739c4c 100644
--- a/include/linux/mod_devicetable.h
+++ b/include/linux/mod_devicetable.h
@@ -482,6 +482,7 @@ enum dmi_field {
DMI_CHASSIS_VERSION,
DMI_CHASSIS_SERIAL,
DMI_CHASSIS_ASSET_TAG,
+ DMI_OEM_STRING,
DMI_STRING_MAX,
};
--
2.7.4
next reply other threads:[~2018-01-31 8:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 8:40 Alex Hung [this message]
2018-01-31 8:40 ` [PATCH 2/2] ACPI / osi: add DMI quirk for Dell systems Alex Hung
2018-02-05 13:14 ` Jean Delvare
2018-02-05 14:15 ` Andy Shevchenko
2018-02-05 17:36 ` Mario.Limonciello
2018-02-05 22:45 ` Dmitry Torokhov
2018-02-06 0:45 ` Mario.Limonciello
2018-02-06 13:45 ` Andy Shevchenko
2018-02-06 16:24 ` Mario.Limonciello
2018-02-07 20:38 ` Alex Hung
2018-02-07 20:49 ` Mario.Limonciello
2018-02-11 9:29 ` Rafael J. Wysocki
2018-02-11 13:45 ` Lukas Wunner
2018-02-12 9:49 ` Rafael J. Wysocki
2018-02-12 20:29 ` Mario.Limonciello
2018-02-12 22:57 ` Rafael J. Wysocki
2018-02-12 23:14 ` Mario.Limonciello
2018-02-13 5:25 ` Alex Hung
2018-02-13 7:32 ` Mika Westerberg
2018-02-14 9:06 ` Rafael J. Wysocki
2018-02-14 9:50 ` Mika Westerberg
2018-02-13 9:18 ` Rafael J. Wysocki
2018-02-13 9:55 ` Lukas Wunner
2018-02-14 9:10 ` Rafael J. Wysocki
2018-02-14 18:47 ` Mario.Limonciello
2018-02-15 9:44 ` Rafael J. Wysocki
2018-02-05 17:24 ` Mario.Limonciello
2018-02-05 21:55 ` Jean Delvare
2018-02-07 20:05 ` Alex Hung
2018-02-05 10:26 ` [PATCH 1/2] firmware: dmi_scan: add DMI_OEM_STRING support to dmi_matches Jean Delvare
2018-02-07 5:25 ` Alex Hung
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=1517388005-14852-1-git-send-email-alex.hung@canonical.com \
--to=alex.hung@canonical.com \
--cc=Mario.Limonciello@dell.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dmitry.torokhov@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.com \
--cc=karniksayli1995@gmail.com \
--cc=kishon@ti.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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).