From: Daniel Palmer <daniel@0x0f.com>
To: linux-mtd@lists.infradead.org
Cc: vigneshr@ti.com, richard@nod.at, Daniel Palmer <daniel@0x0f.com>,
linux-kernel@vger.kernel.org, miquel.raynal@bootlin.com
Subject: [PATCH 0/1] Add basic support for Foresee SPI NAND
Date: Tue, 29 Dec 2020 14:50:58 +0900 [thread overview]
Message-ID: <20201229055059.2255021-1-daniel@0x0f.com> (raw)
This is my very crude attempt at adding support for Longsys'
Foresee branded SPI NAND parts that are showing up on some
boards.
I fully admit I have no idea what I'm doing here and I basically
took one of the existing files, ripped out what I didn't
understand and tried to fill in the numbers from the datasheet
without really knowing what they mean.
This worked well enough for me to get something that looks like
a correct dump of the SPI NAND from a board I'm working with.
I need the vendor firmware on the board for reverse engineering
so I haven't actually tried to write anything yet.
The datasheet for this chip is linked. If someone that actually
knows what they're doing could take a look and point out my
mistakes that would be great.
Link: https://datasheet.lcsc.com/szlcsc/2008121142_FORESEE-FS35ND01G-S1Y2QWFI000_C719495.pdf
Daniel Palmer (1):
mtd: spinand: add support for Foresee FS35ND01G
drivers/mtd/nand/spi/Makefile | 2 +-
drivers/mtd/nand/spi/core.c | 1 +
drivers/mtd/nand/spi/longsys.c | 45 ++++++++++++++++++++++++++++++++++
include/linux/mtd/spinand.h | 1 +
4 files changed, 48 insertions(+), 1 deletion(-)
create mode 100644 drivers/mtd/nand/spi/longsys.c
--
2.30.0.rc2
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2020-12-29 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 5:50 Daniel Palmer [this message]
2020-12-29 5:50 ` [PATCH 1/1] mtd: spinand: add support for Foresee FS35ND01G Daniel Palmer
2021-01-04 14:17 ` Miquel Raynal
2021-01-05 12:18 ` Daniel Palmer
2021-01-05 13:04 ` Miquel Raynal
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=20201229055059.2255021-1-daniel@0x0f.com \
--to=daniel@0x0f.com \
--cc=linux-kernel@vger.kernel.org \
--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