From: Mark Pearson <markpearson@lenovo.com>
To: <markpearson@lenovo.com>
Cc: <hdegoede@redhat.com>, <mgross@linux.intel.com>,
<platform-driver-x86@vger.kernel.org>
Subject: [PATCH 1/2] Documentation: syfs-class-firmware-attributes: Lenovo Opcode support
Date: Mon, 8 Nov 2021 18:25:32 -0500 [thread overview]
Message-ID: <20211108232533.211693-1-markpearson@lenovo.com> (raw)
In-Reply-To: <markpearson@lenovo.com>
Newer Lenovo BIOS's have an opcode GUID support interface which provides
- improved password setting control
- ability to set System, hard drive and NVMe passwords
Add the support for these new passwords, and the ability to select
user/master mode and the drive index.
Signed-off-by: Mark Pearson <markpearson@lenovo.com>
---
.../ABI/testing/sysfs-class-firmware-attributes | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-class-firmware-attributes b/Documentation/ABI/testing/sysfs-class-firmware-attributes
index 3348bf80a37c..6af4c5cf3d47 100644
--- a/Documentation/ABI/testing/sysfs-class-firmware-attributes
+++ b/Documentation/ABI/testing/sysfs-class-firmware-attributes
@@ -161,6 +161,12 @@ Description:
power-on:
Representing a password required to use
the system
+ system-mgmt:
+ Representing System Management password
+ HDD:
+ Representing HDD password
+ NVMe:
+ Representing NVMe password
mechanism:
The means of authentication. This attribute is mandatory.
@@ -185,6 +191,17 @@ Description:
A write only value that when used in tandem with
current_password will reset a system or admin password.
+ level:
+ Used with HDD and NVMe authentication to set 'user' or 'master'
+ privilege level
+ This attribute defaults to 'user' level
+
+ index:
+ Used with HDD and NVME authentication to set the drive index
+ that is being referenced (e.g hdd0, hdd1 etc)
+ This attribute defaults to device 0.
+
+
Note, password management is session specific. If Admin password is set,
same password must be written into current_password file (required for
password-validation) and must be cleared once the session is over.
--
2.31.1
next reply other threads:[~2021-11-08 23:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 23:25 Mark Pearson [this message]
2021-11-08 23:25 ` [PATCH 2/2] platform/x86: think-lmi: Opcode support Mark Pearson
2021-11-16 14:07 ` Hans de Goede
2021-11-16 21:08 ` [External] " Mark Pearson
2021-11-16 14:00 ` [PATCH 1/2] Documentation: syfs-class-firmware-attributes: Lenovo " Hans de Goede
2021-11-16 21:05 ` [External] " Mark Pearson
2021-11-17 12:09 ` Hans de Goede
2021-11-17 15:20 ` Mark Pearson
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=20211108232533.211693-1-markpearson@lenovo.com \
--to=markpearson@lenovo.com \
--cc=hdegoede@redhat.com \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@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