From: Rob Herring <robh@kernel.org>
To: David Mosberger-Tang <davidm@egauge.net>
Cc: srinivas.kandagatla@linaro.org, maxime.ripard@free-electrons.com,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
nicolas.ferre@atmel.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel Secumod nvram
Date: Fri, 20 May 2016 14:21:01 -0500 [thread overview]
Message-ID: <20160520192101.GA15615@rob-hp-laptop> (raw)
In-Reply-To: <1463605564-14397-1-git-send-email-davidm@egauge.net>
On Wed, May 18, 2016 at 03:06:04PM -0600, David Mosberger-Tang wrote:
> Signed-off-by: David Mosberger <davidm@egauge.net>
> ---
> .../devicetree/bindings/nvmem/atmel-secumod.txt | 47 +++++++
> drivers/nvmem/Kconfig | 7 +
> drivers/nvmem/Makefile | 2 +
> drivers/nvmem/atmel-secumod.c | 143 +++++++++++++++++++++
> 4 files changed, 199 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/atmel-secumod.txt
> create mode 100644 drivers/nvmem/atmel-secumod.c
>
> diff --git a/Documentation/devicetree/bindings/nvmem/atmel-secumod.txt b/Documentation/devicetree/bindings/nvmem/atmel-secumod.txt
> new file mode 100644
> index 0000000..d65cad5
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/atmel-secumod.txt
> @@ -0,0 +1,47 @@
> += Atmel Secumod device tree bindings =
> +
> +This binding is intended to represent Atmel's Secumod which is found
> +in SAMA5D2 and perhaps others.
> +
> +Required properties:
> +- compatible: should be "atmel,sama5d2-secumod"
> +- reg: Should contain RAM location and length, followed
> + by register location and length of the Secumod controller.
> +
> += Data cells =
> +Are child nodes of secumod, bindings of which as described in
> +bindings/nvmem/nvmem.txt
> +
> +Example:
> +
> + secumod@fc040000 {
This unit-address should match the first reg address.
> + compatible = "atmel,sama5d2-secumod";
> + reg = <0xf8044000 0x1420>, <0xfc040000 0x4000>;
> + reg-names = "SECURAM", "SECUMOD";
> + status = "okay";
> +
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges;
Sorry, to be clear, you need values here too.
> +
> + secram-auto-erasable@0 {
> + reg = <0x0000 0x1000>;
The 0 here is address 0xf8044000, right? So ranges is what is used to
translate from child address of 0 to the parent address.
> + };
> + secram@1000 {
> + reg = <0x1000 0x400>;
> + };
> + ram@1400 {
> + reg = <0x1400 0x20>;
> + };
> + };
> +
> += Data consumers =
> +Are device nodes which consume nvmem data cells.
> +
> +For example:
> +
> + ram {
> + ...
> + nvmem-cells = <&ram>;
> + nvmem-cell-names = "RAM";
> + };
next prev parent reply other threads:[~2016-05-20 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LNX.2.00.1605121505320.21379@nippy.intranet>
2016-05-16 20:17 ` [PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel Secumod nvram David Mosberger-Tang
[not found] ` <1463429830-20539-1-git-send-email-davidm-haPfTeumbwasTnJN9+BGXg@public.gmane.org>
2016-05-18 16:42 ` Rob Herring
2016-05-18 20:46 ` David Mosberger
2016-05-18 21:06 ` David Mosberger-Tang
2016-05-20 19:21 ` Rob Herring [this message]
2016-05-23 8:50 ` Srinivas Kandagatla
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=20160520192101.GA15615@rob-hp-laptop \
--to=robh@kernel.org \
--cc=davidm@egauge.net \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=nicolas.ferre@atmel.com \
--cc=pawel.moll@arm.com \
--cc=srinivas.kandagatla@linaro.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