devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
	robh+dt@kernel.org, kernel@pengutronix.de, galak@codeaurora.org,
	shawn.guo@linaro.org, festevam@gmail.com, mhei@heimpold.de
Subject: Re: [PATCH RFC V3 2/3] mxs: add driver for ocotp in i.MX23 and i.MX28
Date: Mon, 20 Oct 2014 17:32:37 +0200	[thread overview]
Message-ID: <54452B15.50502@i2se.com> (raw)
In-Reply-To: <3434817.dk7dLDFrcN@wuerfel>

Hi Arnd,

Am 20.10.2014 um 16:44 schrieb Arnd Bergmann:
> On Saturday 18 October 2014 10:32:51 Stefan Wahren wrote:
>> This patch brings readonly support for the On Chip OTP cells in the i.MX23
>> and i.MX28 processor. The driver uses files (one for each cell) in sysfs
>> as interface.
>>
>> ...
> I think this needs to be an MTD driver, not a "misc" driver, and it
> should use the proper MTD interfaces instead of introducing an
> incompatible set of interfaces.
>
> 	Arnd

phew that sounds like a lot of work and much complexity.

Am i right, that i should drop the sysfs interface?

Does MTD drivers have a readonly text (non binary) user interface?

Best regards
Stefan

  reply	other threads:[~2014-10-20 15:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-18 10:32 [PATCH RFC V3 0/3] mxs: add ocotp support for i.MX23 and i.MX28 Stefan Wahren
     [not found] ` <1413628372-2809-1-git-send-email-stefan.wahren-eS4NqCHxEME@public.gmane.org>
2014-10-18 10:32   ` [PATCH RFC V3 1/3] mxs: add binding for fsl ocotp Stefan Wahren
2014-10-18 10:32   ` [PATCH RFC V3 2/3] mxs: add driver for ocotp in i.MX23 and i.MX28 Stefan Wahren
     [not found]     ` <1413628372-2809-3-git-send-email-stefan.wahren-eS4NqCHxEME@public.gmane.org>
2014-10-20 14:44       ` Arnd Bergmann
2014-10-20 15:32         ` Stefan Wahren [this message]
     [not found]           ` <54452B15.50502-eS4NqCHxEME@public.gmane.org>
2014-10-20 17:32             ` Arnd Bergmann
2014-10-28 17:17         ` Ezequiel Garcia
     [not found]           ` <544FCFB3.10100-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org>
2014-10-28 19:13             ` Arnd Bergmann
2014-11-06 19:25               ` Stefan Wahren
     [not found]                 ` <1003885907.22061.1415301932743.JavaMail.open-xchange-0SF9iQWekqLZ78VGacPtK8gmgJlYmuWJ@public.gmane.org>
2014-11-06 19:47                   ` Arnd Bergmann
2014-11-07 19:14                   ` Ezequiel Garcia
     [not found]                     ` <545D1A0D.9050307-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org>
2014-11-07 19:44                       ` Stefan Wahren
2014-10-29  7:14             ` Stefan Wahren
2014-10-18 10:32   ` [PATCH RFC V3 3/3] mxs: enable ocotp for " Stefan Wahren

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=54452B15.50502@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=mhei@heimpold.de \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=shawn.guo@linaro.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).