From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC V3 2/3] mxs: add driver for ocotp in i.MX23 and i.MX28
Date: Mon, 20 Oct 2014 16:44:03 +0200 [thread overview]
Message-ID: <3434817.dk7dLDFrcN@wuerfel> (raw)
In-Reply-To: <1413628372-2809-3-git-send-email-stefan.wahren@i2se.com>
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.
>
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
> ---
> drivers/misc/Kconfig | 13 ++
> drivers/misc/Makefile | 1 +
> drivers/misc/fsl_ocotp.c | 332 ++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 346 insertions(+)
> create mode 100644 drivers/misc/fsl_ocotp.c
>
> diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
> index b841180..7455efa 100644
> --- a/drivers/misc/Kconfig
> +++ b/drivers/misc/Kconfig
> @@ -515,6 +515,19 @@ config VEXPRESS_SYSCFG
> bus. System Configuration interface is one of the possible means
> of generating transactions on this bus.
>
> +config FSL_OCOTP
> + tristate "Freescale MXS On-Chip OTP Memory Support"
> + depends on ARCH_MXS && SYSFS
> + help
> + If you say Y here, you will get support for a readonly
> + SysFS interface for the One Time Programmable memory pages that
> + are stored on the Freescale i.MX23/i.MX28 processor.
> +
> + To compile this driver as a module, choose M here: the module
> + will be called fsl_ocotp.
> +
> + If unsure, it is safe to say N.
>
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
next prev parent reply other threads:[~2014-10-20 14:44 UTC|newest]
Thread overview: 23+ 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
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
2014-10-20 14:44 ` Arnd Bergmann [this message]
2014-10-20 15:32 ` Stefan Wahren
2014-10-20 17:32 ` Arnd Bergmann
2014-10-28 17:17 ` Ezequiel Garcia
2014-10-28 19:13 ` Arnd Bergmann
2014-11-06 19:25 ` Stefan Wahren
2014-11-06 19:47 ` Arnd Bergmann
2015-01-08 13:59 ` Ezequiel Garcia
2015-01-08 14:53 ` Stefan Wahren
2015-01-08 20:47 ` Stefan Wahren
2015-01-09 10:02 ` Thierry Reding
2015-01-12 9:21 ` Maxime Ripard
2014-11-07 19:14 ` Ezequiel Garcia
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
2015-02-25 20:18 ` [PATCH RFC V3 0/3] mxs: add ocotp support " Jörg Krause
2015-02-25 20:27 ` Jörg Krause
2015-02-26 7:11 ` Stefan Wahren
2015-02-26 8:02 ` Jörg Krause
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=3434817.dk7dLDFrcN@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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