From: Jamie Iles <jamie@jamieiles.com>
To: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH] picoxcell_fuse: add support for the picoXcell fuse block
Date: Thu, 17 Feb 2011 16:49:52 +0000 [thread overview]
Message-ID: <20110217164952.GD941@pulham.picochip.com> (raw)
In-Reply-To: <1297092390-10610-1-git-send-email-jamie@jamieiles.com>
On Mon, Feb 07, 2011 at 03:26:30PM +0000, Jamie Iles wrote:
> Picochip picoXcell devices contain a fuse block that controls
> aspects of the device such as disabling JTAG, disabling the ARM
> memory controller, secure booting and storing secure keys. This
> driver provides a character device to read and write the fuse
> values and exports the fuse ranges to sysfs.
>
> Platforms should add a struct picoxcell_fuse_map to the platform
> device platform_data defining all of the fuse ranges and protection
> bits.
>
> Signed-off-by: Jamie Iles <jamie@jamieiles.com>
Does anyone have any feedback on this driver?
Thanks,
Jamie
prev parent reply other threads:[~2011-02-17 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 15:26 [RFC PATCH] picoxcell_fuse: add support for the picoXcell fuse block Jamie Iles
2011-02-17 16:49 ` Jamie Iles [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=20110217164952.GD941@pulham.picochip.com \
--to=jamie@jamieiles.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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