From: <Tudor.Ambarus@microchip.com>
To: <jaimeliao.tw@gmail.com>
Cc: <u-boot@lists.denx.de>, <jagan@amarulasolutions.com>,
<vigneshr@ti.com>, <miquel.raynal@bootlin.com>,
<zhengxunli@mxic.com.tw>, <jaimeliao@mxic.com.tw>
Subject: Re: [PATCH] mtd: spi-nor: Parse SFDP Command Sequence to change to Octal DDR(8D-8D-8D) mode
Date: Wed, 16 Mar 2022 03:45:07 +0000 [thread overview]
Message-ID: <6ad18c7a-73bf-6d7c-712a-6cbc98a4e8b5@microchip.com> (raw)
In-Reply-To: <CAAQoYRmpY+uy1y2eBoWANd_1B6fxyxwF=Sc8=GJzTVT4VNYsrw@mail.gmail.com>
On 3/16/22 04:41, liao jaime wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Hi Tudor
>
>>
>> On 3/15/22 10:45, liao jaime wrote:
>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>>
>>> Hi
>>>
>>>> Hi,
>>>>
>>>> On 3/10/22 08:59, JaimeLiao wrote:
>>>>> +static int spi_nor_generall_octal_dtr_enable(struct spi_nor *nor)
>>>>
>>>> Is there a disable method too? If not, can we deduce it?
>>> Because of difference with flash vendors, I think it is hard to deduce the
>>> method "spi_nor_generall_octal_dtr_disable".
>>>>
>>
>> I've quickly skimmed through the code it seems that once octal is enabled
>> and you reset the board, the flash remains in octal mode if it doesn't
>> have a dedicated hardware reset line and the octal bit is non volatile.
>> This is bad because there might be ROMs that don't know 8d-8d-8d mode and
>> you'll break the boot sequence for them.
>
> spi_nor_soft_reset will execute at spi_nor_scan and spi_nor_remove.
> After spi_nor_soft_reset, flash will back to 1-1-1 mode.
> I think we don't need disable method for backing 1-1-1 mode.
>
True for flashes that support software reset.
prev parent reply other threads:[~2022-03-16 3:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 6:59 [PATCH] mtd: spi-nor: Parse SFDP Command Sequence to change to Octal DDR(8D-8D-8D) mode JaimeLiao
2022-03-10 9:33 ` Tudor.Ambarus
2022-03-15 8:45 ` liao jaime
2022-03-15 18:40 ` Tudor.Ambarus
2022-03-16 2:41 ` liao jaime
2022-03-16 3:45 ` Tudor.Ambarus [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=6ad18c7a-73bf-6d7c-712a-6cbc98a4e8b5@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=jagan@amarulasolutions.com \
--cc=jaimeliao.tw@gmail.com \
--cc=jaimeliao@mxic.com.tw \
--cc=miquel.raynal@bootlin.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=zhengxunli@mxic.com.tw \
/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