From: Paul Fertser <fercerpav@gmail.com>
To: barebox@lists.infradead.org
Cc: Paul Fertser <fercerpav@gmail.com>
Subject: [PATCH 1/2] mach-imx: iim: clarify documentation
Date: Wed, 28 Sep 2011 13:16:57 +0400 [thread overview]
Message-ID: <1317201418-3290-1-git-send-email-fercerpav@gmail.com> (raw)
This adds additional Kconfig help to clarify the way to use barebox
for eFuses handling.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
---
arch/arm/mach-imx/Kconfig | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-imx/Kconfig b/arch/arm/mach-imx/Kconfig
index 8dc6a24..8d5bd74 100644
--- a/arch/arm/mach-imx/Kconfig
+++ b/arch/arm/mach-imx/Kconfig
@@ -497,6 +497,12 @@ config IMX_IIM
Device driver for the IC Identification Module (IIM) fusebox. Use the
regular md/mw commands to program and read the fusebox.
+ Fuses are grouped in "rows", 8 bits per row. When using md/mw commands,
+ employ the -b switch and consider the region to be specifying the "Fuse
+ Row Index" rather than "Fuse Row Offset" (which is FRI * 4). You should
+ consult the documentation for your chip for more elaborate description,
+ including the eFuse map, e.g. see AN3682 for i.MX25.
+
config IMX_IIM_FUSE_BLOW
bool "IIM fuses blow support"
depends on IMX_IIM
@@ -507,6 +513,10 @@ config IMX_IIM_FUSE_BLOW
Warning: blown fuses can not be unblown. Using this option may damage
your CPU, or make it unbootalbe. Use with care.
+ Before being actually able to blow the fuses, you need to explicitely
+ enable it:
+ imx_iim0.permanent_write_enable=1
+
endmenu
endif
--
1.7.3.4
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2011-09-28 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 9:16 Paul Fertser [this message]
2011-09-28 9:16 ` [PATCH 2/2] mach-imx: iim: cosmetic changes to the code to make it easier to follow Paul Fertser
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=1317201418-3290-1-git-send-email-fercerpav@gmail.com \
--to=fercerpav@gmail.com \
--cc=barebox@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