From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [uboot-snps-arc] Re: [PATCH 1/2] SPI Flash: add support of sst26wf* flash series
Date: Tue, 13 Mar 2018 18:29:31 +0000 [thread overview]
Message-ID: <1520965770.4653.27.camel@synopsys.com> (raw)
In-Reply-To: <CAD6G_RTzU-54nGjO0hGqcLFtM1-xs5f4gXFYF+7EtepxPGy+Uw@mail.gmail.com>
Hi Jagan,
On Tue, 2018-03-13 at 22:11 +0530, Jagan Teki wrote:
> On Tue, Feb 6, 2018 at 8:45 PM, Eugeniy Paltsev
> <Eugeniy.Paltsev@synopsys.com> wrote:
> > sst26wf flash series block protection implementation differs
> > from other SST series, so add implementation for sst26wf
> > lock/unlock/is_locked functions.
>
> How it is different from existing SST implementation, Linux has
> support this similar part and use normal SST?
Looks like the person, who add sst26wf* flash series support to Linux
only use/test reading from these flash ICs and reading works fine
as only write protection implementation was changed.
Also it ids possible that these write protection bits were cleared
by prebootloader on platform there that patch was test - so flash
IC was already unlocked.
BTW: I have plans to port this patch to linux too.
--
Eugeniy Paltsev
next prev parent reply other threads:[~2018-03-13 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 15:15 [U-Boot] [PATCH 0/2] SF: add support for sst26wf016, sst26wf032, sst26wf064 Eugeniy Paltsev
2018-02-06 15:15 ` [U-Boot] [PATCH 1/2] SPI Flash: add support of sst26wf* flash series Eugeniy Paltsev
2018-02-23 19:01 ` [U-Boot] [uboot-snps-arc] " Eugeniy Paltsev
2018-03-13 16:41 ` [U-Boot] " Jagan Teki
2018-03-13 18:29 ` Eugeniy Paltsev [this message]
2018-02-06 15:15 ` [U-Boot] [PATCH 2/2] SF: add support for sst26wf016, sst26wf032, sst26wf064 Eugeniy Paltsev
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=1520965770.4653.27.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