Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1403147

Re: [PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel Secumod nvram

From Rob Herring <robh@kernel.org>
Newsgroups linux.kernel
Subject Re: [PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel Secumod nvram
Date 2016-05-18 18:50 +0200
Message-ID <rAcPx-4AL-35@gated-at.bofh.it> (permalink)
References <rzxjk-3lZ-13@gated-at.bofh.it> <rzxjk-3lZ-11@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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@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@0000 {

Use '-' rather than '_' and drop leading 0s.

> +                    reg = <0x0000 0x1000>;
> +            };
> +            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";
> +	};

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel Secumod nvram David Mosberger-Tang <davidm@egauge.net> - 2016-05-16 22:30 +0200
  Re: [PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel  Secumod nvram Rob Herring <robh@kernel.org> - 2016-05-18 18:50 +0200
    Re: [PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel  Secumod nvram David Mosberger <davidm@egauge.net> - 2016-05-18 22:50 +0200
    [PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel Secumod nvram David Mosberger-Tang <davidm@egauge.net> - 2016-05-18 23:10 +0200
      Re: [PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel  Secumod nvram Rob Herring <robh@kernel.org> - 2016-05-20 21:30 +0200
      Re: [PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel  Secumod nvram Srinivas Kandagatla <srinivas.kandagatla@linaro.org> - 2016-05-23 11:00 +0200

csiph-web