All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takahiro Kuwano <kuwano.takahiro@gmail.com>
To: Tudor.Ambarus@microchip.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: Tue, 7 Jul 2020 14:48:44 +0900	[thread overview]
Message-ID: <63f7d4a7-18fc-e699-10dc-9be781d5b0cb@gmail.com> (raw)
In-Reply-To: <48516fcf-70fd-dffe-96b4-39a7772eaabc@microchip.com>

On 7/3/20 9:20 PM, Tudor.Ambarus@microchip.com wrote:
> 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?

No, because the S70FS01GS does not support RDSR(05h) which is critical
for erase/write. The S70FS01GS is a dual die stack with one chip select.
Accessing to the registers requires RDAR(65h)/WRAR(71h) designating die
and register address.  

Best Regards,
Takahiro


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2020-07-07  5:53 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
2020-07-07  5:48   ` Takahiro Kuwano [this message]
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=63f7d4a7-18fc-e699-10dc-9be781d5b0cb@gmail.com \
    --to=kuwano.takahiro@gmail.com \
    --cc=Bacem.Daassi@cypress.com \
    --cc=Takahiro.Kuwano@cypress.com \
    --cc=Tudor.Ambarus@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.