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 v2 0/4] Armada 7k/8k variable support
Date: Tue, 21 Nov 2017 07:46:17 +0100 [thread overview]
Message-ID: <1511246781-7073-1-git-send-email-mw@semihalf.com> (raw)
Hi,
I submit v2 of the Armada variable support with the style of
the MvFvbDxe driver fixed and other minor modifications. Depex
configuration was moved from 4/4 to previous patches. Details
can be found in the changelog and commit messages.
Patches are available in the github:
https://github.com/MarvellEmbeddedProcessors/edk2-open-platform/commits/var-upstream-r20171121
I'm looking forward to the comments or remarks.
Best regards,
Marcin
Changelog:
v1 -> v2:
* Change patches order in order to safely apply related Depex modifications
* 1/4:
- Fix style (line breaking, openining brackets, alignment, typos)
- Rework MvFvbSetAttributes - because it can return only EFI_SUCCESS /
EFI_INVALID_PARAMETER and should return FVB attributes,
add debug information, that operation is not supported and return
default values via MvFvbGetAttributes.
- Return EFI_SUCCESS, in case NumBytes == 0 in MvFvbRead.
* 2/4:
- Move Depex configuration from 4/4
* 3/4:
- Move Depex configuration from 4/4
- Reword and break commit message.
* 4/4:
- Remove Depex configuration
Marcin Wojtas (4):
Platform/Marvell: Introduce MvFvbDxe variable support driver
Marvell/Drivers: MvSpiFlash: Enable using driver in RT
Marvell/Drivers: MvSpiDxe: Enable using driver in RT
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 | 1056 ++++++++++++++++++++
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, 1420 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-21 6:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 6:46 Marcin Wojtas [this message]
2017-11-21 6:46 ` [platforms: PATCH v2 1/4] Platform/Marvell: Introduce MvFvbDxe variable support driver Marcin Wojtas
2017-11-25 14:09 ` Leif Lindholm
2017-11-26 13:38 ` Marcin Wojtas
2017-11-26 14:37 ` Leif Lindholm
2017-11-21 6:46 ` [platforms: PATCH v2 2/4] Marvell/Drivers: MvSpiFlash: Enable using driver in RT Marcin Wojtas
2017-11-21 6:46 ` [platforms: PATCH v2 3/4] Marvell/Drivers: MvSpiDxe: " Marcin Wojtas
2017-11-21 6:46 ` [platforms: PATCH v2 4/4] Marvell/Armada: Enable variables support Marcin Wojtas
2017-11-25 14:16 ` [platforms: PATCH v2 0/4] Armada 7k/8k variable support 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=1511246781-7073-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