From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
Graeme Gregory <graeme.gregory@linaro.org>,
Masahisa Kojima <masahisa.kojima@linaro.org>
Subject: Re: [PATCH edk2-platforms 3/3] Platform/Secure96Dxe: add ACPI description of the GPIO LEDs
Date: Fri, 26 Apr 2019 15:17:38 +0100 [thread overview]
Message-ID: <20190426141738.q4gm4s3jbrj42mib@bivouac.eciton.net> (raw)
In-Reply-To: <CAKv+Gu_RiCXBfR-ZscX38LRb6XBYwpE6LRezk5v+NabrDrJ3ug@mail.gmail.com>
On Fri, Apr 26, 2019 at 01:56:54PM +0200, Ard Biesheuvel wrote:
> On Fri, 26 Apr 2019 at 13:16, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> >
> > On Thu, Apr 25, 2019 at 02:32:54PM +0200, Ard Biesheuvel wrote:
> > > Wire up the new 96boards mezzanine SSDT loading support, and use it
> > > to describe the four GPIO LEDs on the Secure96 mezzanine board.
> > >
> > > Contributed-under: TianoCore Contribution Agreement 1.1
> > > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > > ---
> > > Platform/96Boards/Secure96Dxe/Secure96.asl | 103 ++++++++++++++++++++
> > > Platform/96Boards/Secure96Dxe/Secure96Dxe.c | 59 ++++++++++-
> > > Platform/96Boards/Secure96Dxe/Secure96Dxe.inf | 1 +
> > > 3 files changed, 158 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/Platform/96Boards/Secure96Dxe/Secure96.asl b/Platform/96Boards/Secure96Dxe/Secure96.asl
> > > new file mode 100644
> > > index 000000000000..bb9dac462a33
> > > --- /dev/null
> > > +++ b/Platform/96Boards/Secure96Dxe/Secure96.asl
> > > @@ -0,0 +1,103 @@
> > > +/** @file
> > > + * Copyright (c) 2019, Linaro Limited. All rights reserved.
> > > + *
> > > + * This program and the accompanying materials are licensed and made
> > > + * available under the terms and conditions of the BSD License which
> > > + * accompanies this distribution. The full text of the license may be
> > > + * found at http://opensource.org/licenses/bsd-license.php
> > > + *
> > > + * THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,
> > > + * WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR
> > > + * IMPLIED.
> > > + */
> > > +
> > > +#include "Secure96.h"
> > > +
> > > +DefinitionBlock ("Secure96.aml", "SSDT", 2, "LINARO", "SECURE96", 1)
> > > +{
> > > + External (\_SB.LS96.GPIO)
> > > +
> > > + Scope (_SB)
> > > + {
> > > + Device (LD96)
> > > + {
> > > + Name (_HID, "PRP0001") // _HID: Hardware ID
> > > + Name (_UID, 0x00) // _UID: Unique ID
> > > + Name (_DSD, Package () {
> > > + ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
> >
> > Surely the above stanza is the most repeated bit of boiler plate in
> > the entire tree? I count 207 instances before this goes in.
> > Can we stick a #define in some common header for this and reuse?
> > ACPI_DSD_UUID?
> >
> > As I said, not required for this patch, but would be worth addressing.
> >
>
> We should add the GUID to MdePkg, given that it occurs in the ACPI spec.
Yeah. What form would be practically consumable by .asl?
/
Leif
next prev parent reply other threads:[~2019-04-26 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 12:32 [PATCH edk2-platforms 0/3] enable Secure96 GPIO LEDs on ACPI systems Ard Biesheuvel
2019-04-25 12:32 ` [PATCH edk2-platforms 1/3] Silicon/SynQuacer: describe 96boards LS connector GPIOs via ACPI Ard Biesheuvel
2019-04-25 12:32 ` [PATCH edk2-platforms 2/3] Platform/96Boards: add ACPI support to mezzanine/LS connector driver Ard Biesheuvel
2019-04-25 12:32 ` [PATCH edk2-platforms 3/3] Platform/Secure96Dxe: add ACPI description of the GPIO LEDs Ard Biesheuvel
2019-04-26 11:16 ` Leif Lindholm
2019-04-26 11:56 ` Ard Biesheuvel
2019-04-26 14:17 ` Leif Lindholm [this message]
2019-04-26 14:18 ` Ard Biesheuvel
2019-04-26 11:10 ` [PATCH edk2-platforms 0/3] enable Secure96 GPIO LEDs on ACPI systems Leif Lindholm
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=20190426141738.q4gm4s3jbrj42mib@bivouac.eciton.net \
--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