public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: marex@denx•de (Marek Vasut)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH V4 RFC 2/3] nvmem: add driver for ocotp in i.MX23 and i.MX28
Date: Mon, 20 Jul 2015 00:12:13 +0200	[thread overview]
Message-ID: <201507200012.13608.marex@denx.de> (raw)
In-Reply-To: <1437343499-16422-3-git-send-email-stefan.wahren@i2se.com>

On Monday, July 20, 2015 at 12:04:58 AM, Stefan Wahren wrote:
> This patch brings read-only support for the On-Chip OTP cells
> in the i.MX23 and i.MX28 processor. The driver implements the
> new NVMEM provider API.
> 
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se•com>

How come this driver isn't doing any manipulation with the VDDIO
voltage -- or did I miss that? I seem to remember that the VDDIO
had to be lowered to 2.8V before the fuses could be programmed
and restored to 3.3V afterward. See for example recent mainline
u-boot, drivers/misc/mxs_ocotp.c .

Best regards,
Marek Vasut

  reply	other threads:[~2015-07-19 22:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-19 22:04 [PATCH V4 RFC 0/3] nvmem: add ocotp support for i.MX23 and i.MX28 Stefan Wahren
2015-07-19 22:04 ` [PATCH V4 RFC 1/3] DT: nvmem: add binding for mxs-ocotp Stefan Wahren
2015-07-19 22:04 ` [PATCH V4 RFC 2/3] nvmem: add driver for ocotp in i.MX23 and i.MX28 Stefan Wahren
2015-07-19 22:12   ` Marek Vasut [this message]
2015-07-20  6:45     ` Stefan Wahren
2015-07-20  8:15       ` Marek Vasut
2015-07-19 22:04 ` [PATCH V4 RFC 3/3] mxs: enable ocotp for " Stefan Wahren
2015-07-19 22:07 ` [PATCH V4 RFC 0/3] nvmem: add ocotp support " Marek Vasut
2015-07-20  6:37   ` Stefan Wahren
2015-07-20  8:16     ` Marek Vasut

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=201507200012.13608.marex@denx.de \
    --to=marex@denx$(echo .)de \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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