public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Pete Batard <pete@akeo.ie>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
	Leif Lindholm <leif@nuviainc.com>
Subject: Re: [PATCH 1/1] EmbeddedPkg/AcpiLib: add GICC table init macro for ACPI 6.3
Date: Mon, 30 Mar 2020 15:06:43 +0200	[thread overview]
Message-ID: <CAKv+Gu_yThBiobM=mE_PdbKUYZhM25KCNCRfVZY9SA1FYXkZdw@mail.gmail.com> (raw)
In-Reply-To: <a3c8b289-6603-4e3d-9c19-9d16a27df9b6@akeo.ie>

On Fri, 27 Mar 2020 at 14:06, Pete Batard <pete@akeo.ie> wrote:
>
> Incidentally, this is not an [edk2-platform] patch, as the subject line
> from previous mail seemed to indicate, but an [edk2] patch.
>

Do we have a user for this?

>
> On 2020.03.27 13:01, Pete Batard wrote:
> > ACPI 6.3 added a 16-bit SPE overflow Interrupt field, replacing
> > 2 of the 3 reserved bytes that are defined at the end of the
> > GICC structure for 6.0.
> >
> > Add a new macro to initialise the new field.
> >
> > Signed-off-by: Pete Batard <pete@akeo.ie>
> > ---
> >   EmbeddedPkg/Include/Library/AcpiLib.h | 8 ++++++++
> >   1 file changed, 8 insertions(+)
> >
> > diff --git a/EmbeddedPkg/Include/Library/AcpiLib.h b/EmbeddedPkg/Include/Library/AcpiLib.h
> > index 5c6e2075de79..57d7bd595584 100644
> > --- a/EmbeddedPkg/Include/Library/AcpiLib.h
> > +++ b/EmbeddedPkg/Include/Library/AcpiLib.h
> > @@ -64,6 +64,14 @@
> >       {EFI_ACPI_RESERVED_BYTE, EFI_ACPI_RESERVED_BYTE, EFI_ACPI_RESERVED_BYTE}         \
> >     }
> >
> > +#define EFI_ACPI_6_3_GICC_STRUCTURE_INIT(GicId, AcpiCpuUid, Mpidr, Flags, PmuIrq,    \
> > +    GicBase, GicVBase, GicHBase, GsivId, GicRBase, Efficiency, SpeOvflIrq)           \
> > +  {                                                                                  \
> > +    EFI_ACPI_6_0_GIC, sizeof (EFI_ACPI_6_0_GIC_STRUCTURE), EFI_ACPI_RESERVED_WORD,   \
> > +    GicId, AcpiCpuUid, Flags, 0, PmuIrq, 0, GicBase, GicVBase, GicHBase,             \
> > +    GsivId, GicRBase, Mpidr, Efficiency, EFI_ACPI_RESERVED_BYTE, SpeOvflIrq          \
> > +  }
> > +
> >   #define EFI_ACPI_6_0_GIC_MSI_FRAME_INIT(GicMsiFrameId, PhysicalBaseAddress, Flags, SPICount, SPIBase) \
> >     { \
> >       EFI_ACPI_6_0_GIC_MSI_FRAME, sizeof (EFI_ACPI_6_0_GIC_MSI_FRAME_STRUCTURE), EFI_ACPI_RESERVED_WORD, \
> >
>

  reply	other threads:[~2020-03-30 13:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 13:01 [edk2-platforms][PATCH 1/1] EmbeddedPkg/AcpiLib: add GICC table init macro for ACPI 6.3 Pete Batard
2020-03-27 13:06 ` [PATCH " Pete Batard
2020-03-30 13:06   ` Ard Biesheuvel [this message]
2020-03-30 13:09     ` Pete Batard
2020-03-30 13:12       ` Ard Biesheuvel
2020-03-30 13:20         ` Ard Biesheuvel
2020-03-30 13:56           ` Pete Batard
2020-03-30 14:01             ` Ard Biesheuvel
2020-03-30 14:06               ` Pete Batard
2020-03-30 14:16                 ` Ard Biesheuvel
2020-03-30 14:29                   ` Pete Batard
2020-03-30 14:34                     ` Ard Biesheuvel
2020-03-30 14:39                       ` Pete Batard
2020-03-30 14:42                         ` Ard Biesheuvel
2020-03-30 14:50                           ` Pete Batard
2020-03-30 14:19                 ` Ard Biesheuvel
2020-03-30 14:33                   ` Pete Batard
2020-03-30 14:48 ` [edk2-platforms][PATCH " Ard Biesheuvel

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-list 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='CAKv+Gu_yThBiobM=mE_PdbKUYZhM25KCNCRfVZY9SA1FYXkZdw@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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