public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel RAYNAL <miquel.raynal@free-electrons.com>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Richard Weinberger <richard.weinberger@gmail.com>,
	Boris Brezillon <Boris.Brezillon@free-electrons.com>
Subject: Re: macronix ONFI nand flash OTP support
Date: Thu, 23 Nov 2017 09:57:35 +0100	[thread overview]
Message-ID: <20171123095735.538118e0@xps13> (raw)
In-Reply-To: <CAAfyv37B2yRc7gybNi3hNs=ap52bgqTCrsx4tZe_5LNb7LfzVQ@mail.gmail.com>

Hi Marek,

+CC: NAND maintainers Boris and Richard

> Hi,
> 
> I'm trying to add find out how to use OTP area in Macronix
> MX30LF4G18AC flash. AFAIU it is ONFI based flash and I did some quick
> hack and I can set/reset flash to go to OTP mode via get/set_features
> function available in nand_base.c.

Ok, so until now you can enter/leave OTP mode with get/set_features(),
right ?

> But for read page I need to send
> according datasheet:
> To use the PAGE READ command for reading data from the OTP area, issue
> the 00h command, and then issue five address cycles: for the first two
> cycles, the column address; and for the remaining address cycles,
> select a page in the range of 02h-00h-00h through 1Fh-00h-00h. Lastly,
> issue the 30h command. The PAGE READ CACHE MODE command is not
> supported on OTP pages.

This is the description of a normal READ operation, there is nothing
specific to OTP.

> 
> I did check nand_do_read_ops function but it's not sending e.g. 0x30
> which should be at the end of command. I'm using 4.1 kernel but
> checked also 4.14 and no such functionality is added even there.
> Nobody is using OTP area in nand flashes ;) ? Thanks for any pointers.

I suppose you added some tweaks to enable OTP and use nand_do_read_ops,
because there is currently no implementation for that in the NAND
framework (I think there is something in MTD layer though). But must
importantly, nand_do_read_ops basically calls chip->ecc.read*() which
is handled by the controller driver, so what driver are you using ?

How (where) did you trace the commands sent to the NAND chip ? For
instance, if you just looked at the arguments of ->cmdfunc(), it is
normal not to see any READSTART (0x30) command as it should be added
automatically later in the function. If the driver implements
->cmd_ctrl(), you may see there what exactly is sent to the device.

Thanks,
Miquèl

  reply	other threads:[~2017-11-23  8:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 13:13 macronix ONFI nand flash OTP support Belisko Marek
2017-11-23  8:57 ` Miquel RAYNAL [this message]
2017-11-23  9:11   ` Belisko Marek
2017-11-23  9:30     ` Miquel RAYNAL
2017-11-23  9:40       ` Belisko Marek

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=20171123095735.538118e0@xps13 \
    --to=miquel.raynal@free-electrons.com \
    --cc=Boris.Brezillon@free-electrons.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.belisko@gmail.com \
    --cc=richard.weinberger@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