From: Igor Mammedov <imammedo@redhat.com>
To: way sorry <waysorrypub@gmail.com>
Cc: qemu-devel@nongnu.org, 17746591750@163.com, maobibo@loongson.cn,
lixianglai@loongson.cn, jiaxun.yang@flygoat.com, mst@redhat.com,
anisinha@redhat.com
Subject: Re: [PATCH v4 2/4] hw/loongarch/virt-acpi-build: Drop UART _DSD clock and add _STA
Date: Thu, 22 Oct 2026 13:27:57 +0200 [thread overview]
Message-ID: <20261022132757.0f197972@imammedo> (raw)
In-Reply-To: <CAECqSzWt5gP91iOnoGcKymSYp_O6vt8=7s6-Mg616S_VVREYbg@mail.gmail.com>
On Thu, 22 Oct 2026 17:25:00 +0800
way sorry <waysorrypub@gmail.com> wrote:
> Hi Igor,
>
> One additional observation: QEMU's x86 ISA serial implementation explicitly
> defines _STA =
> 0x0f in serial_isa_build_aml(), rather than relying on the ACPI default:
>
> https://github.com/qemu/qemu/blob/8967b2fe1b2aaae3c29e207d85fab901d580a2dc/hw/char/serial-isa.c#L101
>
> I think following the same approach for LoongArch UART would be reasonable
> for consistency.
preexisting code in this case is not a good example to follow.
if it works without adding unnecessary stuff, do not add it.
DSD and CCA changes are also unrelated => separate patches
>
> Thanks,
> pillow
>
> On Thu, Oct 22, 2026 at 5:01 PM way sorry <waysorrypub@gmail.com> wrote:
>
> > Hi Igor,
> >
> > The _STA method was added in response to Bibo's review comment on the
> > original patch, where
> > he explicitly suggested adding _STA.
> >
> > I understand your concern that omitting _STA already implies 0x0f.
> > However, the two review
> > comments seem to suggest different approaches.
> >
> > I'm happy to split the changes into separate patches as required. For
> > _STA, though, I'd
> > appreciate it if we could first agree on whether it should be added or
> > omitted, so I have a clear
> > direction for the next version.
> >
> > Thanks,
> > pillow
> >
> > On Thu, Oct 22, 2026 at 4:18 PM Igor Mammedov <imammedo@redhat.com> wrote:
> >
> >> On Thu, 22 Oct 2026 15:22:36 +0800
> >> pillow <waysorrypub@gmail.com> wrote:
> >>
> >> ...
> >> > @@ -325,7 +324,7 @@ static void build_uart_device_aml(Aml *table, int
> >> index)
> >> ...
> >> > + aml_append(dev, aml_name_decl("_STA", aml_int(0x0f)));
> >>
> >> also is it really necessary? Doesn't missing _STA imply 0xF already?
> >>
> >> > crs = aml_resource_template();
> >> > aml_append(crs,
> >> > aml_qword_memory(AML_POS_DECODE, AML_MIN_FIXED, AML_MAX_FIXED,
> >>
> >>
next prev parent reply other threads:[~2026-10-22 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 7:22 [PATCH v4 0/4] hw/loongarch/virt: Fix UART ACPI and FDT pillow
2026-10-22 7:22 ` [PATCH v4 1/4] bios-tables-test-allowed-diff.h: Allow LoongArch DSDT.* pillow
2026-10-22 7:22 ` [PATCH v4 2/4] hw/loongarch/virt-acpi-build: Drop UART _DSD clock and add _STA pillow
2026-10-22 8:15 ` Igor Mammedov
2026-10-22 8:18 ` Igor Mammedov
2026-10-22 9:01 ` way sorry
2026-10-22 9:25 ` way sorry
2026-10-22 11:27 ` Igor Mammedov [this message]
2026-10-22 7:22 ` [PATCH v4 3/4] tests/data/acpi/loongarch64: Update expected DSDT.* pillow
2026-10-22 7:22 ` [PATCH v4 4/4] hw/loongarch/virt: Fix UART clock frequency in FDT pillow
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=20261022132757.0f197972@imammedo \
--to=imammedo@redhat.com \
--cc=17746591750@163.com \
--cc=anisinha@redhat.com \
--cc=jiaxun.yang@flygoat.com \
--cc=lixianglai@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=waysorrypub@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.