From: Igor Mammedov <imammedo@redhat.com>
To: Sunil V L <sunilvl@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Bin Meng <bmeng.cn@gmail.com>, Weiwei Li <liwei1518@gmail.com>,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Ani Sinha <anisinha@redhat.com>
Subject: Re: [PATCH v3 2/9] hw/riscv/virt-acpi-build.c: Update the HID of RISC-V UART
Date: Tue, 16 Jul 2024 12:28:21 +0200 [thread overview]
Message-ID: <20240716122821.2480bdc5@imammedo.users.ipa.redhat.com> (raw)
In-Reply-To: <20240715171129.1168896-3-sunilvl@ventanamicro.com>
On Mon, 15 Jul 2024 22:41:22 +0530
Sunil V L <sunilvl@ventanamicro.com> wrote:
> The requirement ACPI_060 in the RISC-V BRS specification [1], requires
> NS16550 compatible UART to have the HID RSCV0003. So, update the HID for
> the UART.
>
> [1] - https://github.com/riscv-non-isa/riscv-brs/commits/main/acpi.adoc
this should point to text like in previous patch and not to commit
> (commit: 7bfa87e86ad5658283731207dbfc8ab3744d3265)
>
> Signed-off-by: Sunil V L <sunilvl@ventanamicro.com>
> Acked-by: Alistair Francis <alistair.francis@wdc.com>
with above fixed:
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> ---
> hw/riscv/virt-acpi-build.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/riscv/virt-acpi-build.c b/hw/riscv/virt-acpi-build.c
> index 5f5082a35b..36d6a3a412 100644
> --- a/hw/riscv/virt-acpi-build.c
> +++ b/hw/riscv/virt-acpi-build.c
> @@ -170,7 +170,7 @@ acpi_dsdt_add_uart(Aml *scope, const MemMapEntry *uart_memmap,
> uint32_t uart_irq)
> {
> Aml *dev = aml_device("COM0");
> - aml_append(dev, aml_name_decl("_HID", aml_string("PNP0501")));
> + aml_append(dev, aml_name_decl("_HID", aml_string("RSCV0003")));
> aml_append(dev, aml_name_decl("_UID", aml_int(0)));
>
> Aml *crs = aml_resource_template();
next prev parent reply other threads:[~2024-07-16 10:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 17:11 [PATCH v3 0/9] RISC-V: ACPI: Namespace updates Sunil V L
2024-07-15 17:11 ` [PATCH v3 1/9] hw/riscv/virt-acpi-build.c: Add namespace devices for PLIC and APLIC Sunil V L
2024-07-16 10:24 ` Igor Mammedov
2024-07-16 12:14 ` Sunil V L
2024-07-15 17:11 ` [PATCH v3 2/9] hw/riscv/virt-acpi-build.c: Update the HID of RISC-V UART Sunil V L
2024-07-16 10:28 ` Igor Mammedov [this message]
2024-07-15 17:11 ` [PATCH v3 3/9] tests/acpi: Allow DSDT acpi table changes for aarch64 Sunil V L
2024-07-15 17:11 ` [PATCH v3 4/9] acpi/gpex: Create PCI link devices outside PCI root bridge Sunil V L
2024-07-16 10:33 ` Igor Mammedov
2024-07-15 17:11 ` [PATCH v3 5/9] tests/acpi: update expected DSDT blob for aarch64 and microvm Sunil V L
2024-07-15 17:11 ` [PATCH v3 6/9] tests/qtest/bios-tables-test.c: Remove the fall back path Sunil V L
2024-07-15 17:11 ` [PATCH v3 7/9] tests/acpi: Add empty ACPI data files for RISC-V Sunil V L
2024-07-15 17:11 ` [PATCH v3 8/9] tests/qtest/bios-tables-test.c: Enable basic testing " Sunil V L
2024-07-15 17:11 ` [PATCH v3 9/9] tests/acpi: Add expected ACPI AML files " Sunil V L
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=20240716122821.2480bdc5@imammedo.users.ipa.redhat.com \
--to=imammedo@redhat.com \
--cc=alistair.francis@wdc.com \
--cc=anisinha@redhat.com \
--cc=bmeng.cn@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=mst@redhat.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sunilvl@ventanamicro.com \
--cc=zhiwei_liu@linux.alibaba.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).