From: Sunil V L <sunilvl@ventanamicro.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: ardb@kernel.org, Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, heinrich.schuchardt@canonical.com,
Atish Patra <atishp@rivosinc.com>,
apatel@ventanamicro.com, abner.chang@hpe.com, jrtc27@jrtc27.com,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [RFC PATCH V2 0/1] RISCV_EFI_BOOT_PROTOCOL support in linux
Date: Wed, 23 Mar 2022 21:57:48 +0530 [thread overview]
Message-ID: <20220323162748.GA55066@sunil-laptop> (raw)
In-Reply-To: <mhng-5eb23850-e2a9-43d3-8093-2f588c71de00@palmer-ri-x1c9>
On Tue, Mar 22, 2022 at 06:32:22PM -0700, Palmer Dabbelt wrote:
> On Thu, 03 Mar 2022 06:59:43 PST (-0800), sunilvl@ventanamicro.com wrote:
> > 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 latest draft spec of this new protocol is available at
> > https://github.com/riscv-non-isa/riscv-uefi/releases/download/1.0-rc2/RISCV_UEFI_PROTOCOL-spec.pdf
>
> This looks fine to me, but we need the spec folk to commit to this being a
> stable interface before we can start using it. Historically that's been
> "frozen" for RISC-V specs, but I'm not sure how that all fits together in
> EFI land as IIUC we also have to follow the UEFI forum's process. Last I
> checked you guys understood that better than I did, so
Thank you Palmer. The specification is in frozen state now.
http://lists.infradead.org/pipermail/linux-riscv/2022-March/013431.html.
Thanks
Sunil
>
> Acked-by: Palmer Dabbelt <palmer@rivosinc.com> # pending spec freeze
>
> I had a minor comment about the error message, as well.
>
> Thanks!
>
> > This linux ptach can be found in:
> > riscv_boot_protocol_rfc_v2 branch at
> > https://github.com/vlsunil/linux.git
> >
> > This is tested in qemu with u-boot 2022.04.rc3.
> >
> > 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(-)
prev parent reply other threads:[~2022-03-23 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 14:59 [RFC PATCH V2 0/1] RISCV_EFI_BOOT_PROTOCOL support in linux Sunil V L
2022-03-03 14:59 ` [RFC PATCH V2 1/1] riscv/efi_stub: Add support for RISCV_EFI_BOOT_PROTOCOL Sunil V L
2022-03-23 1:32 ` Palmer Dabbelt
2022-03-24 11:01 ` Sunil V L
2022-03-23 1:32 ` [RFC PATCH V2 0/1] RISCV_EFI_BOOT_PROTOCOL support in linux Palmer Dabbelt
2022-03-23 16:27 ` Sunil V L [this message]
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=20220323162748.GA55066@sunil-laptop \
--to=sunilvl@ventanamicro.com \
--cc=abner.chang@hpe.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=ardb@kernel.org \
--cc=atishp@rivosinc.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=jrtc27@jrtc27.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox