From: Tom Fitzhenry <tom@tom-fitzhenry.me.uk>
To: Michael Walle <michael@walle.cc>
Cc: Tudor Ambarus <tudor.ambarus@microchip.com>,
Pratyush Yadav <p.yadav@ti.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Martijn Braam <martijn@brixit.nl>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: ...
Date: Sun, 29 May 2022 13:21:07 +1000 [thread overview]
Message-ID: <23811367-3180-32aa-56d6-355e679a304e@tom-fitzhenry.me.uk> (raw)
In-Reply-To: <10c2bc96821e9a907e54ef1675dc4c60@walle.cc>
On 25/5/22 08:30, Michael Walle wrote:
> Yes that would be great. Could also be one of the other
> 25h vendors, usually the continuation code is just ignored.
> I'd bet it some china SPI flash.
Physical inspection of the SPI NOR chip shows the chip is a
"SiliconKaiser SK25LP128" on it. Thanks to biktorgj[0] for finding that.
Per
https://github.com/Yatekii/jep106/commit/caa92b6f811609d49b46777fce0d1f84a3550c31,
SiliconKaiser is a vendor rename from Chingis introduced in JEP106BD, at
0x25 in bank/continuation 8.
Unfortunately I have been unable to find a datasheet for this chip.
I will add a siliconkaiser.c file with this chip "sk25lp128" using the
SNOR_ID3 API, and submit a patch once I have tested this.
It's confusing that the chip's returned JEDEC ID has no continuation
codes to reflect being in bank 8. Does this risk collisions if another
25h vendor uses the same JEDEC ID?
0. https://github.com/Biktorgj
prev parent reply other threads:[~2022-05-29 3:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 5:55 [PATCH] mtd: spi-nor: gigadevice: add support for gd25lq128e Tom Fitzhenry
2022-05-23 8:03 ` Michael Walle
2022-05-24 20:50 ` Tom Fitzhenry
2022-05-24 22:30 ` Michael Walle
2022-05-29 3:21 ` Tom Fitzhenry [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=23811367-3180-32aa-56d6-355e679a304e@tom-fitzhenry.me.uk \
--to=tom@tom-fitzhenry.me.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=martijn@brixit.nl \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--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).