public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] nvmem: add NXP LPC18xx OTP driver
Date: Mon, 19 Sep 2016 11:56:30 +0100	[thread overview]
Message-ID: <b46055ae-84f8-1ee8-bb4e-91d1722c66c8@linaro.org> (raw)
In-Reply-To: <20160913161241.22492-2-manabian@gmail.com>

On 13/09/16 17:12, Joachim Eastwood wrote:
> Add simple read only driver for the internal OTP (One Time Programmable)
> memory found on all NXP LPC18xx and LPC43xx devices.
>
> The OTP memory is split into 4 banks each with 4 32-bits word. Some of
> the banks contain predefined data while others are for general purpose
> and user programmable via the OTP API in ROM. Note that writing to the
> OTP memory is not yet supported.
>
> Signed-off-by: Joachim Eastwood <manabian@gmail.com>
> ---
>  drivers/nvmem/Kconfig       |  10 ++++
>  drivers/nvmem/Makefile      |   2 +
>  drivers/nvmem/lpc18xx_otp.c | 123 ++++++++++++++++++++++++++++++++++++++++++++
>  3 files changed, 135 insertions(+)
>  create mode 100644 drivers/nvmem/lpc18xx_otp.c
>

Patch looks good to me.

I will pick this patch + bindings patch once rc1 lands in.

Thanks,
srini

  reply	other threads:[~2016-09-19 10:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 16:12 [PATCH 0/3] nvmem: add lpc18xx OTP memory driver Joachim Eastwood
2016-09-13 16:12 ` [PATCH 1/3] nvmem: add NXP LPC18xx OTP driver Joachim Eastwood
2016-09-19 10:56   ` Srinivas Kandagatla [this message]
2016-10-07  1:44   ` Vladimir Zapolskiy
2016-10-08 10:26     ` Joachim Eastwood
2016-09-13 16:12 ` [PATCH 2/3] nvmem: dt: document lpc1850 OTP binding Joachim Eastwood
2016-09-23 13:35   ` Rob Herring
2016-09-23 20:05     ` Joachim Eastwood
2016-09-13 16:12 ` [PATCH 3/3] ARM: dts: lpc18xx: add otp node Joachim Eastwood

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=b46055ae-84f8-1ee8-bb4e-91d1722c66c8@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --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