From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: devel@edk2.groups.io
Cc: leif.lindholm@linaro.org, graeme.gregory@linaro.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [PATCH edk2-platforms v2 0/2] enable Secure96 mezzanine on ACPI systems
Date: Thu, 2 May 2019 11:58:52 +0200 [thread overview]
Message-ID: <20190502095854.6989-1-ard.biesheuvel@linaro.org> (raw)
This series plumbs in the support for describing 96boards mezzanines
via ACPI, and uses it to add a description of the Secure96. Note that
the TPM is still missing at the moment, but the I2C crypto accelerators
and the GPIO LEDs are covered.
Changes since v1:
- Don't rely on a ACPI device in the host platform's namespace to describe
the GPIO lines - this prevents the mezzanine from using GPIOs as interrupts,
and is generally far too restrictive. Since we need a hack (see below) for
I2C anyway, just use the same method for the GPIO controller.
- I2C resources are described with a reference to the I2C controller via a
string argument, which cannot be parameterized using PCDs like we do with
GPIO interrupt numbers. (This is due to the fact that string PCDs are not
expanded to true string literals by EDK2's AutoGen.h CPP magic). So add the
default names (e.g., \_SB.I2C0) to Secure96.h, and permit a platform to
override them if necessary by setting a scoped build option with a -D
argument.
Ard Biesheuvel (2):
Platform/96Boards: add ACPI support to mezzanine/LS connector driver
Platform/Secure96Dxe: add ACPI description of the LEDs and I2C
peripherals
Platform/96Boards/Include/Protocol/Mezzanine.h | 21 ++++
Platform/96Boards/LsConnectorDxe/LsConnectorDxe.c | 35 ++++--
Platform/96Boards/LsConnectorDxe/LsConnectorDxe.inf | 1 +
Platform/96Boards/Secure96Dxe/Secure96.asl | 116 ++++++++++++++++++++
Platform/96Boards/Secure96Dxe/Secure96.h | 8 ++
Platform/96Boards/Secure96Dxe/Secure96Dxe.c | 59 +++++++++-
Platform/96Boards/Secure96Dxe/Secure96Dxe.inf | 1 +
7 files changed, 225 insertions(+), 16 deletions(-)
create mode 100644 Platform/96Boards/Secure96Dxe/Secure96.asl
--
2.20.1
next reply other threads:[~2019-05-02 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 9:58 Ard Biesheuvel [this message]
2019-05-02 9:58 ` [PATCH edk2-platforms v2 1/2] Platform/96Boards: add ACPI support to mezzanine/LS connector driver Ard Biesheuvel
2019-05-02 9:58 ` [PATCH edk2-platforms v2 2/2] Platform/Secure96Dxe: add ACPI description of the LEDs and I2C peripherals Ard Biesheuvel
2019-05-02 15:40 ` [PATCH edk2-platforms v2 0/2] enable Secure96 mezzanine on ACPI systems Leif Lindholm
2019-05-03 14:06 ` 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=20190502095854.6989-1-ard.biesheuvel@linaro.org \
--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