public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Joey Gouly" <joey.gouly@arm.com>
To: <devel@edk2.groups.io>
Cc: <joey.gouly@arm.com>, <ardb+tianocore@kernel.org>,
	<sami.mujawar@arm.com>, <jbrasen@nvidia.com>, <ipark@nvidia.com>,
	<Samer.El-Haj-Mahmoud@arm.com>, <nd@arm.com>
Subject: [PATCH v2 0/2] Add a Pcd to override the 16650 HID in SSDT
Date: Fri, 22 Jan 2021 12:51:10 +0000	[thread overview]
Message-ID: <20210122125112.4705-1-joey.gouly@arm.com> (raw)

This series adds PcdNonSbsaCompliantSerialHid so that firmware can
override the PNP0501 HID used by 16550 UART in the SSDT table, in case
they are not compatible with the generic PNP0501 HID.

I have tested this with acpiview, some extra testing would be
appreciated.

Changes available at https://github.com/jgouly/edk2/tree/1588_non_sbsa_hid_v2

v2:
  - Renamed PcdNonSbsaCompliantSerialHid to PcdNonBsaCompliant16550SerialHid

Joey Gouly (2):
  DynamicTablesPkg: Don't use gEfiMdeModulePkgTokenSpaceGuid
  DynamicTablesPkg: Add an override for 16550 HID in SSDT

 DynamicTablesPkg/DynamicTablesPkg.dec              | 13 +++++++++----
 .../DynamicTableFactoryDxe.inf                     |  8 ++++----
 .../SsdtSerialPortFixupLib.inf                     |  4 +++-
 .../SsdtSerialPortFixupLib.c                       | 14 +++++++++++---
 4 files changed, 27 insertions(+), 12 deletions(-)

-- 
Guid("CE165669-3EF3-493F-B85D-6190EE5B9759")


             reply	other threads:[~2021-01-22 12:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 12:51 Joey Gouly [this message]
2021-01-22 12:51 ` [PATCH v2 1/2] DynamicTablesPkg: Don't use gEfiMdeModulePkgTokenSpaceGuid Joey Gouly
2021-02-02 13:00   ` [edk2-devel] " Alexei Fedorov
2021-01-22 12:51 ` [PATCH v2 2/2] DynamicTablesPkg: Add an override for 16550 HID in SSDT Joey Gouly
2021-02-02 13:01   ` [edk2-devel] " Alexei Fedorov
2021-02-02 13:00 ` [edk2-devel] [PATCH v2 0/2] Add a Pcd to override the 16650 " Alexei Fedorov

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=20210122125112.4705-1-joey.gouly@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