From: Daniel Gutson <daniel.gutson@eclypsium.com>
To: Daniel Gutson <daniel.gutson@eclypsium.com>,
Derek Kiernan <derek.kiernan@xilinx.com>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org,
Richard Hughes <hughsient@gmail.com>,
Alex Bazhaniuk <alex@eclypsium.com>,
linux-mtd@lists.infradead.org
Subject: [PATCH 0/2] Platform integrity information in sysfs (version 9)
Date: Wed, 30 Sep 2020 10:51:01 -0300 [thread overview]
Message-ID: <20200930135101.5424-1-daniel.gutson@eclypsium.com> (raw)
This patch serie adds a misc kernel module and extends the intel-spi drivers
to publish platform integrity data in the sys-fs.
Please check the comments in the following patches of this serie for further
details.
Daniel Gutson (2):
Platform integrity information in sysfs (version 9)
This patch exports the BIOS Write Enable (bioswe), BIOS Lock Enable
(biosle), and the SMM BIOS Write Protect (SMM_BIOSWP) fields of the
BIOS Control register using the platform-integrity misc kernel
module. The idea is to keep adding more flags, not only from the BC
but also from other registers in following versions.
.../ABI/stable/sysfs-class-platform-integrity | 23 +++++
MAINTAINERS | 7 ++
drivers/misc/Kconfig | 11 +++
drivers/misc/Makefile | 1 +
drivers/misc/platform-integrity.c | 57 ++++++++++++
drivers/mtd/spi-nor/controllers/Kconfig | 1 +
.../mtd/spi-nor/controllers/intel-spi-pci.c | 75 +++++++++++++++-
.../spi-nor/controllers/intel-spi-platform.c | 2 +-
drivers/mtd/spi-nor/controllers/intel-spi.c | 90 ++++++++++++++++++-
drivers/mtd/spi-nor/controllers/intel-spi.h | 9 +-
include/linux/platform-integrity.h | 19 ++++
11 files changed, 288 insertions(+), 7 deletions(-)
create mode 100644 Documentation/ABI/stable/sysfs-class-platform-integrity
create mode 100644 drivers/misc/platform-integrity.c
create mode 100644 include/linux/platform-integrity.h
--
2.25.1
WARNING: multiple messages have this Message-ID
From: Daniel Gutson <daniel.gutson@eclypsium.com>
To: Daniel Gutson <daniel.gutson@eclypsium.com>,
Derek Kiernan <derek.kiernan@xilinx.com>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org,
Richard Hughes <hughsient@gmail.com>,
Alex Bazhaniuk <alex@eclypsium.com>,
linux-mtd@lists.infradead.org
Subject: [PATCH 0/2] Platform integrity information in sysfs (version 9)
Date: Wed, 30 Sep 2020 10:51:01 -0300 [thread overview]
Message-ID: <20200930135101.5424-1-daniel.gutson@eclypsium.com> (raw)
This patch serie adds a misc kernel module and extends the intel-spi drivers
to publish platform integrity data in the sys-fs.
Please check the comments in the following patches of this serie for further
details.
Daniel Gutson (2):
Platform integrity information in sysfs (version 9)
This patch exports the BIOS Write Enable (bioswe), BIOS Lock Enable
(biosle), and the SMM BIOS Write Protect (SMM_BIOSWP) fields of the
BIOS Control register using the platform-integrity misc kernel
module. The idea is to keep adding more flags, not only from the BC
but also from other registers in following versions.
.../ABI/stable/sysfs-class-platform-integrity | 23 +++++
MAINTAINERS | 7 ++
drivers/misc/Kconfig | 11 +++
drivers/misc/Makefile | 1 +
drivers/misc/platform-integrity.c | 57 ++++++++++++
drivers/mtd/spi-nor/controllers/Kconfig | 1 +
.../mtd/spi-nor/controllers/intel-spi-pci.c | 75 +++++++++++++++-
.../spi-nor/controllers/intel-spi-platform.c | 2 +-
drivers/mtd/spi-nor/controllers/intel-spi.c | 90 ++++++++++++++++++-
drivers/mtd/spi-nor/controllers/intel-spi.h | 9 +-
include/linux/platform-integrity.h | 19 ++++
11 files changed, 288 insertions(+), 7 deletions(-)
create mode 100644 Documentation/ABI/stable/sysfs-class-platform-integrity
create mode 100644 drivers/misc/platform-integrity.c
create mode 100644 include/linux/platform-integrity.h
--
2.25.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2020-09-30 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 13:51 Daniel Gutson [this message]
2020-09-30 13:51 ` [PATCH 0/2] Platform integrity information in sysfs (version 9) Daniel Gutson
2020-09-30 14:19 ` Greg Kroah-Hartman
2020-09-30 14:19 ` Greg Kroah-Hartman
2020-09-30 16:37 Daniel Gutson
2020-09-30 16:37 ` Daniel Gutson
2020-09-30 16:42 ` Daniel Gutson
2020-09-30 16:42 ` Daniel Gutson
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=20200930135101.5424-1-daniel.gutson@eclypsium.com \
--to=daniel.gutson@eclypsium.com \
--cc=alex@eclypsium.com \
--cc=arnd@arndb.de \
--cc=derek.kiernan@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=hughsient@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mchehab+huawei@kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--cc=vigneshr@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.