From: Vadim Chichikalyuk <chichikalyuk@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, Vadim Chichikalyuk <chichikalyuk@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Ani Sinha <anisinha@redhat.com>,
Shannon Zhao <shannon.zhaosl@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: [PATCH v2 0/3] hw: acpi: add UART clock freq to AArch64 SPCR
Date: Sun, 10 Aug 2025 00:10:48 +0300 [thread overview]
Message-ID: <20250809211051.68824-1-chichikalyuk@gmail.com> (raw)
This series upgrades the ACPI SPCR table for AArch64 virt to revision 4,
adding the UART clock frequency, which was not previously available via ACPI.
Regarding the NamespaceString: following the example of the SPCR table
for RISC-V, I've set it to "." (indicating that there is no device
corresponding to the UART in the ACPI namespace). However, looking
at build_dsdt(), the UART is actually added to the DSDT, as
"\_SB.COM0" (same as RISC-V). Should the NamespaceString be that instead?
Thanks,
Vadim
Signed-off-by: Vadim Chichikalyuk <chichikalyuk@gmail.com>
Vadim Chichikalyuk (3):
tests: acpi: whitelist expected blobs
hw: arm: acpi: upgrade SPCR table to revision 4
tests: acpi: update expected blobs
hw/arm/virt-acpi-build.c | 14 ++++++++------
tests/data/acpi/aarch64/virt/SPCR | Bin 80 -> 90 bytes
2 files changed, 8 insertions(+), 6 deletions(-)
--
2.39.5 (Apple Git-154)
next reply other threads:[~2025-08-09 21:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 21:10 Vadim Chichikalyuk [this message]
2025-08-09 21:10 ` [PATCH v2 1/3] tests: acpi: whitelist expected blobs Vadim Chichikalyuk
2025-08-09 21:10 ` [PATCH v2 2/3] hw: arm: acpi: upgrade SPCR table to revision 4 Vadim Chichikalyuk
2025-08-18 15:41 ` Peter Maydell
2025-08-09 21:10 ` [PATCH v2 3/3] tests: acpi: update expected blobs Vadim Chichikalyuk
2025-08-18 15:26 ` [PATCH v2 0/3] hw: acpi: add UART clock freq to AArch64 SPCR Peter Maydell
2025-08-24 23:00 ` Vadim Chichikalyuk
2025-08-25 12:50 ` Peter Maydell
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=20250809211051.68824-1-chichikalyuk@gmail.com \
--to=chichikalyuk@gmail.com \
--cc=anisinha@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhaosl@gmail.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).