From: Marcin Wojtas <mw@semihalf.com>
To: edk2-devel@lists.01.org
Cc: leif.lindholm@linaro.org, ard.biesheuvel@linaro.org,
nadavh@marvell.com, neta@marvell.com, kostap@marvell.com,
jinghua@marvell.com, mw@semihalf.com, jsd@semihalf.com
Subject: [platforms: PATCH 0/4] Armada 7k/8k variable support
Date: Sun, 5 Nov 2017 11:55:35 +0100 [thread overview]
Message-ID: <1509879339-10516-1-git-send-email-mw@semihalf.com> (raw)
Hi,
Basing on the latest SPI improvements, I submit the variable
support for the Marvell platforms. It relies on a memory mapped
SPI read access, configured in ARM-TF. The new driver (MvFvbDxe)
uses the Marvell SPI protocols, thanks to which it is ready to work
with different host controllers and flash devices combinations.
Patches are available in the github:
https://github.com/MarvellEmbeddedProcessors/edk2-open-platform/commits/var-upstream-r20171105
I'm looking forward to the comments or remarks.
Best regards,
Marcin
Marcin Wojtas (4):
Marvell/Drivers: MvSpiFlash: Enable using driver in RT
Marvell/Drivers: MvSpiDxe: Enable using driver in RT
Platform/Marvell: Introduce MvFvbDxe variable support driver
Marvell/Armada: Enable variables support
Platform/Marvell/Armada/Armada.dsc.inc | 25 +-
Platform/Marvell/Armada/Armada70x0.fdf | 6 +-
Platform/Marvell/Drivers/Spi/Devices/MvSpiFlash.c | 58 +-
Platform/Marvell/Drivers/Spi/Devices/MvSpiFlash.h | 1 +
Platform/Marvell/Drivers/Spi/Devices/MvSpiFlash.inf | 11 +-
Platform/Marvell/Drivers/Spi/MvSpiDxe.c | 50 +-
Platform/Marvell/Drivers/Spi/MvSpiDxe.h | 2 +
Platform/Marvell/Drivers/Spi/MvSpiDxe.inf | 9 +-
Platform/Marvell/Drivers/Spi/Variables/MvFvbDxe.c | 1049 ++++++++++++++++++++
Platform/Marvell/Drivers/Spi/Variables/MvFvbDxe.h | 114 +++
Platform/Marvell/Drivers/Spi/Variables/MvFvbDxe.inf | 91 ++
Platform/Marvell/Include/Protocol/Spi.h | 7 +
Platform/Marvell/Marvell.dec | 4 +
13 files changed, 1413 insertions(+), 14 deletions(-)
create mode 100644 Platform/Marvell/Drivers/Spi/Variables/MvFvbDxe.c
create mode 100644 Platform/Marvell/Drivers/Spi/Variables/MvFvbDxe.h
create mode 100644 Platform/Marvell/Drivers/Spi/Variables/MvFvbDxe.inf
--
2.7.4
next reply other threads:[~2017-11-05 10:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 10:55 Marcin Wojtas [this message]
2017-11-05 10:55 ` [platforms: PATCH 1/4] Marvell/Drivers: MvSpiFlash: Enable using driver in RT Marcin Wojtas
2017-11-09 13:38 ` Leif Lindholm
2017-11-05 10:55 ` [platforms: PATCH 2/4] Marvell/Drivers: MvSpiDxe: " Marcin Wojtas
2017-11-09 13:44 ` Leif Lindholm
2017-11-09 13:46 ` Marcin Wojtas
2017-11-05 10:55 ` [platforms: PATCH 3/4] Platform/Marvell: Introduce MvFvbDxe variable support driver Marcin Wojtas
2017-11-09 15:02 ` Leif Lindholm
2017-11-09 15:16 ` Marcin Wojtas
2017-11-09 15:40 ` Leif Lindholm
2017-11-09 15:48 ` Marcin Wojtas
2017-11-09 16:04 ` Leif Lindholm
2017-11-05 10:55 ` [platforms: PATCH 4/4] Marvell/Armada: Enable variables support Marcin Wojtas
2017-11-09 15:04 ` Leif Lindholm
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=1509879339-10516-1-git-send-email-mw@semihalf.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