From: Thierry Escande <thierry.escande@collabora.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Google VPD sysfs driver
Date: Tue, 11 Apr 2017 11:14:29 +0200 [thread overview]
Message-ID: <1491902071-17935-1-git-send-email-thierry.escande@collabora.com> (raw)
Hi,
This patchset adds support for accessing Google Vital Product Data (VPD)
through the sysfs interface under /sys/firmware/vpd.
This patchset contains the VPD decoding routines read from coreboot
table entries and the driver responsible for creating the sysfs
interface.
This patchset depends on [1] for coreboot support in the Google memory
console.
Regards,
Thierry
[1] https://lkml.org/lkml/2017/3/28/902
Wei-Ning Huang (2):
firmware: Google Vital Product Data: import lib_vpd source files
firmware: Google VPD sysfs driver
drivers/firmware/google/Kconfig | 7 +
drivers/firmware/google/Makefile | 3 +
drivers/firmware/google/vpd.c | 333 +++++++++++++++++++++++++++++++++++
drivers/firmware/google/vpd_decode.c | 102 +++++++++++
drivers/firmware/google/vpd_decode.h | 59 +++++++
5 files changed, 504 insertions(+)
create mode 100644 drivers/firmware/google/vpd.c
create mode 100644 drivers/firmware/google/vpd_decode.c
create mode 100644 drivers/firmware/google/vpd_decode.h
--
2.7.4
next reply other threads:[~2017-04-11 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 9:14 Thierry Escande [this message]
2017-04-11 9:14 ` [PATCH 1/2] firmware: Google VPD: import lib_vpd source files Thierry Escande
2017-04-11 14:09 ` Greg Kroah-Hartman
2017-04-11 14:28 ` Thierry Escande
2017-04-11 18:15 ` Joe Perches
2017-04-11 18:42 ` Greg Kroah-Hartman
2017-04-11 18:50 ` Joe Perches
2017-04-11 14:10 ` Greg Kroah-Hartman
2017-04-11 14:11 ` Greg Kroah-Hartman
2017-04-11 14:31 ` Thierry Escande
2017-04-11 9:14 ` [PATCH 2/2] firmware: Google VPD sysfs driver Thierry Escande
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=1491902071-17935-1-git-send-email-thierry.escande@collabora.com \
--to=thierry.escande@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®