From: "Oldřich Jedlička" <oldium.pro@gmail.com>
To: linux-raid@vger.kernel.org
Cc: "Oldřich Jedlička" <oldium.pro@gmail.com>
Subject: [PATCH 1/1] mdadm: enable Intel Alderlake RST VMD configuration
Date: Fri, 5 Aug 2022 12:05:45 +0200 [thread overview]
Message-ID: <20220805100545.9369-2-oldium.pro@gmail.com> (raw)
In-Reply-To: <20220805100545.9369-1-oldium.pro@gmail.com>
Alderlake changed UEFI variable name to 'RstVmdV' also and for VMD devices,
so check the updated name for VMD devices like it is done in the SATA case.
Signed-off-by: Oldřich Jedlička <oldium.pro@gmail.com>
---
platform-intel.c | 19 ++++++++++++-------
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/platform-intel.c b/platform-intel.c
index a4d55a3..2f8e6af 100644
--- a/platform-intel.c
+++ b/platform-intel.c
@@ -512,8 +512,8 @@ static const struct imsm_orom *find_imsm_hba_orom(struct sys_dev *hba)
#define AHCI_PROP "RstSataV"
#define AHCI_SSATA_PROP "RstsSatV"
#define AHCI_TSATA_PROP "RsttSatV"
-#define AHCI_RST_PROP "RstVmdV"
-#define VMD_PROP "RstUefiV"
+#define RST_VMD_PROP "RstVmdV"
+#define RST_UEFI_PROP "RstUefiV"
#define VENDOR_GUID \
EFI_GUID(0x193dfefa, 0xa445, 0x4302, 0x99, 0xd8, 0xef, 0x3a, 0xad, 0x1a, 0x04, 0xc6)
@@ -607,7 +607,8 @@ const struct imsm_orom *find_imsm_efi(struct sys_dev *hba)
struct orom_entry *ret;
static const char * const sata_efivars[] = {AHCI_PROP, AHCI_SSATA_PROP,
AHCI_TSATA_PROP,
- AHCI_RST_PROP};
+ RST_VMD_PROP};
+ static const char * const vmd_efivars[] = {RST_UEFI_PROP, RST_VMD_PROP};
unsigned long i;
if (check_env("IMSM_TEST_AHCI_EFI") || check_env("IMSM_TEST_SCU_EFI"))
@@ -640,10 +641,14 @@ const struct imsm_orom *find_imsm_efi(struct sys_dev *hba)
break;
case SYS_DEV_VMD:
- if (!read_efi_variable(&orom, sizeof(orom), VMD_PROP,
- VENDOR_GUID))
- break;
- return NULL;
+ for (i = 0; i < ARRAY_SIZE(vmd_efivars); i++) {
+ if (!read_efi_variable(&orom, sizeof(orom),
+ vmd_efivars[i], VENDOR_GUID))
+ break;
+ }
+ if (i == ARRAY_SIZE(vmd_efivars))
+ return NULL;
+ break;
default:
return NULL;
}
--
2.37.1
next prev parent reply other threads:[~2022-08-05 10:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 10:05 [PATCH 0/1] enable Intel Alderlake RST VMD configuration Oldřich Jedlička
2022-08-05 10:05 ` Oldřich Jedlička [this message]
2022-08-05 11:56 ` [PATCH 1/1] mdadm: " Kinga Tanska
2022-08-05 12:50 ` Oldřich Jedlička
2022-08-11 10:18 ` Mariusz Tkaczyk
2022-08-11 19:38 ` Oldřich Jedlička
2022-08-16 11:43 ` Mariusz Tkaczyk
2022-08-18 14:12 ` Kinga Tanska
2022-08-18 14:53 ` Oldřich Jedlička
2022-08-18 15:21 ` Oldřich Jedlička
2022-08-23 14:03 ` Kinga Tanska
2022-08-25 18:57 ` Oldřich Jedlička
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=20220805100545.9369-2-oldium.pro@gmail.com \
--to=oldium.pro@gmail.com \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).