[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEEQ3wn2zHUZP8gs8ezCczQLdQJqU6MqAgpcG0YeDW2aYTz0TA@mail.gmail.com>
Date: Mon, 26 Jun 2023 10:35:01 +0800
From: 运辉崔 <cuiyunhui@...edance.com>
To: ron minnich <rminnich@...il.com>
Cc: Ard Biesheuvel <ardb@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>, rafael@...nel.org,
lenb@...nel.org, jdelvare@...e.com, yc.hung@...iatek.com,
angelogioacchino.delregno@...labora.com,
allen-kh.cheng@...iatek.com, pierre-louis.bossart@...ux.intel.com,
tinghan.shen@...iatek.com,
lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-acpi@...r.kernel.org,
葛士建 <geshijian@...edance.com>,
韦东 <weidong.wd@...edance.com>
Subject: Re: [External] Re: [PATCH] firmware: added a firmware information
passing method FFI
Hi Ron, Ard,
On Sun, Jun 25, 2023 at 11:57 PM ron minnich <rminnich@...il.com> wrote:
>
> Hey Ard, thanks for the discussion, sounds like we are able to move forward now!
>
> On Sun, Jun 25, 2023, 6:13 AM Ard Biesheuvel <ardb@...nel.org> wrote:
>>
>> If this is only used on RISC-V, and implemented under arch/riscv, I
>> have no objections.
Thank you for your suggestions that made us reach an agreement, let's
continue to review this patch.
The current logic is to implement the common interface under
drivers/firmware/, if we need this function, we can call
fdt_fwtbl_init() to complete it in arch/xxx/kernel/setup.c.
For enabling on RISC-V, we can complete it in a subsequent patch to
setup_arch-->fdt_fwtbl_init() in arch/riscv/kernel/setup.c.
What do you think?
Thanks,
Yunhui
Powered by blists - more mailing lists