From: Alexandre Ghiti <alex@ghiti.fr>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Ryan Roberts <ryan.roberts@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
kernel@vger.kernel.org, Yunhui Cui <cuiyunhui@bytedance.com>,
linux-acpi@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-riscv@lists.infradead.org, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH 2/2] ACPI: support BGRT table on RISC-V
Date: Thu, 31 Jul 2025 21:51:48 +0200 [thread overview]
Message-ID: <8b933393-e9cf-4192-9e69-ef5c2a699c5b@ghiti.fr> (raw)
In-Reply-To: <CAJZ5v0hvaw=m8zPDJn0vPvw5RBxUsRzyvjHPiganPkxHGCisRw@mail.gmail.com>
On 7/31/25 20:17, Rafael J. Wysocki wrote:
> On Thu, Jul 31, 2025 at 3:13 PM Alexandre Ghiti <alex@ghiti.fr> wrote:
>> Hi Heinrich,
>>
>> On 7/29/25 15:15, Heinrich Schuchardt wrote:
>>> The BGRT table is used to display a vendor logo in the boot process.
>>> There is no good reason why RISC-V should not support it.
>>>
>>> Remove the architecture constraint.
>>>
>>> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
>>> ---
>>> drivers/acpi/Kconfig | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
>>> index 7bc40c2735ac0..2b83c91bb1a78 100644
>>> --- a/drivers/acpi/Kconfig
>>> +++ b/drivers/acpi/Kconfig
>>> @@ -460,7 +460,7 @@ config ACPI_HED
>>>
>>> config ACPI_BGRT
>>> bool "Boottime Graphics Resource Table support"
>>> - depends on EFI && (X86 || ARM64 || LOONGARCH)
>>> + depends on EFI
>>> help
>>> This driver adds support for exposing the ACPI Boottime Graphics
>>> Resource Table, which allows the operating system to obtain
>>
>> @Rafael: If you ack this patch, I can merge that for 6.17 as I haven't
>> sent my PR yet, just let me know!
> There you go:
>
> Acked-by: Rafael J. Wysocki <rafael@kernel.org>
Great, thanks!
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-07-31 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 13:15 [PATCH 0/2] ACPI: support BGRT table on RISC-V Heinrich Schuchardt
2025-07-29 13:15 ` [PATCH 1/2] RISC-V: ACPI: enable parsing the BGRT table Heinrich Schuchardt
2025-07-29 13:15 ` [PATCH 2/2] ACPI: support BGRT table on RISC-V Heinrich Schuchardt
2025-07-31 13:13 ` Alexandre Ghiti
2025-07-31 18:17 ` Rafael J. Wysocki
2025-07-31 19:51 ` Alexandre Ghiti [this message]
2025-07-30 4:48 ` [PATCH 0/2] " Sunil V L
2025-08-06 17:15 ` patchwork-bot+linux-riscv
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=8b933393-e9cf-4192-9e69-ef5c2a699c5b@ghiti.fr \
--to=alex@ghiti.fr \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=catalin.marinas@arm.com \
--cc=cuiyunhui@bytedance.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=kernel@vger.kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rafael@kernel.org \
--cc=ryan.roberts@arm.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