All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: imammedo@redhat.com, qemu-devel@nongnu.org, shannon.zhao@linaro.org
Subject: Re: [Qemu-devel] [PATCH 1/2] ACPI: Add definitions for the SPCR table
Date: Tue, 9 Jun 2015 19:28:26 +0200	[thread overview]
Message-ID: <20150609191908-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20150609170304.GB9626@hawk.localdomain>

On Tue, Jun 09, 2015 at 07:03:04PM +0200, Andrew Jones wrote:
> On Tue, Jun 09, 2015 at 04:52:39PM +0200, Michael S. Tsirkin wrote:
> > On Mon, Jun 08, 2015 at 10:00:49AM -0400, Andrew Jones wrote:
> > > SPCR is the Serial Port Console Redirection table. See the document
> > > linked from http://uefi.org/acpi. For serial port types, "Interface
> > > Type", see the documentation for the Debug Port Table 2 (DBG2).
> > > 
> > > Signed-off-by: Andrew Jones <drjones@redhat.com>
> > > ---
> > >  include/hw/acpi/acpi-defs.h | 72 +++++++++++++++++++++++++++++++++++++++++++++
> > >  1 file changed, 72 insertions(+)
> > > 
> > > diff --git a/include/hw/acpi/acpi-defs.h b/include/hw/acpi/acpi-defs.h
> > > index 59cf277434b37..e579d4c509fc8 100644
> > > --- a/include/hw/acpi/acpi-defs.h
> > > +++ b/include/hw/acpi/acpi-defs.h
> > > @@ -197,6 +197,78 @@ enum {
> > >  };
> > >  
> > >  /*
> > > + * ACPI Serial Port Console Redirection Table
> > > + */
> > > +enum {
> > > +    ACPI_SERIAL_16550_COMPAT        = 0,
> > > +    ACPI_SERIAL_16550_SUBSET_COMPAT = 1,
> > > +    ACPI_SERIAL_ARM_PL011_UART      = 3,
> > > +};
> > > +
> > > +enum {
> > > +    ACPI_SERIAL_ITYPE_PC            = 1,
> > > +    ACPI_SERIAL_ITYPE_APIC          = 2,
> > > +    ACPI_SERIAL_ITYPE_SAPIC         = 4,
> > > +    ACPI_SERIAL_ITYPE_ARMH_GIC      = 8,
> > > +};
> > > +
> > > +enum {
> > > +    ACPI_SERIAL_BAUD_9600           = 3,
> > > +    ACPI_SERIAL_BAUD_19200          = 4,
> > > +    ACPI_SERIAL_BAUD_57600          = 6,
> > > +    ACPI_SERIAL_BAUD_115200         = 7,
> > > +};
> > > +
> > > +enum {
> > > +    ACPI_SERIAL_FLOW_DCD_REQUIRED   = 1,
> > > +    ACPI_SERIAL_FLOW_HW             = 2,
> > > +    ACPI_SERIAL_FLOW_SW             = 4,
> > > +};
> > > +
> > > +enum {
> > > +    ACPI_SERIAL_TERM_VT100          = 0,
> > > +    ACPI_SERIAL_TERM_VT100_PLUS     = 1,
> > > +    ACPI_SERIAL_TERM_VT_UTF8        = 2,
> > > +    ACPI_SERIAL_TERM_ANSI           = 3,
> > > +};
> > > +
> > 
> > Please don't do these single-use enums, this more than doubles the
> > amount of code required and makes it hard to look up things in spec.
> 
> They also serve to document the structure though. Without them
> we either need to add several lines to the comments for the struct
> members, or to simply not document the structure at all.

The idea is to document the code, that has both values
and struct names together.

> But, if
> the general preference is less lines of code, at the expense of
> always needing the spec open, then I won't resist removing the
> enums

In some cases, we've already given up on structs too, using
things like build_append_int_noprefix instead.

> (and struct documentation?).

Move the documentation to build_spcr, yes.

> I don't understand how they make looking things up in the spec
> more difficult. Is it because the naming doesn't exactly match
> the spec verbiage?

Yes.

> In both cases, I guess the actual value is
> what would be compared on lookup.

It's very convenient to locate things quickly using
full text search.
Try doing a full text search for 0x0 in a spec :)



> > Do this instead
> > 	sprc->interface_type = 0x0; /* full 16550 interface */
> > 
> > you should also list earliest spec version which has the data
> > since spec text changes with time.
> 
> I'll change the header to
> 
> /*
>  * ACPI 2.0 Serial Port Console Redirection Table (SPCR)
>  */

Isn't it actually
	Microsoft Serial Port Console Redirection Table
and documented in a couple of other specs?
ACPI spec just lists the signatures.

> assuming I understood your comment correctly.
> 
> Thanks for the review,
> drew

  reply	other threads:[~2015-06-09 17:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 14:00 [Qemu-devel] [PATCH 0/2] ACPI: ARM: add SPCR table Andrew Jones
2015-06-08 14:00 ` [Qemu-devel] [PATCH 1/2] ACPI: Add definitions for the " Andrew Jones
2015-06-09 10:53   ` Shannon Zhao
2015-06-09 14:52   ` Michael S. Tsirkin
2015-06-09 17:03     ` Andrew Jones
2015-06-09 17:28       ` Michael S. Tsirkin [this message]
2015-06-08 14:00 ` [Qemu-devel] [PATCH 2/2] hw/arm/virt-acpi-build: Add " Andrew Jones
2015-06-09  2:54   ` Shannon Zhao
2015-06-09  9:53     ` Andrew Jones
2015-06-09 11:10   ` Shannon Zhao
2015-06-09 11:13 ` [Qemu-devel] [PATCH 0/2] ACPI: ARM: add " Shannon Zhao

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=20150609191908-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=drjones@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shannon.zhao@linaro.org \
    /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.