public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pete Batard" <pete@akeo.ie>
To: devel@edk2.groups.io
Cc: ard.biesheuvel@linaro.org, leif.lindholm@linaro.org,
	philmd@redhat.com, samer.el-haj-mahmoud@arm.com,
	andrey.warkentin@gmail.com
Subject: [edk2-platforms][PATCH 0/5] Further RPi4 support groundwork
Date: Wed, 27 Nov 2019 12:37:01 +0000	[thread overview]
Message-ID: <20191127123706.4604-1-pete@akeo.ie> (raw)

This series mostly focuses on adding fixes, that are not directly relevant
for the Pi 3 platform but that are going to be needed for the Pi 4.

The first one of these relates to the Random Number Generator, that
seems to require a new FIFO mode for readout of data on the Pi4/Bcm2711.

The second has to do with some SD SCR read failures that were observed
during RPi4 testing and for which we add a workaround.

Finally, we use this series to add the config behaviour we eventually
require for SD routing, so that both Pi 3 and Pi 4 platforms can be
handled by the same driver.

Andrei Warkentin (2):
  Platform/RPi/MmcDxe: Factorize SCR call and clean up MMC init
  Platform/RPi/MmcDxe: Improve MMC driver stability

Pete Batard (2):
  Silicon/Bcm283x: Clean up Bcm2836.h header
  Silicon/Bcm283x: Add FIFO mode for RNG

Samer El-Haj-Mahmoud (1):
  Platform/RPi: Set SD routing according to model

 Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c          | 137 ++++++++++++++------
 Platform/RaspberryPi/Drivers/MmcDxe/Mmc.c                   |   7 +-
 Platform/RaspberryPi/Drivers/MmcDxe/MmcIdentification.c     | 105 +++++++++------
 Silicon/Broadcom/Bcm283x/Bcm283x.dec                        |   1 +
 Silicon/Broadcom/Bcm283x/Drivers/RngDxe/RngDxe.c            |  96 ++++++++++----
 Silicon/Broadcom/Bcm283x/Drivers/RngDxe/RngDxe.inf          |   2 +
 Silicon/Broadcom/Bcm283x/Include/IndustryStandard/Bcm2836.h |  23 ++--
 7 files changed, 252 insertions(+), 119 deletions(-)

-- 
2.21.0.windows.1


             reply	other threads:[~2019-11-27 12:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 12:37 Pete Batard [this message]
2019-11-27 12:37 ` [edk2-platforms][PATCH 1/5] Silicon/Bcm283x: Clean up Bcm2836.h header Pete Batard
2019-11-27 12:48   ` Ard Biesheuvel
2019-11-27 12:56     ` Pete Batard
2019-11-27 13:00       ` Ard Biesheuvel
2019-11-27 13:09         ` Pete Batard
2019-11-27 13:17           ` Ard Biesheuvel
2019-11-27 13:21             ` Pete Batard
2019-11-27 14:47   ` Philippe Mathieu-Daudé
2019-11-27 14:59     ` [edk2-devel] " Pete Batard
2019-11-27 15:18       ` Philippe Mathieu-Daudé
2019-11-27 12:37 ` [edk2-platforms][PATCH 2/5] Silicon/Bcm283x: Add FIFO mode for RNG Pete Batard
2019-11-27 12:44   ` Ard Biesheuvel
2019-11-27 12:47     ` Pete Batard
2019-11-27 12:37 ` [edk2-platforms][PATCH 3/5] Platform/RPi/MmcDxe: Factorize SCR call and clean up MMC init Pete Batard
2019-11-27 12:37 ` [edk2-platforms][PATCH 4/5] Platform/RPi/MmcDxe: Improve MMC driver stability Pete Batard
2019-11-27 12:37 ` [edk2-platforms][PATCH 5/5] Platform/RPi: Set SD routing according to model Pete Batard
2019-11-27 15:24   ` Philippe Mathieu-Daudé
2019-11-27 16:33     ` Pete Batard
2019-11-27 17:04       ` Leif Lindholm
2019-11-27 17:17         ` Philippe Mathieu-Daudé

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=20191127123706.4604-1-pete@akeo.ie \
    --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