From: <Tudor.Ambarus@microchip.com>
To: <kuwano.takahiro@gmail.com>, <linux-mtd@lists.infradead.org>
Cc: richard@nod.at, Takahiro.Kuwano@cypress.com,
Bacem.Daassi@cypress.com, vigneshr@ti.com,
miquel.raynal@bootlin.com
Subject: Re: [PATCH] mtd: spi-nor: spansion: Remove s70fl01gs from flash_info
Date: Fri, 3 Jul 2020 12:20:24 +0000 [thread overview]
Message-ID: <48516fcf-70fd-dffe-96b4-39a7772eaabc@microchip.com> (raw)
In-Reply-To: <20200626051650.495-1-Takahiro.Kuwano@cypress.com>
On 6/26/20 8:16 AM, kuwano.takahiro@gmail.com wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> From: Takahiro Kuwano <Takahiro.Kuwano@cypress.com>
>
> The s70fl01gs is a dual die stack of two s25fl512s die with dedicated chip
> select pins to each. Tested with the device and confirmed that is working
> as two s25fl512s devices. The current device ID in the flash_info table
Right, the datasheet specifies too that the S70FS01GS device is a dual die
stack of two FS512S die.
> matches with s70fs01gs which does not work with current MTD.
s70fs01gs is not correctly supported indeed, but the lower half of it
(first s25fl512s die) should work. Can't you correctly read/erase/write
on the lower half of the s70fs01gs flash with the current code?
Cheers,
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-07-03 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 5:16 [PATCH] mtd: spi-nor: spansion: Remove s70fl01gs from flash_info kuwano.takahiro
2020-07-03 12:20 ` Tudor.Ambarus [this message]
2020-07-07 5:48 ` Takahiro Kuwano
2020-07-13 9:26 ` Tudor Ambarus
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=48516fcf-70fd-dffe-96b4-39a7772eaabc@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Bacem.Daassi@cypress.com \
--cc=Takahiro.Kuwano@cypress.com \
--cc=kuwano.takahiro@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).