From: Christian Riesch <christian.riesch@omicron.at>
To: linux-mtd@lists.infradead.org
Subject: cfi_cmdset_0002: reading and writing one time programmable memory
Date: Sat, 09 Feb 2013 09:35:09 +0100 [thread overview]
Message-ID: <51160A3D.2080500@omicron.at> (raw)
Hello,
I would like to extend the AMD command set for reading/writing/locking
of one time programmable (OTP) memory areas (called secure silicon in
Spansion device, called extended memory region in Micron devices...). In
particular I would like to support the 256 byte extended memory region
of Micron M29EW devices. Currently the code in
drivers/mtd/chips/cfi_cmdset_0002.c only supports reading of the first 8
bytes of this memory area.
I have already implemented this support partially, but before posting a
first patchset, I have a few questions regarding the current code in
do_read_secsi_onechip() in drivers/mtd/chips/cfi_cmdset_0002.c.
This function first waits for the chip to get into FL_READY state? Could
the get_chip() function be used instead here?
After sending the 0xaa/0x55/0x88 command to the device, the
OTP/SecSi/... memory is mapped to addresses 0x00 - 0xff of the device.
Does this require putting xip_disable/xip_enable around this code?
Should the cache get invalidated before reading? Should the function get
marked __xipram?
Thanks for your help!
Christian
reply other threads:[~2013-02-09 8:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51160A3D.2080500@omicron.at \
--to=christian.riesch@omicron.at \
--cc=linux-mtd@lists.infradead.org \
/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