From: Yunhui Cui <cuiyunhui@bytedance.com>
To: conor@kernel.org, sunilvl@ventanamicro.com, ardb@kernel.org,
palmer@dabbelt.com, paul.walmsley@sifive.com,
aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
rminnich@gmail.com, mark.rutland@arm.com, lpieralisi@kernel.org,
rafael@kernel.org, lenb@kernel.org, jdelvare@suse.com,
yc.hung@mediatek.com, angelogioacchino.delregno@collabora.com,
allen-kh.cheng@mediatek.com,
pierre-louis.bossart@linux.intel.com, tinghan.shen@mediatek.com,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
geshijian@bytedance.com, weidong.wd@bytedance.com,
cuiyunhui@bytedance.com
Subject: [PATCH v3 0/4] Obtain SMBIOS and ACPI entry from FFI
Date: Wed, 5 Jul 2023 19:42:47 +0800 [thread overview]
Message-ID: <20230705114251.661-1-cuiyunhui@bytedance.com> (raw)
Here's version 3 of patch series.
V1: The FFI (FDT FIRMWARE INTERFACE) scheme has reached a
consensus with the Maintainers.
Please refer to:
https://patches.linaro.org/project/linux-acpi/patch/20230426034001.16-1-cuiyunhui@bytedance.com/
Changes v1->v2:
Adjusted the code structure, put the ACPI part under the RISC-V architecture,
and put the general part of obtaining SMBIOS entry through FFI
under driver/firmware/.
Please refer to:
https://lore.kernel.org/lkml/20230703-71f67eb66a037f5c0fb825c6@orel/T/
Changes v2->v3:
According to the suggestions of maintainers, the code has been modified as follows:
1. Modified the commit log.
2. Added description of "ffitbl" subnod in dt-bindings.
3. Add stub function to the function
4. arch/riscv/ and driver/firmware/ use CONFIG_FDT_FW_INTERFACE to control
5. Modified the ffi_smbios_root_pointer() function logic and printing
etc.
Yunhui Cui (4):
riscv: obtain ACPI RSDP from devicetree
firmware: introduce FFI for SMBIOS entry
riscv: obtain SMBIOS entry from FFI
dt-bindings: firmware: Document ffitbl binding
.../devicetree/bindings/firmware/ffitbl.txt | 27 ++++++
MAINTAINERS | 13 +++
arch/riscv/include/asm/acpi.h | 9 ++
arch/riscv/include/asm/ffi.h | 14 +++
arch/riscv/kernel/Makefile | 1 +
arch/riscv/kernel/ffi.c | 40 ++++++++
arch/riscv/kernel/setup.c | 2 +
drivers/firmware/Kconfig | 11 +++
drivers/firmware/Makefile | 1 +
drivers/firmware/dmi_scan.c | 97 +++++++++++--------
drivers/firmware/ffi.c | 42 ++++++++
include/linux/ffi.h | 29 ++++++
12 files changed, 246 insertions(+), 40 deletions(-)
create mode 100644 Documentation/devicetree/bindings/firmware/ffitbl.txt
create mode 100644 arch/riscv/include/asm/ffi.h
create mode 100644 arch/riscv/kernel/ffi.c
create mode 100644 drivers/firmware/ffi.c
create mode 100644 include/linux/ffi.h
--
2.20.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-07-05 11:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 11:42 Yunhui Cui [this message]
2023-07-05 11:42 ` [PATCH v3 1/4] riscv: obtain ACPI RSDP from devicetree Yunhui Cui
2023-07-05 11:42 ` [PATCH v3 2/4] firmware: introduce FFI for SMBIOS entry Yunhui Cui
2023-07-05 11:42 ` [PATCH v3 3/4] riscv: obtain SMBIOS entry from FFI Yunhui Cui
2023-07-05 11:42 ` [PATCH v3 4/4] dt-bindings: firmware: Document ffitbl binding Yunhui Cui
2023-07-05 15:06 ` Conor Dooley
2023-07-06 3:43 ` [External] " 运辉崔
2023-07-06 6:00 ` Krzysztof Kozlowski
2023-07-06 6:24 ` 运辉崔
2023-07-06 6:41 ` Krzysztof Kozlowski
2023-07-06 6:55 ` 运辉崔
2023-07-06 6:44 ` Conor Dooley
2023-07-06 9:02 ` 运辉崔
2023-07-07 16:16 ` Conor Dooley
[not found] ` <CAN3iYbP_dQOOJKLjAf+pVeYUZRBqwZBG7eq6=pR0upsjT2GpOA@mail.gmail.com>
2023-07-08 3:04 ` [External] " 运辉崔
2023-07-08 8:09 ` Conor Dooley
2023-07-05 14:17 ` [PATCH v3 0/4] Obtain SMBIOS and ACPI entry from FFI Palmer Dabbelt
2023-07-05 15:33 ` Conor Dooley
2023-07-06 2:04 ` [External] " 运辉崔
2023-07-06 8:53 ` Ard Biesheuvel
2023-07-06 15:32 ` Palmer Dabbelt
[not found] ` <CAP6exYKwZG=_47r0jAUFYNL5-P-SS==k6vWdKiMJ9nB0upH5Zw@mail.gmail.com>
2023-07-06 21:47 ` Conor Dooley
2023-07-06 21:53 ` ron minnich
2023-07-07 8:38 ` Conor Dooley
2023-07-07 10:43 ` Sunil V L
[not found] ` <CAN3iYbMhQU5Ng4r6_rQDnLmit1GCmheC5T49rsUP5NgHFEXsHA@mail.gmail.com>
2023-07-07 12:55 ` Sunil V L
[not found] ` <CAN3iYbOe+i4jVhz0sSQwVQ2PMB7UvaTPyN_sLtZj0uiOD2emDA@mail.gmail.com>
2023-07-07 16:07 ` Conor Dooley
2023-07-07 16:18 ` 葛士建
[not found] ` <DBAPR08MB5783AED8329E38D840B7015D9C2DA@DBAPR08MB5783.eurprd08.prod.outlook.com>
[not found] ` <CAMj1kXEkL0gF8uGcy2AjJvD-yZHmyLX9jiVVDtR+uBAYf+BfUg@mail.gmail.com>
2023-07-08 12:03 ` Sunil V L
2023-07-08 16:26 ` Palmer Dabbelt
[not found] ` <CAN3iYbMsUNMH27kdtwPwLeBSUfH0gTvyqjZ8ExZaoGcuv8CBdA@mail.gmail.com>
2023-09-07 12:15 ` yunhui cui
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=20230705114251.661-1-cuiyunhui@bytedance.com \
--to=cuiyunhui@bytedance.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=conor@kernel.org \
--cc=geshijian@bytedance.com \
--cc=jdelvare@suse.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rafael@kernel.org \
--cc=rminnich@gmail.com \
--cc=sunilvl@ventanamicro.com \
--cc=tinghan.shen@mediatek.com \
--cc=weidong.wd@bytedance.com \
--cc=yc.hung@mediatek.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;
as well as URLs for NNTP newsgroup(s).