From: Thomas Gleixner <tglx@linutronix.de>
To: Greg KH <gregkh@suse.de>
Cc: Jamie Iles <jamie@jamieiles.com>,
LKML <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [RFC PATCH 1/2] picoxcell-otp: add support for picoxcell OTP devices
Date: Sun, 3 Apr 2011 00:15:05 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1104030013070.5929@localhost6.localdomain6> (raw)
In-Reply-To: <20110323144230.GD17369@suse.de>
On Wed, 23 Mar 2011, Greg KH wrote:
> On Wed, Mar 23, 2011 at 12:16:58PM +0000, Jamie Iles wrote:
> > picoxcell devices contain a block of OTP memory that can be used for
> > storing first-stage bootloaders, cryptographic keys and other data to be
> > kept onchip. Different devices support a number of redundancy formats
> > to cope with in-field programming errors and can be partitioned into
> > regions to allow different redundancy formats with different effective
> > sizes.
> >
> > This patch implements an OTP device layer which different devices may
> > register their OTP regions with.
>
> Great, but why put it in drivers/char/? Why not drivers/otp/?
Why not drivers/mtd ? It's one time programmable memory technology
device if I'm not missing something.
Thanks,
tglx
next prev parent reply other threads:[~2011-04-02 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 12:16 [RFC PATCH 0/2] Support for picoxcell OTP memory Jamie Iles
2011-03-23 12:16 ` [RFC PATCH 1/2] picoxcell-otp: add support for picoxcell OTP devices Jamie Iles
2011-03-23 14:42 ` Greg KH
2011-03-23 15:12 ` Jamie Iles
2011-03-24 9:30 ` Jamie Iles
2011-04-02 22:15 ` Thomas Gleixner [this message]
2011-03-23 12:16 ` [RFC PATCH 2/2] picoxcellotp: add support for PC3X3 " Jamie Iles
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=alpine.LFD.2.00.1104030013070.5929@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=dwmw2@infradead.org \
--cc=gregkh@suse.de \
--cc=jamie@jamieiles.com \
--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;
as well as URLs for NNTP newsgroup(s).