From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Tom Tatakis <ttatakis@appliedlogix.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Implementing OTP
Date: Tue, 31 May 2016 12:08:55 +0200 [thread overview]
Message-ID: <20160531120855.32ab3e57@bbrezillon> (raw)
In-Reply-To: <CAKKoKz5T5uddqyV955gnNenH6ejt_xMU_odmTC1FoQrbNm3R7w@mail.gmail.com>
Hi Tom,
Sorry for the late reply (remember to also Cc the NAND and MTD
maintainers next time).
On Thu, 5 May 2016 13:35:32 -0400
Tom Tatakis <ttatakis@appliedlogix.com> wrote:
> Hello,
>
> I have implemented OTP functionality in the NAND driver for the
> Macronix MX30LF1G18AC device. I would like to send it on up in a
> patch but I'd like to confirm that what I did makes sense. I modified
> nand_base.c file to include the requisite functions for reading and
> writing the OTP. I also modified the nand_scan_tail function to
> assign the names of the functions in the mtd structure. The potential
> issue is that the ONFI command used to read and write the OTP uses a
> feature address of 0x90 which is defined as part of the 'Vendor
> Specific' area if I understand the ONFI spec (it's entirely possible
> that I do not). Specifically, section 5.30 in Version 4.0 of the ONFI
> spec.
>
> If my modification of nand_base.c to include this makes sense, then I
> can put together a patch.
>
> I did try and figure out a way to get this potentially device
> dependent code into its own file, but I do not see how to do that
> other than creating a whole other driver for it complete with a
> configuration setting. If that's what I need to do then I will try
> and put it together. If there is a better way and you can point me
> int the right direction, that would be helpful as well.
You might want to have a look at [1] ;).
Regards,
Boris
[1]https://lkml.org/lkml/2016/5/27/264
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-05-31 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 17:35 Implementing OTP Tom Tatakis
2016-05-31 10:08 ` Boris Brezillon [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=20160531120855.32ab3e57@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-mtd@lists.infradead.org \
--cc=ttatakis@appliedlogix.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