From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5 1/2] SPI Flash: add support of sst26wf* flash ICs protection ops
Date: Mon, 16 Apr 2018 13:52:48 +0000 [thread overview]
Message-ID: <1523886767.17585.1.camel@synopsys.com> (raw)
In-Reply-To: <20180410114045.22121-2-Eugeniy.Paltsev@synopsys.com>
Hi Jagan!
Any comments?
On Tue, 2018-04-10 at 14:40 +0300, Eugeniy Paltsev wrote:
> sst26wf flash series block protection implementation differs
> from other SST series, so add specific implementation
> flash_lock/flash_unlock/flash_is_locked functions for sst26wf
> flash ICs.
>
> Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
> ---
> Changes v4->v5:
> * Return EACCES when flash is locked instead of custom define (SF_LOCKED)
> * Add SST26_CTL_* prefix to sst27 lock ops enum.
> * Move all sst26 code inside of existing CONFIG_SPI_FLASH_SST #ifdef.
>
> Changes v3->v4:
> * Make sst26_process_bpr() and sst26_lock_ctl() functions static.
>
> Changes v2->v3:
> * Move SST26 command defenition to sf_internal.h
> * Merge sst26_set_bpr, sst26_clear_bpr and sst26_check_bpr functions
> into single sst26_process_bpr function.
> * Use SF_UNLOCKED/SF_LOCKED instead of magic numbers in
> sst26_lock_ctl()
>
> Changes v1->v2:
> * Use generic defines from linux/sizes.h instead of custom ones.
>
> diff --git a/drivers/mtd/spi/spi_flash.c b/drivers/mtd/spi/spi_flash.c
[snip]
--
Eugeniy Paltsev
next prev parent reply other threads:[~2018-04-16 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 11:40 [U-Boot] [PATCH v5 0/2] SF: add support for sst26wf016, sst26wf032, sst26wf064 Eugeniy Paltsev
2018-04-10 11:40 ` [U-Boot] [PATCH v5 1/2] SPI Flash: add support of sst26wf* flash ICs protection ops Eugeniy Paltsev
2018-04-12 12:59 ` Eugeniy Paltsev
2018-04-16 13:52 ` Eugeniy Paltsev [this message]
2018-04-10 11:40 ` [U-Boot] [PATCH v5 2/2] SF: add support for sst26wf016, sst26wf032, sst26wf064 Eugeniy Paltsev
2018-04-19 11:25 ` [U-Boot] [PATCH v5 0/2] " Jagan Teki
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=1523886767.17585.1.camel@synopsys.com \
--to=eugeniy.paltsev@synopsys.com \
--cc=u-boot@lists.denx.de \
/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