[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220518095646.47548-1-sunilvl@ventanamicro.com>
Date: Wed, 18 May 2022 15:26:45 +0530
From: Sunil V L <sunilvl@...tanamicro.com>
To: Ard Biesheuvel <ardb@...nel.org>,
Palmer Dabbelt <palmer@...belt.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Albert Ou <aou@...s.berkeley.edu>
Cc: Ilias Apalodimas <ilias.apalodimas@...aro.org>,
Heinrich Schuchardt <heinrich.schuchardt@...onical.com>,
Atish Patra <atishp@...osinc.com>,
Anup Patel <apatel@...tanamicro.com>,
Jessica Clarke <jrtc27@...c27.com>,
Abner Chang <abner.chang@....com>, linux-efi@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
Sunil V L <sunilvl@...tanamicro.com>,
Palmer Dabbelt <palmer@...osinc.com>
Subject: [PATCH V4 0/1] RISCV_EFI_BOOT_PROTOCOL support in linux
This patch adds support for getting the boot hart ID using new
RISCV_EFI_BOOT_PROTOCOL in linux efi stub. While there is an existing
solution of passing the boot hart ID through Device Tree, it doesn't work for
ACPI. Hence an EFI protocol protocol is recommended which works for both DT
and ACPI based platforms.
The spec of this new protocol post public review (Ratification-ready) is
available at:
https://github.com/riscv-non-isa/riscv-uefi/releases/download/1.0.0/RISCV_UEFI_PROTOCOL-spec.pdf
This is tested in qemu with both u-boot and edk2.
Changes since V3:
- Rebased, no code changes.
- cover letter updated with link to spec version after public review
Changes since V2:
- Updated error message
Changes since V1:
- Rebased to get the "Fix get_boot_hartid_from_fdt() return value"
patch
- Removed mixed_mode member
- Separated return value and status.
Sunil V L (1):
riscv/efi_stub: Add support for RISCV_EFI_BOOT_PROTOCOL
drivers/firmware/efi/libstub/efistub.h | 7 ++++++
drivers/firmware/efi/libstub/riscv-stub.c | 29 +++++++++++++++++++----
include/linux/efi.h | 1 +
3 files changed, 32 insertions(+), 5 deletions(-)
--
2.25.1
Powered by blists - more mailing lists