public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Huang Shijie <shijie.huang@intel.com>
To: Zhi Li <lznuaa@gmail.com>
Cc: linux-mtd@lists.infradead.org, White Ding <bpqw@micron.com>,
	Brian Norris <computersforpeace@gmail.com>,
	Huang Shijie <shijie8@gmail.com>,
	boris.brezillon@free-electrons.com
Subject: Re: mtd: nand: lock unlock function
Date: Thu, 6 Nov 2014 08:50:37 +0800	[thread overview]
Message-ID: <20141106005036.GA19030@shldeISGChi005.sh.intel.com> (raw)
In-Reply-To: <CAHrpEqTQQ+YBnBY-fj9uW1bAMn-t_dmdVR9KuJR+2E+uA4vZ2Q@mail.gmail.com>

On Wed, Nov 05, 2014 at 04:00:29PM -0600, Zhi Li wrote:
> On Wed, Nov 5, 2014 at 2:57 PM, Brian Norris
> <computersforpeace@gmail.com> wrote:
> > +
> >
> > On Wed, Nov 05, 2014 at 02:31:34PM -0600, Zhi Li wrote:
> >> Does any know the reason why there are nand_lock and nand_unlock
> >> function in nand_base.c, but
> >>
> >>         mtd->_lock = NULL;
> >>         mtd->_unlock = NULL;
> >>
> >> Not set to nand_lock and nand_unlock?
> >
> > Possible answers:
> >
> >  * Lack of testing
> >
> >  * The LOCK/UNLOCK opcodes are not supported by all vendors
> >
> >  * Even the vendors that support them don't do so consistently (not sure
> >    about this one; I know Micron supports this in some cases)
> >
> >  * The opcodes aren't even documented (again, I'm not even sure about
> >    this one; but many Micron datasheets I see don't mention LOCK/UNLOCK.
> >    I recall that other similar lock/protection implementations are
> >    secret to some extent, and are intentionally omitted from the
> >    datasheets)
> 
> Yes, we recently met a problem with micron flash. Need send unlock command.
> The datasheet I get from micron
> MT29F8G08ABACA, MT29F8G16ABACA, MT29F8G08ABBCA,
> MT29F8G16ABBCA, MT29F16G08ADACA, MT29F16G16ADACA,
> MT29F16G08ADBCA , MT29F16G16ADBCA
> 
> support it.
> But not sure if it is public document.
> 
could you please describe what is the problem?

thanks
Huang Shijie

  reply	other threads:[~2014-11-06  0:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05 20:31 mtd: nand: lock unlock function Zhi Li
2014-11-05 20:57 ` Brian Norris
2014-11-05 22:00   ` Zhi Li
2014-11-06  0:50     ` Huang Shijie [this message]
2014-11-06  2:32     ` bpqw
2014-11-06  3:31       ` Zhi Li

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=20141106005036.GA19030@shldeISGChi005.sh.intel.com \
    --to=shijie.huang@intel.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=bpqw@micron.com \
    --cc=computersforpeace@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lznuaa@gmail.com \
    --cc=shijie8@gmail.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