spi: intel: Add protected and locked attributes
PATCH v2 1/1 spi: intel: Add protected and locked attributes
From: Alexander Usyskin <[email protected]>
The manufacturing access to the PCH/SoC SPI device is traditionally performed via userspace driver accessing registers via /dev/mem but due to security concerns /dev/mem access is being much restricted, hence the reason for utilizing dedicated Intel PCH/SoC SPI controller driver, which is already implemented in the Linux kernel.
Intel PCH/SoC SPI controller protects the flash storage via two mechanisms one is the via region protection registers and second via BIOS lock. The BIOS locks only the BIOS regions usually 0 and/or 6.
The device always boots with BIOS lock set, but during manufacturing the BIOS lock has to be lifted in order to enable the write access. This can be done by passing "writeable=1" in the command line when the driver is loaded. This "locked" state is exposed through new sysfs attributes (intel_spi_locked, intel_spi_bios_locked).
Second, also the region protection status is exposed via sysfs attribute (intel_spi_protected) as the manufacturing will need the both files in order to validate that the device is properly sealed.
Includes code written by Tamar Mashiah.
---
Changes from v1:
* Use correct email address for Tomas.
.../ABI/testing/sysfs-driver-spi-intel | 20 ++++++ drivers/spi/spi-intel-pci.c | 1 + drivers/spi/spi-intel-platform.c | 1 + drivers/spi/spi-intel.c | 64 +++++++++++++++++-- drivers/spi/spi-intel.h | 2 + 5 files changed, 83 insertions(+), 5 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-driver-spi-intel
Documentation/ABI/testing/sysfs-driver-spi-intel new file +20 -0
@@ -0,0 +1,20 @@ +What: /sys/devices/.../intel_spi_protected +Date: Feb 2025 +KernelVersion: 6.13 +Contact: Alexander Usyskin <[email protected]> +Description: This attribute allows the userspace to check if the + Intel SPI flash controller is write protected from the host. + +What: /sys/devices/.../intel_spi_locked +Date: Feb 2025 +KernelVersion: 6.13 +Contact: Alexander Usyskin <[email protected]> +Description: This attribute allows the user space to check if the + Intel SPI flash controller locks supported opcodes. + +What: /sys/devices/.../intel_spi_bios_locked +Date: Feb 2025 +KernelVersion: 6.13 +Contact: Alexander Usyskin <[email protected]> +Description: This attribute allows the user space to check if the + Intel SPI flash controller BIOS region is locked for writes.
drivers/spi/spi-intel-pci.c +1 -0
@@ -94,6 +94,7 @@ static struct pci_driver intel_spi_pci_driver = { .name = "intel-spi", .id_table = intel_spi_pci_ids, .probe = intel_spi_pci_probe, + .dev_groups = intel_spi_groups, };module_pci_driver (intel_spi_pci_driver);
drivers/spi/spi-intel-platform.c +1 -0
@@ -28,6 +28,7 @@ static struct platform_driver intel_spi_platform_driver = { .probe = intel_spi_platform_probe, .driver = { .name = "intel-spi", + .dev_groups = intel_spi_groups, }, };
drivers/spi/spi-intel.c +59 -5
101 lines not on this page · raw message
drivers/spi/spi-intel.h +2 -0
@@ -13,6 +13,8 @@struct resource ; +extern const struct attribute_group *intel_spi_groups[]; +int intel_spi_probe (struct device *dev,struct resource *mem,const struct intel_spi_boardinfo *info);
Signature · 1 line
2.45.2
Mark Brown
maintainerQuoted 11 lines · Mika Westerberg
The manufacturing access to the PCH/SoC SPI device is traditionally performed via userspace driver accessing registers via
/dev/membut due to security concerns/dev/memaccess is being much restricted, hence the reason for utilizing dedicated Intel PCH/SoC SPI controller driver, which is already implemented in the Linux kernel.Intel PCH/SoC SPI controller protects the flash storage via two mechanisms one is the via region protection registers and second via BIOS lock. The BIOS locks only the BIOS regions usually 0 and/or 6.
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: intel: Add protected and locked attributes
commit: b1258105f9ce5203f48a47fd2f2cec8c38c41841
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark