public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: 运辉崔 <cuiyunhui@bytedance.com>
Cc: Conor Dooley <conor@kernel.org>, <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>, <alexghiti@rivosinc.com>,
	<sunilvl@ventanamicro.com>
Subject: Re: [External] Re: [PATCH v2 1/3] riscv: obtain ACPI RSDP from FFI.
Date: Mon, 3 Jul 2023 13:18:59 +0100	[thread overview]
Message-ID: <20230703-handstand-prototype-733d702c946c@wendy> (raw)
In-Reply-To: <CAEEQ3wnjYK+Jj9Ce_yEHPL_z3eYn4OKP85YLXnVeaPd+SA3DJw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]

On Mon, Jul 03, 2023 at 06:16:07PM +0800, 运辉崔 wrote:
> Hi Conor,

> This needs to be confirmed with you:

> Continue to follow the current code structure, patch 1/3 is placed in
> arch/riscv/, and 2/3 is placed under driver/firmware?

You do want the SMBIOS stuff to be cross architecture, right?
If so, keeping the code as-is seems to make the most sense to me.

> How about changing the commit log to the following?
> 
> riscv: obtain ACPI RSDP from devicetree.
> 
> On RISC-V, when using Coreboot to start, since Coreboot only supports
> DTS but not EFI, and
> RISC-V does not have a reserved address segment.
> When the system enables ACPI, ACPI RSDP needs to be passed through DTS

I would probably write something like:
	On RISC-V, Coreboot does not support booting using EFI, only devicetree
	nor does RISC-V have a reserved address segment.
	To allow using Coreboot on platforms that require ACPI, the ACPI RSDP
	needs to be passed to supervisor mode software using devicetree.
	Add support for parsing the "configtbls" devicetree node to find the
	ACPI entry point and use wire up acpi_arch_get_root_pointer().
	This feature is known as FDT Firmware Interface (FFI).

> > > > > +extern u64 acpi_rsdp;
> > > >
> > > > /stuff/linux/drivers/acpi/osl.c:178:22: error: redefinition of 'acpi_rsdp' with a different type: 'unsigned long' vs 'u64' (aka 'unsigned long long')
> > > >
> > > > Fails to build when Kexec is enabled.
> > >
> > > Rename my acpi_rsdp to arch_acpi_rsdp? WDYT?
> >
> > You could do s/arch/riscv/ either, that'd match what we prefix a lot of
> > stuff with.
> 
>  Sorry, I don't quite understand what you mean. Could you tell me in detail?

What I meant is that variables & functions in /arch/riscv are often
prefixed with riscv_. I was saying that you could change "arch_acpi_rsdp"
to "riscv_acpi_rsdp".

Thanks,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-07-03 12:20 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-02  9:57 [PATCH v2 1/3] riscv: obtain ACPI RSDP from FFI Yunhui Cui
2023-07-02  9:57 ` [PATCH v2 2/3] firmware: introduce FFI for SMBIOS entry Yunhui Cui
2023-07-02 12:41   ` Conor Dooley
2023-07-03  8:23     ` [External] " 运辉崔
2023-07-03  8:34       ` Conor Dooley
2023-07-03 12:41         ` 运辉崔
2023-07-03 13:02           ` Conor Dooley
2023-07-03 13:26             ` 运辉崔
2023-07-02  9:57 ` [PATCH v2 3/3] riscv: obtain SMBIOS entry from FFI Yunhui Cui
2023-07-02 12:42   ` Conor Dooley
2023-07-03  7:50     ` [External] " 运辉崔
2023-07-03  8:16       ` Conor Dooley
2023-07-02 13:47 ` [PATCH v2 1/3] riscv: obtain ACPI RSDP " Conor Dooley
2023-07-03  4:21   ` Sunil V L
2023-07-03  6:19     ` [External] " 运辉崔
2023-07-03  7:19   ` 运辉崔
2023-07-03  8:12     ` Conor Dooley
2023-07-03 10:16       ` 运辉崔
2023-07-03 12:18         ` Conor Dooley [this message]
2023-07-03 13:04           ` 运辉崔
2023-07-03 13:01 ` Andrew Jones
2023-07-03 13:30   ` [External] " 运辉崔
2023-07-03 14:17     ` Andrew Jones
2023-07-03 14:23       ` Conor Dooley
2023-07-03 18:58     ` Emil Renner Berthing
2023-07-03 21:32       ` [External] " Jessica Clarke
2023-07-05 14:42         ` Björn Töpel
2023-07-06  2:24           ` 运辉崔
2023-07-06  8:52             ` Björn Töpel
     [not found]               ` <CAP6exY+gTSxU95nDK14z-Y1suKeXPkLzZ_BZqr-vRVGO9qmcxg@mail.gmail.com>
2023-07-07  9:05                 ` Björn Töpel

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=20230703-handstand-prototype-733d702c946c@wendy \
    --to=conor.dooley@microchip.com \
    --cc=alexghiti@rivosinc.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=cuiyunhui@bytedance.com \
    --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