From: <Tudor.Ambarus@microchip.com>
To: <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>
Cc: <michael@walle.cc>, <p.yadav@ti.com>, <linux-mtd@lists.infradead.org>
Subject: How does an SPI NOR handle a single byte write in Octal DTR mode?
Date: Mon, 20 Dec 2021 09:36:05 +0000 [thread overview]
Message-ID: <f593ded7-6cb1-7645-a0b4-dc20b5576d1d@microchip.com> (raw)
Hello,
We're trying to understand how flashes handle single byte writes in
Octal DTR mode, and since we haven't found this info in the datasheets
that we read, you're our only hope. Can you shed some light and let us
now:
1/ Do the flashes ignore the second byte in Octal DTR mode? Are we forced
to first read the byte that we want to update together with the second byte,
so that when writing in Octal DTR mode to write the 2nd byte that we've just
read, so that we don't change its value?
2/ Can reads or writes start at an odd address in 8D-8D-8D mode? Pratyush
proposed something at:
https://patchwork.ozlabs.org/project/linux-mtd/list/?series=246518
Are the assumptions correct in the patch set?
Feel free to forward this to anyone interested. Thanks.
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2021-12-20 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 9:36 Tudor.Ambarus [this message]
2021-12-20 10:32 ` How does an SPI NOR handle a single byte write in Octal DTR mode? Takahiro Kuwano
2021-12-20 15:47 ` Michael Walle
2021-12-21 23:32 ` Takahiro Kuwano
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=f593ded7-6cb1-7645-a0b4-dc20b5576d1d@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Bacem.Daassi@infineon.com \
--cc=Takahiro.Kuwano@infineon.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