From: Jiri Slaby <jirislaby@gmail.com>
To: Robin Getz <rgetz@blackfin.uclinux.org>
Cc: Bryan Wu <bryan.wu@analog.com>,
linux-kernel@vger.kernel.org,
Mike Frysinger <michael.frysinger@analog.com>
Subject: Re: [PATCH 1/1] [Blackfin] char driver for Blackfin on-chip OTP memory
Date: Wed, 30 Jan 2008 14:08:59 +0100 [thread overview]
Message-ID: <47A076EB.9020401@gmail.com> (raw)
In-Reply-To: <200801300739.21344.rgetz@blackfin.uclinux.org>
On 01/30/2008 01:39 PM, Robin Getz wrote:
> On Wed 30 Jan 2008 06:00, Jiri Slaby pondered:
>> On 01/30/2008 11:36 AM, Bryan Wu wrote:
>>> From: Mike Frysinger <michael.frysinger@analog.com>
>>>
>>> initial char driver for otp memory
>>> (only read supported atm ... needs real examples/docs for write support)
>>>
>>> Signed-off-by: Mike Frysinger <michael.frysinger@analog.com>
>>> Signed-off-by: Bryan Wu <bryan.wu@analog.com>
>
>>> + bfin_otp_class = class_create(THIS_MODULE, "otp");
>>> + device_create(bfin_otp_class, NULL, bfin_otp_dev_node, "otp");
>> Anyway, wouldn't be easier/better to use misc.c functionality here
>> (misc_register() et al.)?
>
> OTP (one time programmable) memory are not registers, they are small blocks
> (8k bytes) of non violate on chip memory, for storing things that you don't
> want other people to look at via a PCB level probe. (like keys), or things
> that are just helpful - like MAC addresses.
Sorry, misc_register() allows you to get rid of the chrdev initialization
including class creation. Maybe I'm not understanding what you are trying to
explain me?
next prev parent reply other threads:[~2008-01-30 13:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 10:36 [PATCH 1/1] [Blackfin] char driver for Blackfin on-chip OTP memory Bryan Wu
2008-01-30 11:00 ` Jiri Slaby
2008-01-30 12:39 ` Robin Getz
2008-01-30 13:08 ` Jiri Slaby [this message]
2008-01-30 13:15 ` Bryan Wu
2008-01-30 13:43 ` Jiri Slaby
2008-01-30 13:53 ` Jiri Slaby
2008-01-30 13:19 ` Mike Frysinger
2008-01-30 13:38 ` Jiri Slaby
2008-01-30 13:41 ` Mike Frysinger
2008-02-05 18:59 ` Mike Frysinger
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=47A076EB.9020401@gmail.com \
--to=jirislaby@gmail.com \
--cc=bryan.wu@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.frysinger@analog.com \
--cc=rgetz@blackfin.uclinux.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).