From: "Rohit Mathew" <rohit.mathew@arm.com>
To: devel@edk2.groups.io
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
Sami Mujawar <sami.mujawar@arm.com>
Subject: [edk2-platforms][PATCH V1 0/2] Uart segregation patch series
Date: Wed, 9 Mar 2022 12:00:23 +0000 [thread overview]
Message-ID: <20220309120025.10754-1-rohit.mathew@arm.com> (raw)
This patch series aims at routing uart logs via different sets of uart ports,
namely secure port for secure partition logs and non-secure port for all other
logs.
The first patch deals with removing redundant DSDT descriptions. For sgi575,
a hardcoded uart base address was being used within the DSDT which hindered
migration to the required uart ports. The addition of this patch solves this
issue.
The second patch deals with the migration and grouping of uart related PCDs for
all Neoverese reference design platforms
Link to github branch with the patches in this series -
https://github.com/rohit-arm/edk2-platforms/tree/uart_segregation
Rohit Mathew (2):
Platform/Sgi: Remove redundant platform description from DSDT
Platform/Sgi: Route logs to different sets of consoles
Platform/ARM/SgiPkg/SgiMemoryMap.dsc.inc | 8 +--
Platform/ARM/SgiPkg/SgiMemoryMap2.dsc.inc | 8 +--
Platform/ARM/SgiPkg/SgiPlatform.dsc.inc | 6 +-
Platform/ARM/SgiPkg/SgiPlatformMm.dsc.inc | 3 +-
Platform/ARM/SgiPkg/PlatformStandaloneMm.dsc | 4 +-
Platform/ARM/SgiPkg/PlatformStandaloneMm2.dsc | 4 +-
Platform/ARM/SgiPkg/AcpiTables/Sgi575/Dsdt.asl | 64 --------------------
7 files changed, 12 insertions(+), 85 deletions(-)
--
2.25.1
next reply other threads:[~2022-03-09 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 12:00 Rohit Mathew [this message]
2022-03-09 12:00 ` [edk2-platforms][PATCH V1 1/2] Platform/Sgi: Remove redundant platform description from DSDT Rohit Mathew
2022-03-09 12:00 ` [edk2-platforms][PATCH V1 2/2] Platform/Sgi: Route logs to different sets of consoles Rohit Mathew
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=20220309120025.10754-1-rohit.mathew@arm.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