From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [uboot-snps-arc] [PATCH v2 0/2] SF: add support for sst26wf016, sst26wf032, sst26wf064
Date: Fri, 30 Mar 2018 12:04:21 +0000 [thread overview]
Message-ID: <1522411460.6917.11.camel@synopsys.com> (raw)
In-Reply-To: <20180326110823.28921-1-Eugeniy.Paltsev@synopsys.com>
Hi Jagan,
On Mon, 2018-03-26 at 14:08 +0300, Eugeniy Paltsev wrote:
> Add support for the SST sst26wf016, sst26wf032 and sst26wf064 flash IC:
>
> sst26wf*** flash series block protection implementation differs from other
> SST series, so we add implementation for sst26wf*** lock/unlock/is_locked
> functions.
>
> Add sst26wf016, sst26wf032 and sst26wf064 flash IC info to spi_flash_ids list.
>
>
> Changes v1->v2:
> * Use generic defines from linux/sizes.h instead of custom ones.
>
> Eugeniy Paltsev (2):
> SPI Flash: add support of sst26wf* flash series
> SF: add support for sst26wf016, sst26wf032, sst26wf064
>
> drivers/mtd/spi/spi_flash.c | 188 ++++++++++++++++++++++++++++++++++++++++
> drivers/mtd/spi/spi_flash_ids.c | 3 +
> 2 files changed, 191 insertions(+)
Any chance for this series to hit your's and then Tom's
repos before RC1 gets cut on Monday April 2nd?
-Alexey
prev parent reply other threads:[~2018-03-30 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 11:08 [U-Boot] [PATCH v2 0/2] SF: add support for sst26wf016, sst26wf032, sst26wf064 Eugeniy Paltsev
2018-03-26 11:08 ` [U-Boot] [PATCH v2 1/2] SPI Flash: add support of sst26wf* flash series Eugeniy Paltsev
2018-04-04 13:43 ` Jagan Teki
2018-04-04 13:50 ` Alexey Brodkin
2018-04-04 14:07 ` Jagan Teki
2018-04-04 14:28 ` Jagan Teki
2018-04-05 12:40 ` Eugeniy Paltsev
2018-04-05 12:49 ` Jagan Teki
2018-03-26 11:08 ` [U-Boot] [PATCH v2 2/2] SF: add support for sst26wf016, sst26wf032, sst26wf064 Eugeniy Paltsev
2018-03-26 15:26 ` [U-Boot] [uboot-snps-arc] [PATCH v2 0/2] " Alexey Brodkin
2018-03-30 12:04 ` Alexey Brodkin [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=1522411460.6917.11.camel@synopsys.com \
--to=alexey.brodkin@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