From: Sagar Shrikant Kadam <sagar.kadam@sifive.com>
To: marek.vasut@gmail.com, tudor.ambarus@microchip.com,
dwmw2@infradead.org, computersforpeace@gmail.com,
bbrezillon@kernel.org, richard@nod.at
Cc: palmer@sifive.com, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org,
Sagar Shrikant Kadam <sagar.kadam@sifive.com>,
paul.walmsley@sifive.com, linux-riscv@lists.infradead.org
Subject: [PATCH v2 0/3] add support for is25wp256 spi-nor device.
Date: Sun, 28 Apr 2019 23:39:13 +0530 [thread overview]
Message-ID: <1556474956-27786-1-git-send-email-sagar.kadam@sifive.com> (raw)
The patch set is tested on HiFive Unleashed board and is based on mainline
kernel v 5.1-rc5. Its intended to add support for 32 MB spi-nor flash
mounted on the board. Memory Device supports 4/32/and 64 KB sectors size.
The device id table is updated accordingly.
Flash parameter table for ISSI device is set to use macronix_quad_enable
procedure to set the QE (quad-enable) bit of Status register.
With issi_lock and unlock schemes support for block protection is added
in patch 2 and 3.
These patches are extended from base work done in a patch at following commit:
https://github.com/riscv/riscv-linux/commit/c94e267766d62bc9a669611c3d0c8ed5ea26569b
Erase/Read/Write operations are verified on HiFive Unleashed board using mtd and flash utils (v1.5.2):
1. mtd_debug :Options available are : erase/read/write.
2. flashcp :Single utility that erases flash, writes a file to flash and verifies the data back.
3. flash_lock :Lock flash memory blocks.
4. flash_unlock: Unlock flash memory blocks.
Unlock scheme clears the bit protection bits of all blocks in the Status register.
Lock schemes in patch 3 is based on stm_lock mechanism. With current implementation entire flash memory
gets protected.
Block protection schemes are tested with flash_lock and unlock utils.
Revision history:
V1<-> V2:
-Incorporated changes suggested by reviewers regarding patch/cover letter versioning, references of patch.
-Updated cover letter with description for flash operations verified with these changes.
-Add support for unlocking is25xxxxxx device
-Add support for locking is25xxxxxx device.
v1:
-Add support for is25wp256 device.
Sagar Shrikant Kadam (3):
mtd: spi-nor: add support for is25wp256
mtd: spi-nor: add support to unlock flash device.
mtd: spi-nor: add locking support for is25xxxxx device
drivers/mtd/spi-nor/spi-nor.c | 116 +++++++++++++++++++++++++++++++++++++++++-
include/linux/mtd/spi-nor.h | 2 +
2 files changed, 117 insertions(+), 1 deletion(-)
--
1.9.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2019-04-28 18:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 18:09 Sagar Shrikant Kadam [this message]
2019-04-28 18:09 ` [PATCH v2 1/3] mtd: spi-nor: add support for is25wp256 Sagar Shrikant Kadam
2019-04-30 17:03 ` Paul Walmsley
2019-05-02 9:50 ` Sagar Kadam
2019-04-28 18:09 ` [PATCH v2 2/3] mtd: spi-nor: add support to unlock flash device Sagar Shrikant Kadam
2019-04-30 17:19 ` Paul Walmsley
2019-05-02 9:56 ` Sagar Kadam
2019-04-28 18:09 ` [PATCH v2 3/3] mtd: spi-nor: add locking support for is25xxxxx device Sagar Shrikant Kadam
2019-04-30 17:13 ` Paul Walmsley
2019-04-30 17:19 ` Paul Walmsley
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=1556474956-27786-1-git-send-email-sagar.kadam@sifive.com \
--to=sagar.kadam@sifive.com \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.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).