From: Sascha Hauer <s.hauer@pengutronix.de>
To: Baruch Siach <baruch@tkos.co.il>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 1/2] cmd: add fuse_blow/fuse_sense for the i.MX IIM fusebox
Date: Thu, 12 Aug 2010 14:04:40 +0200 [thread overview]
Message-ID: <20100812120440.GZ27749@pengutronix.de> (raw)
In-Reply-To: <20100812092701.GE13166@jasper.tkos.co.il>
On Thu, Aug 12, 2010 at 12:27:01PM +0300, Baruch Siach wrote:
> Hi Sascha,
>
> On Thu, Aug 12, 2010 at 11:06:00AM +0200, Sascha Hauer wrote:
> > On Thu, Aug 12, 2010 at 11:35:04AM +0300, Baruch Siach wrote:
> > > This has only been tested on i.MX25, but should work on other i.MX chips with
> > > IIM.
> >
> > I would prefer this command to be implemented as a device driver which
> > registers a file under /dev. This way we could use the standard md/mw
> > commands for this and look at a nice hexdump of all fuses and not only
> > one at a time.
>
> There are two methods for getting fuses values, direct memory access, and
> explicit sensing. Each method can independently be disabled with two dedicated
> protect fuses. How can md choose the right sensing method?
By trying one method first and fall back to the other method.
>
> The IIM block also has an override functionality. Direct memory write to the
> fuse row overrides the value in this row. This feature can also be disabled
> with an override protect fuse. How does mw know whether you want to blow the
> fuses, or just override them?
You could override them when iim.writeenable=0 and blow them when
iim.writeenable=1. Return failure when the override protect fuse is
blown.
The fuse_blow/fuse_sense commands do not make this decision either, they
use the explicit sensing method hardcoded.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2010-08-12 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 6:25 [PATCH " Baruch Siach
2010-08-10 6:25 ` [PATCH 2/2] fec: add support for IIM stored mac address Baruch Siach
2010-08-10 7:09 ` [PATCH 1/2] cmd: add fuse_blow/fuse_sense for the i.MX IIM fusebox Jean-Christophe PLAGNIOL-VILLARD
2010-08-12 8:34 ` Baruch Siach
2010-08-12 8:35 ` [PATCH v2 " Baruch Siach
2010-08-12 8:35 ` [PATCH v2 2/2] fec: add support for IIM stored mac address Baruch Siach
2010-08-12 9:06 ` [PATCH v2 1/2] cmd: add fuse_blow/fuse_sense for the i.MX IIM fusebox Sascha Hauer
2010-08-12 9:27 ` Baruch Siach
2010-08-12 12:04 ` Sascha Hauer [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=20100812120440.GZ27749@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=baruch@tkos.co.il \
/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