From: maitysanchayan@gmail.com (Sanchayan Maity)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v6 0/3] Implement NVMEM/SoC bus support for Vybrid
Date: Mon, 29 Jun 2015 16:52:16 +0530 [thread overview]
Message-ID: <cover.1435574288.git.maitysanchayan@gmail.com> (raw)
In-Reply-To: <558A99FC.2070902@i2se.com>
Hello,
For what it's worth, a reworked implementation of the OCOTP driver
implementing the proper fuse and shadow register read sequence as
mentioned in the TRM.
I will avoid unnecessary churn after this and send the next v7 once
the nvmem framework gets merged.
Used the OCOTP code in barebox as a reference and the code is highly
similar to that. iMX6 OCOTP memory map is however different to Vybrid.
This set also does not contain code for exposing the ROM information,
have yet to check that.
Feedback and comments are most welcome. Thank you for all the reviews
till now.
Regards,
Sanchayan.
Sanchayan Maity (3):
clk: clk-vf610: Add clock for Vybrid OCOTP controller
ARM: dts: vfxxx: Add OCOTP node
drivers: nvmem: Add Vybrid OCOTP support
arch/arm/boot/dts/vfxxx.dtsi | 7 +
drivers/clk/imx/clk-vf610.c | 1 +
drivers/nvmem/Kconfig | 10 ++
drivers/nvmem/Makefile | 2 +
drivers/nvmem/vf610-ocotp.c | 250 ++++++++++++++++++++++++++++++++
include/dt-bindings/clock/vf610-clock.h | 3 +-
6 files changed, 272 insertions(+), 1 deletion(-)
create mode 100644 drivers/nvmem/vf610-ocotp.c
--
2.4.4
next prev parent reply other threads:[~2015-06-29 11:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 13:44 [RFC PATCH v6 0/2] Implement NVMEM/SoC bus support for Vybrid Sanchayan Maity
2015-06-23 13:44 ` [RFC PATCH v6 1/2] ARM: dts: vfxxx: Add OCOTP and OCROM nodes Sanchayan Maity
2015-06-23 13:44 ` [RFC PATCH v6 2/2] nvmem: Add Vybrid OCOTP and OCROM support Sanchayan Maity
2015-06-23 19:03 ` Srinivas Kandagatla
2015-06-24 5:25 ` maitysanchayan at gmail.com
2015-06-23 19:31 ` Stefan Wahren
2015-06-24 5:19 ` maitysanchayan at gmail.com
2015-06-24 9:37 ` Srinivas Kandagatla
2015-06-24 9:44 ` Sanchayan Maity
2015-06-24 9:56 ` Stefan Wahren
2015-06-24 10:45 ` maitysanchayan at gmail.com
2015-06-24 11:52 ` Stefan Wahren
2015-06-24 12:05 ` maitysanchayan at gmail.com
2015-06-29 11:22 ` Sanchayan Maity [this message]
2015-06-29 11:22 ` [RFC PATCH v6 1/3] clk: clk-vf610: Add clock for Vybrid OCOTP controller Sanchayan Maity
2015-06-29 11:22 ` [RFC PATCH v6 2/3] ARM: dts: vfxxx: Add OCOTP node Sanchayan Maity
2015-06-29 11:22 ` [RFC PATCH v6 3/3] drivers: nvmem: Add Vybrid OCOTP support Sanchayan Maity
2015-07-06 10:16 ` Stefan Wahren
2015-07-07 5:19 ` maitysanchayan at gmail.com
2015-07-07 12:49 ` Stefan Wahren
2015-07-08 5:39 ` maitysanchayan at gmail.com
2015-07-08 20:55 ` Stefan Wahren
2015-07-10 18:09 ` maitysanchayan at gmail.com
2015-06-24 11:20 ` [RFC PATCH v6 2/2] nvmem: Add Vybrid OCOTP and OCROM support Stefan Agner
2015-06-24 8:35 ` Maxime Ripard
2015-06-24 9:34 ` Srinivas Kandagatla
2015-06-25 17:49 ` Maxime Ripard
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=cover.1435574288.git.maitysanchayan@gmail.com \
--to=maitysanchayan@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).