From: Takahiro Kuwano <tkuw584924@gmail.com>
To: Michael Walle <michael@walle.cc>
Cc: Tudor.Ambarus@microchip.com, Takahiro.Kuwano@infineon.com,
juliensu@mxic.com.tw, jaimeliao@mxic.com.tw,
Bacem.Daassi@infineon.com, beanhuo@micron.com,
shiva.linuxworks@gmail.com, sshivamurthy@micron.com,
p.yadav@ti.com, linux-mtd@lists.infradead.org
Subject: Re: How does an SPI NOR handle a single byte write in Octal DTR mode?
Date: Wed, 22 Dec 2021 08:32:05 +0900 [thread overview]
Message-ID: <5c38b7ce-cf34-ec62-bdbd-56ee7a50e16a@gmail.com> (raw)
In-Reply-To: <a7bd7dc6db2cb9f74aa6e7737e888625@walle.cc>
Hi,
I need to correct my previous statement.
On 12/21/2021 12:47 AM, Michael Walle wrote:
> Hi,
>
> Am 2021-12-20 11:32, schrieb Takahiro Kuwano:
>> In case of Infineon(Cypress) S28 devices, it can be done by de-asserting
>> chip select before clock falling (not sure typical controllers support this).
This is true for single-byte register write op.
>> That means the device can take odd address in 8D-8D-8D mode.
For page program op, the S28 in 8D-8D-8D mode only supports programming
multiples of 2-bytes and the address must start at an even address.
>
> Ahh nice. FWIW, I had a quick look at the FlexSPI controller found on
> the NXP LS1028A, it doesn't seem to support deasserting the CS after
> half a clock cycle, though.
>
> -michael
Thanks,
Takahiro
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2021-12-21 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 9:36 How does an SPI NOR handle a single byte write in Octal DTR mode? Tudor.Ambarus
2021-12-20 10:32 ` Takahiro Kuwano
2021-12-20 15:47 ` Michael Walle
2021-12-21 23:32 ` Takahiro Kuwano [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=5c38b7ce-cf34-ec62-bdbd-56ee7a50e16a@gmail.com \
--to=tkuw584924@gmail.com \
--cc=Bacem.Daassi@infineon.com \
--cc=Takahiro.Kuwano@infineon.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=beanhuo@micron.com \
--cc=jaimeliao@mxic.com.tw \
--cc=juliensu@mxic.com.tw \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=p.yadav@ti.com \
--cc=shiva.linuxworks@gmail.com \
--cc=sshivamurthy@micron.com \
/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