From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Stefan Wahren <stefan.wahren@i2se.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Eric Anholt <eric@anholt.net>, Phil Elwell <phil@raspberrypi.org>
Cc: devicetree@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
Scott Branden <sbranden@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC 2/3] nvmem: add driver for Raspberry Pi OTP
Date: Wed, 11 Jul 2018 10:45:05 +0100 [thread overview]
Message-ID: <7c1f6ee8-9572-463f-ccc8-3d12ffccb8f5@linaro.org> (raw)
In-Reply-To: <1520602328-28972-3-git-send-email-stefan.wahren@i2se.com>
Hi Stefan,
On 09/03/18 13:32, Stefan Wahren wrote:
> This patch brings read-only support for the Raspberry Pi Customer OTP.
> The driver accesses the OTP via the mailbox property interface
> provided by the VPU firmware.
>
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
> ---
> drivers/nvmem/Kconfig | 10 +++
> drivers/nvmem/Makefile | 2 +
> drivers/nvmem/raspberrypi-otp.c | 138 ++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 150 insertions(+)
> create mode 100644 drivers/nvmem/raspberrypi-otp.c
Looks there are some pending trivial comments, are you planning to
resend this?
--srini
next prev parent reply other threads:[~2018-07-11 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 13:32 [PATCH RFC 0/3] nvmem: Enable OTP access for Raspberry Pi Stefan Wahren
2018-03-09 13:32 ` [PATCH RFC 1/3] dt-bindings: nvmem: add binding for Raspberry Pi OTP Stefan Wahren
2018-03-18 12:48 ` Rob Herring
2018-03-09 13:32 ` [PATCH RFC 2/3] nvmem: add driver " Stefan Wahren
2018-03-09 21:06 ` Eric Anholt
2018-03-18 12:48 ` Rob Herring
2018-07-11 9:45 ` Srinivas Kandagatla [this message]
2018-09-18 14:40 ` Stefan Wahren
2018-03-09 13:32 ` [PATCH RFC 3/3] ARM: dts: bcm2835-rpi: Enable OTP access for Raspberry Pi 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=7c1f6ee8-9572-463f-ccc8-3d12ffccb8f5@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=phil@raspberrypi.org \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.com \
/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).