From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel Secumod nvram
Date: Wed, 18 May 2016 11:42:59 -0500 [thread overview]
Message-ID: <20160518164259.GA28954@rob-hp-laptop> (raw)
In-Reply-To: <1463429830-20539-1-git-send-email-davidm@egauge.net>
On Mon, May 16, 2016 at 02:17:10PM -0600, David Mosberger-Tang wrote:
> Signed-off-by: David Mosberger <davidm@egauge.net>
> ---
> .../devicetree/bindings/nvmem/atmel-secumod.txt | 46 ++++++++
> drivers/nvmem/atmel-secumod.c | 125 +++++++++++++++++++++
> 2 files changed, 171 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..85db709
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/atmel-secumod.txt
> @@ -0,0 +1,46 @@
> += 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 registers location and length of the RAM, followed
registers or RAM location?
"Should contain RAM location and length, ..."
> + 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 at fc040000 {
> + compatible = "atmel,sama5d2-secumod";
> + reg = <0xf8044000 0x1420
> + 0xfc040000 0x4000>;
You are missing ranges property.
> + status = "okay";
> +
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + secram_auto_erasable at 0000 {
Use '-' rather than '_' and drop leading 0s.
> + reg = <0x0000 0x1000>;
> + };
> + secram at 1000 {
> + reg = <0x1000 0x400>;
> + };
> + ram at 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-18 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 3:57 [PATCH] misc: atmel-secumod: Driver for Atmel "security module" David Mosberger-Tang
2016-01-25 11:09 ` Alexandre Belloni
2016-01-25 16:24 ` David Mosberger
2016-01-29 0:13 ` Finn Thain
2016-01-31 11:34 ` Alexandre Belloni
2016-05-23 12:04 ` Boris Brezillon
2016-05-23 12:53 ` Boris Brezillon
2016-05-23 13:59 ` Alexandre Belloni
2016-05-10 19:02 ` [PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel Secumod nvram David Mosberger-Tang
2016-05-12 5:06 ` Finn Thain
2016-05-16 20:17 ` David Mosberger-Tang
2016-05-18 16:42 ` Rob Herring [this message]
2016-05-18 20:46 ` David Mosberger
2016-05-18 21:06 ` David Mosberger-Tang
2016-05-20 19:21 ` Rob Herring
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=20160518164259.GA28954@rob-hp-laptop \
--to=robh@kernel.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