From: Marek Vasut <marek.vasut@gmail.com>
To: "Esponde, Joel" <Joel.Esponde@Honeywell.com>,
Cyrille Pitchen <cyrille.pitchen@atmel.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v3] mtd: spi-nor: fix spansion quad enable
Date: Fri, 25 Nov 2016 17:43:29 +0100 [thread overview]
Message-ID: <d81e5625-4ab8-52cb-ea12-c891bfc84948@gmail.com> (raw)
In-Reply-To: <F6CD090A69E64C4289DC608E1C5D20242545B77C@DE08W1305.global.ds.honeywell.com>
On 11/25/2016 05:01 PM, Esponde, Joel wrote:
>> -----Message d'origine-----
>> De : Marek Vasut [mailto:marek.vasut@gmail.com]
>> Envoyé : vendredi 25 novembre 2016 16:08
>> À : Cyrille Pitchen <cyrille.pitchen@atmel.com>; Esponde, Joel
>> <Joel.Esponde@Honeywell.com>; linux-mtd@lists.infradead.org
>> Objet : Re: [PATCH v3] mtd: spi-nor: fix spansion quad enable
>>
>> On 11/25/2016 03:50 PM, Cyrille Pitchen wrote:
>>> Hi Marek,
>>
>> Hi,
>>
>>> Le 25/11/2016 à 15:17, Marek Vasut a écrit :
>>>> On 11/23/2016 12:47 PM, Joël Esponde wrote:
>>>>> With the S25FL127S nor flash part, each writing to the configuration
>>>>> register takes hundreds of ms. During that time, no more accesses
>>>>> to the flash should be done (even reads).
>>>>>
>>>>> This commit adds a wait loop after the register writing until the
>>>>> flash finishes its work.
>>>>>
>>>>> This issue could make rootfs mounting fail when the latter was done
>>>>> too much closely to this quad enable bit setting step. And in this
>>>>> case, a driver as UBIFS may try to recover the filesystem and may
>>>>> broke it completely.
>>>>
>>>> Does this apply to all spansion chips or only to selected few ?
>>>>
>>>
>>> I've recently faced the very same issue with Winbond memories, which
>>> use the same procedure as Spansion to set the Quad Enable bit.
>>> More precisely, in my case it was some bare metal (bootloader) code
>>> but the issue was the same, there was no polling of busy bit from the
>>> Status Register after having set the QE bit in the Status Register 2 /
>>> Control Register 1. Then the next SPI command came too early and
>>> failed because the memory was actually still busy.
>>>
>>> I faced this issue with Winbond W25Q256 and W25M512.
>>
>> So we can leave this code as is ?
>>
>
>
> Hi,
>
> I checked these data sheets, and in all of them, Bit 0 of the Status Register stands for WIP (Work in progress).
>
> S25FL032P http://www.cypress.com/file/196861/download#G4.1231516
> S25FL064P http://www.cypress.com/file/196856/download#G3.1231516
> S25FL127S http://www.cypress.com/file/177961/download#G3.1468489
> S25FL128S,
> S25FL256S http://www.cypress.com/file/177966/download#G3.1254282
> S25FL512S,
> S70FL01GS http://www.cypress.com/file/177971/download#G3.1238704
> S25FL129P http://www.cypress.com/file/197121/download#G4.1231516
> S25FL004K,
> S25FL008K,
> S25FL016K http://www.mouser.com/ds/2/380/spansion%20inc_s25fl004k-016k_00-329492.pdf#page=16&zoom=auto,61,683
> S25FL128K http://www.cypress.com/file/228376/download#G4.1299435
> S25FL116K,
> S25FL132K,
> S25FL164K http://www.cypress.com/file/196886/download#G3.1239521
> S25FL204K http://www.cypress.com/file/196871/download#G4.1354778
>
> I was not able to find the data sheets of S25SL parts.
> Based on this old patch provided by an Spansion engineer, it looks like S25SL family never existed:
> https://patchwork.ozlabs.org/patch/59109/
Oh great, thanks a lot for checking :-) So we can leave the code as is.
Regarding the S25SL, I found [1], but that might be a typo.
[1]
http://lxr.free-electrons.com/source/arch/powerpc/boot/dts/mpc8536ds.dts?v=3.0
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2016-11-25 16:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 13:43 [PATCH] mtd: spi-nor: fixed spansion quad enable Joël Esponde
2016-10-20 15:23 ` Cyrille Pitchen
2016-10-21 10:37 ` Esponde, Joel
2016-10-21 12:50 ` Cyrille Pitchen
2016-10-21 13:44 ` Cyrille Pitchen
2016-10-24 8:29 ` Esponde, Joel
2016-10-24 8:33 ` Esponde, Joel
2016-11-16 12:58 ` Cyrille Pitchen
2016-11-22 14:02 ` Esponde, Joel
2016-11-22 22:24 ` [PATCH v2] " Joël Esponde
2016-11-23 10:39 ` Cyrille Pitchen
2016-11-23 14:27 ` Esponde, Joel
2016-11-23 15:35 ` Marek Vasut
2016-11-23 18:21 ` Esponde, Joel
2016-11-23 11:47 ` [PATCH v3] mtd: spi-nor: fix " Joël Esponde
2016-11-23 14:35 ` Cyrille Pitchen
2016-11-25 14:17 ` Marek Vasut
2016-11-25 14:50 ` Cyrille Pitchen
2016-11-25 15:08 ` Marek Vasut
2016-11-25 16:01 ` Esponde, Joel
2016-11-25 16:43 ` Marek Vasut [this message]
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-all 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=d81e5625-4ab8-52cb-ea12-c891bfc84948@gmail.com \
--to=marek.vasut@gmail.com \
--cc=Joel.Esponde@Honeywell.com \
--cc=cyrille.pitchen@atmel.com \
--cc=linux-mtd@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).