From: Marcin Wojtas <mw@semihalf.com>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
nadavh@marvell.com, Neta Zur Hershkovits <neta@marvell.com>,
Kostya Porotchkin <kostap@marvell.com>,
Hua Jing <jinghua@marvell.com>, Alexander Graf <agraf@suse.de>,
semihalf-dabros-jan <jsd@semihalf.com>
Subject: Re: [platforms: PATCH 09/11] Drivers/Spi/Devices/MvSpiFlash: Fix usage of erase size parameter
Date: Fri, 1 Sep 2017 17:25:00 +0200 [thread overview]
Message-ID: <CAPv3WKd1d+Rh8GwpDb8Pb3Z8k=r8xqiUvS+k3-Eefs9WxNnyLQ@mail.gmail.com> (raw)
In-Reply-To: <20170901152144.mo5q4nabvqgbqic6@bivouac.eciton.net>
2017-09-01 17:21 GMT+02:00 Leif Lindholm <leif.lindholm@linaro.org>:
> On Fri, Sep 01, 2017 at 03:08:21PM +0200, Marcin Wojtas wrote:
>> Although, hitherto support allowed for using configurable EraseSize,
>> the erase command was fixed to CMD_ERASE_64K. Also it was
>> assumed that EraseSize equals SectorSize, which is not true
>> for some flash devices.
>
> Another thing I immediately wish I had never learned.
> Thanks :/
Do you mean the code or flash quirks? :)
>
>> Fix both issues by adding new PCD
>> (gMarvellTokenSpaceGuid.PcdSpiFlashPageSize) and using
>> this parameter properly in MvSpiFlashUpdate routine instead
>> of the EraseSize. Also erase command is adjusted to the settings.
>> Update PortingGuide accordingly.
>>
>> Contributed-under: TianoCore Contribution Agreement 1.1
>> Signed-off-by: Marcin Wojtas <mw@semihalf.com>
>> ---
>> Platform/Marvell/Documentation/PortingGuide.txt | 3 +++
>> Platform/Marvell/Drivers/Spi/Devices/MvSpiFlash.c | 26 +++++++++++++++++-----
>> Platform/Marvell/Drivers/Spi/Devices/MvSpiFlash.h | 6 +++++
>> .../Marvell/Drivers/Spi/Devices/MvSpiFlash.inf | 1 +
>> Platform/Marvell/Marvell.dec | 1 +
>> 5 files changed, 31 insertions(+), 6 deletions(-)
>>
>> diff --git a/Platform/Marvell/Documentation/PortingGuide.txt b/Platform/Marvell/Documentation/PortingGuide.txt
>> index 3b79bd2..f637fee 100644
>> --- a/Platform/Marvell/Documentation/PortingGuide.txt
>> +++ b/Platform/Marvell/Documentation/PortingGuide.txt
>> @@ -297,6 +297,9 @@ Folowing PCDs for spi flash driver configuration must be set properly:
>> - gMarvellTokenSpaceGuid.PcdSpiFlashPageSize
>> (Size of SPI flash page)
>>
>> + - gMarvellTokenSpaceGuid.PcdSpiFlashSectorSize
>> + (Size of SPI flash sector, 65536 bytes by default)
>> +
>> - gMarvellTokenSpaceGuid.PcdSpiFlashId
>> (Id of SPI flash)
>>
>> diff --git a/Platform/Marvell/Drivers/Spi/Devices/MvSpiFlash.c b/Platform/Marvell/Drivers/Spi/Devices/MvSpiFlash.c
>> index 9a04493..f3fdba4 100755
>> --- a/Platform/Marvell/Drivers/Spi/Devices/MvSpiFlash.c
>> +++ b/Platform/Marvell/Drivers/Spi/Devices/MvSpiFlash.c
>> @@ -191,7 +191,21 @@ MvSpiFlashErase (
>> return EFI_DEVICE_ERROR;
>> }
>>
>> - Cmd[0] = CMD_ERASE_64K;
>> + switch (EraseSize) {
>> + case SPI_ERASE_SIZE_4K:
>> + Cmd[0] = CMD_ERASE_4K;
>> + break;
>> + case SPI_ERASE_SIZE_32K:
>> + Cmd[0] = CMD_ERASE_32K;
>> + break;
>> + case SPI_ERASE_SIZE_64K:
>> + Cmd[0] = CMD_ERASE_64K;
>> + break;
>> + default:
>> + DEBUG ((DEBUG_ERROR, "MvSpiFlash: Invalid EraseSize parameter\n"));
>> + return EFI_INVALID_PARAMETER;
>> + }
>> +
>> while (Length) {
>> EraseAddr = Offset;
>>
>> @@ -353,14 +367,14 @@ MvSpiFlashUpdate (
>> )
>> {
>> EFI_STATUS Status;
>> - UINT64 EraseSize, ToUpdate, Scale = 1;
>> + UINT64 SectorSize, ToUpdate, Scale = 1;
>> UINT8 *TmpBuf, *End;
>>
>> - EraseSize = PcdGet64 (PcdSpiFlashEraseSize);
>> + SectorSize = PcdGet64 (PcdSpiFlashSectorSize);
>>
>> End = Buf + ByteCount;
>>
>> - TmpBuf = (UINT8 *)AllocateZeroPool (EraseSize);
>> + TmpBuf = (UINT8 *)AllocateZeroPool (SectorSize);
>> if (TmpBuf == NULL) {
>> DEBUG((DEBUG_ERROR, "SpiFlash: Cannot allocate memory\n"));
>> return EFI_OUT_OF_RESOURCES;
>> @@ -370,9 +384,9 @@ MvSpiFlashUpdate (
>> Scale = (End - Buf) / 100;
>>
>> for (; Buf < End; Buf += ToUpdate, Offset += ToUpdate) {
>> - ToUpdate = MIN((UINT64)(End - Buf), EraseSize);
>> + ToUpdate = MIN((UINT64)(End - Buf), SectorSize);
>> Print (L" \rUpdating, %d%%", 100 - (End - Buf) / Scale);
>> - Status = MvSpiFlashUpdateBlock (Slave, Offset, ToUpdate, Buf, TmpBuf, EraseSize);
>> + Status = MvSpiFlashUpdateBlock (Slave, Offset, ToUpdate, Buf, TmpBuf, SectorSize);
>>
>> if (EFI_ERROR (Status)) {
>> DEBUG((DEBUG_ERROR, "SpiFlash: Error while updating\n"));
>> diff --git a/Platform/Marvell/Drivers/Spi/Devices/MvSpiFlash.h b/Platform/Marvell/Drivers/Spi/Devices/MvSpiFlash.h
>> index 3889643..646598a 100755
>> --- a/Platform/Marvell/Drivers/Spi/Devices/MvSpiFlash.h
>> +++ b/Platform/Marvell/Drivers/Spi/Devices/MvSpiFlash.h
>> @@ -57,6 +57,8 @@ SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>> #define CMD_READ_ARRAY_FAST 0x0b
>> #define CMD_PAGE_PROGRAM 0x02
>> #define CMD_BANK_WRITE 0xc5
>> +#define CMD_ERASE_4K 0x20
>> +#define CMD_ERASE_32K 0x52
>> #define CMD_ERASE_64K 0xd8
>> #define CMD_4B_ADDR_ENABLE 0xb7
>>
>> @@ -66,6 +68,10 @@ SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>> #define SPI_TRANSFER_BEGIN 0x01 // Assert CS before transfer
>> #define SPI_TRANSFER_END 0x02 // Deassert CS after transfers
>>
>> +#define SPI_ERASE_SIZE_4K 4096
>> +#define SPI_ERASE_SIZE_32K 32768
>> +#define SPI_ERASE_SIZE_64K 65536
>> +
>
> Maybe just replace these with SIZE_4KB, SIZE_32KB and SIZE_64KB?
>
Sure, will do.
Marcin
next prev parent reply other threads:[~2017-09-01 15:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 13:08 [platforms: PATCH 00/11] Armada 70x0/80x0 SPI improvements Marcin Wojtas
2017-09-01 13:08 ` [platforms: PATCH 01/11] Platform/Marvell/Documentation: Refactor PortingGuide Marcin Wojtas
2017-09-01 14:36 ` Leif Lindholm
2017-09-01 15:08 ` Marcin Wojtas
2017-09-01 15:45 ` Leif Lindholm
2017-09-01 15:56 ` Marcin Wojtas
2017-09-01 13:08 ` [platforms: PATCH 02/11] Drivers/Spi/MvSpiDxe: Log and return correct error Marcin Wojtas
2017-09-01 14:05 ` Ard Biesheuvel
2017-09-01 13:08 ` [platforms: PATCH 03/11] Drivers/Spi/MvSpiDxe: Fix write bug Marcin Wojtas
2017-09-01 14:44 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 04/11] Applications/SpiTool: Enable configurable CS and SCLK mode Marcin Wojtas
2017-09-01 14:47 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 05/11] Platform/Marvell/Armada70x0: set CS and SCLK Mode for SPI flash Marcin Wojtas
2017-09-01 14:48 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 06/11] Applications/SpiTool: Fix bug in error test Marcin Wojtas
2017-09-01 14:48 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 07/11] Applications/FirmwareUpdate: Fix 32-bit issues Marcin Wojtas
2017-09-01 14:54 ` Leif Lindholm
2017-09-01 15:16 ` Ard Biesheuvel
2017-09-01 15:51 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 08/11] Applications/SpiTool: " Marcin Wojtas
2017-09-01 14:56 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 09/11] Drivers/Spi/Devices/MvSpiFlash: Fix usage of erase size parameter Marcin Wojtas
2017-09-01 15:21 ` Leif Lindholm
2017-09-01 15:25 ` Marcin Wojtas [this message]
2017-09-01 15:51 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 10/11] Drivers/Spi/Devices/MvSpiFlash: Enable dynamic SPI Flash detection Marcin Wojtas
2017-09-01 15:33 ` Leif Lindholm
2017-09-01 17:20 ` Marcin Wojtas
2017-09-01 22:03 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 11/11] Drivers/Spi/Devices/MvSpiFlash: Fix bank selection for Spansion Marcin Wojtas
2017-09-01 15:34 ` 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='CAPv3WKd1d+Rh8GwpDb8Pb3Z8k=r8xqiUvS+k3-Eefs9WxNnyLQ@mail.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