public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: lintonrjeremy@gmail.com
To: devel@edk2.groups.io
Cc: pete@akeo.ie, ardb+tianocore@kernel.org, leif@nuviainc.com,
	awarkentin@vmware.com, Sunny.Wang@arm.com,
	samer.el-haj-mahmoud@arm.com,
	Jeremy Linton <lintonrjeremy@gmail.com>
Subject: [PATCH 0/4] Platform/RaspberryPi: new GPIO and DT menu items
Date: Thu, 11 Nov 2021 00:57:37 -0600	[thread overview]
Message-ID: <20211111065742.8923-1-lintonrjeremy@gmail.com> (raw)

Its been reported that some kernel versions still need the XHCI reload
while others only work if the reload isn't present. Lets give the user
the ability to control that for DT systems.

Further, there is now an example persistent variable store implementation
that uses the on-board SPI flash rather than trying to rewrite the UEFI
firmware image on SD/etc late in the boot cycle. The problem is that
we now need to control the GPIO pin mux. This isn't a problem for
Linux as such, because it only messes with the pin mux under DT, but
windows has some drivers which export the GPIO devices using the
ACPI definition. Lets add a menu item to enable the GPIO and default
it to off on the RPi4 under the assumption that we can't fix a GPIO
pin mux war reliably and instead will simply revert to a mode that
fails to persist variables written while the OS is active if the
GPIO is enabled.

This set also cleans up the ACPI/DT visiblity of a couple
nearby menu items as well.

Jeremy Linton (4):
  Platform/RaspberryPi: Cleanup menu visibility
  Platform/RaspberryPi: Give the user control over the XHCI mailbox
  Platform/RaspberryPi: Move GPIO/SPI/I2C to SSDT
  Platform/RaspberryPi: Add menu item to enable/disable GPIO

 Platform/RaspberryPi/AcpiTables/AcpiTables.inf     |   1 +
 Platform/RaspberryPi/AcpiTables/Dsdt.asl           |   7 -
 Platform/RaspberryPi/AcpiTables/GpuDevs.asl        | 125 ----------------
 Platform/RaspberryPi/AcpiTables/SsdtGpio.asl       | 157 +++++++++++++++++++++
 Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c |  31 ++++
 .../RaspberryPi/Drivers/ConfigDxe/ConfigDxe.inf    |   2 +
 .../RaspberryPi/Drivers/ConfigDxe/ConfigDxeHii.uni |  10 ++
 .../RaspberryPi/Drivers/ConfigDxe/ConfigDxeHii.vfr |  36 ++++-
 Platform/RaspberryPi/Drivers/FdtDxe/FdtDxe.c       |   4 +
 Platform/RaspberryPi/Drivers/FdtDxe/FdtDxe.inf     |   1 +
 Platform/RaspberryPi/Include/ConfigVars.h          |   4 +
 Platform/RaspberryPi/RPi3/RPi3.dsc                 |  12 ++
 Platform/RaspberryPi/RPi4/RPi4.dsc                 |  14 ++
 Platform/RaspberryPi/RaspberryPi.dec               |   2 +
 14 files changed, 271 insertions(+), 135 deletions(-)
 create mode 100644 Platform/RaspberryPi/AcpiTables/SsdtGpio.asl

-- 
2.13.7


             reply	other threads:[~2021-11-11  6:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11  6:57 lintonrjeremy [this message]
2021-11-11  6:57 ` [PATCH 1/1] Platform/RaspberryPi: Add menu item to enable/disable GPIO Jeremy Linton
2021-11-11  6:57 ` [PATCH 1/4] Platform/RaspberryPi: Cleanup menu visibility Jeremy Linton
2021-11-11  6:57 ` [PATCH 2/4] Platform/RaspberryPi: Give the user control over the XHCI mailbox Jeremy Linton
2021-11-11  6:57 ` [PATCH 3/4] Platform/RaspberryPi: Move GPIO/SPI/I2C to SSDT Jeremy Linton
2021-11-11  6:57 ` [PATCH 4/4] Platform/RaspberryPi: Add menu item to enable/disable GPIO Jeremy Linton

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=20211111065742.8923-1-lintonrjeremy@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