[PATCH] Clean up the Spansion/Cypress/Infineon device ID table

[Bacem Daassi]

The device s25fl512s is not offered with neither 64kB sector size, nor 512kB sector size,
that's why s25fl512s_64k and s25fl512s_512k need to be removed from the device ID table.

The device ID entries "s25fl512s_256k" and "s25fl512s" are exactly the same, that's why the
entry "s25fl512s_256k" needs to be removed. Any legacy board having that device will still be able to
probe the Flash memory as "s25fl512s" and will definitely not fail.

Best regards,
Bacem Daassi
Principal Applications Engineer

Cypress Semiconductor GmbH
An Infineon Technologies Company
Willy-Brandt-Allee 4, 81829 Munich, Germany
www.infineon.com   www.cypress.com

-----Original Message-----
From: Jagan Teki <jagan at amarulasolutions.com>
Sent: Thursday, July 9, 2020 10:19 AM
To: bacem.daassi at gmail.com
Cc: U-Boot-Denx <u-boot at lists.denx.de>; Vignesh R <vigneshr at ti.com>; Bacem Daassi <Bacem.Daassi at cypress.com>; Takahiro Kuwano <Takahiro.Kuwano at cypress.com>
Subject: Re: [PATCH] Clean up the Spansion/Cypress/Infineon device ID table

On Fri, May 22, 2020 at 10:41 PM <bacem.daassi at gmail.com> wrote:
>
> From: Bacem Daassi <Bacem.Daassi at cypress.com>
>
> Signed-off-by: Bacem Daassi <Bacem.Daassi at cypress.com>
>
> Clean up the Spansion/Cypress/Infineon device ID table.
>    Remove s25fl512s_256k since it's a duplicate of s25fl512s.
>    Remove s25fl512s_64k and s25fl512s_512k since these devices do not exist.

Why these removed, what if legacy board usage still exists?

>    Rename s25fl128s to s25fl128s1.
>    Add the new device s25fl128s0.
>    Add device s25fl256l to the device ID table.
> All devices were tested on real silicon and confirmed to be working.
> ---

Please work with a proper commit message.

mtd: spi: Clean up Spansion/Cypress/Infineon ID table

< body >

Signed-off-by: Bacem Daassi <Bacem.Daassi at cypress.com>

This message and any attachments may contain confidential information from Cypress or its subsidiaries. If it has been received in error, please advise the sender and immediately delete this message.