public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Nandor Han <nandor.han@vaisala.com>
Cc: srinivas.kandagatla@linaro.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: nvmem: Add bootcount-nvmem
Date: Thu, 29 Apr 2021 15:53:10 -0500	[thread overview]
Message-ID: <20210429205310.GA1729011@robh.at.kernel.org> (raw)
In-Reply-To: <e0f9c2629ad651817a4726cd4f2d8e1775201595.1619617498.git.nandor.han@vaisala.com>

On Wed, Apr 28, 2021 at 04:50:38PM +0300, Nandor Han wrote:
> Documents the device tree bindings for `bootcount-nvmem` driver.
> 
> Signed-off-by: Nandor Han <nandor.han@vaisala.com>
> ---
>  .../bindings/nvmem/bootcount-nvmem.yaml       | 66 +++++++++++++++++++
>  1 file changed, 66 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/nvmem/bootcount-nvmem.yaml
> 
> diff --git a/Documentation/devicetree/bindings/nvmem/bootcount-nvmem.yaml b/Documentation/devicetree/bindings/nvmem/bootcount-nvmem.yaml
> new file mode 100644
> index 000000000000..cc673452fe0f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/bootcount-nvmem.yaml
> @@ -0,0 +1,66 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +# Copyright (c) Vaisala Oyj. All rights reserved.
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/nvmem/bootcount-nvmem.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Bootcount NVMEM bindings
> +
> +maintainers:
> +  - Nandor Han <nandor.han@vaisala.com>
> +
> +description: |
> +  This binding is intendent to describe the hardware location for
> +  storing the bootcount value and magic combo.
> +
> +  The NVMEM cell size should be 2 or 4 bytes.
> +
> +allOf:
> +  - $ref: "nvmem-consumer.yaml#"
> +
> +properties:
> +  compatible:
> +    enum:
> +      - linux,bootcount-nvmem

What makes this Linux specific? IIRC, u-boot has boot counting function 
too.

> +
> +  nvmem-cells:
> +    description: Phandle to reboot mode nvmem data cell.
> +    $ref: /schemas/types.yaml#/definitions/phandle-array
> +
> +  nvmem-cell-names:
> +    description: Name of the NVMEM cell.
> +    $ref: /schemas/types.yaml#/definitions/string-array
> +    enum:
> +      - bootcount-regs
> +
> +  linux,bootcount-magic:
> +    description: Override default mask value.
> +    $ref: /schemas/types.yaml#/definitions/uint32

I don't understand what this is. Is it magic or a mask?

> +
> +dependencies:
> +  nvmem-cell-names: [ nvmem-cells ]

Core schema takes care of this.

> +
> +required:
> +  - compatible
> +  - nvmem-cells
> +  - nvmem-cell-names
> +
> +additionalProperties: false
> +
> +examples:
> +  # example with 16 bit nvram cell:
> +  - |
> +    bootcount {
> +        compatible = "linux,bootcount-nvmem";
> +        nvmem-cells = <&bootcount_regs>;
> +        nvmem-cell-names = "bootcount-regs";
> +    };
> +
> +    rtc: rtc@68 {
> +        bootcount_regs: bootcount_nvmem_regs@e {
> +            reg = <0x0e 0x2>;

It would be simpler to just add a compatible here and get rid of the 
'bootcount' node here.

> +        };
> +    };
> +
> +...
> -- 
> 2.26.3
> 

  parent reply	other threads:[~2021-04-29 20:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 13:50 [PATCH v2 0/4] Bootcount driver using NVMEM cell as backend Nandor Han
2021-04-28 13:50 ` [PATCH v2 1/4] dt-bindings: nvmem: Add bootcount-nvmem Nandor Han
2021-04-28 22:15   ` Rob Herring
2021-04-29 20:53   ` Rob Herring [this message]
2021-04-30  8:21     ` Nandor Han
2021-04-28 13:50 ` [PATCH v2 2/4] nvmem: bootcount: add bootcount driver Nandor Han
2021-04-28 13:50 ` [PATCH v2 3/4] nvmem: snvs_lpgpr: use cell stride for regmap size calculation Nandor Han
2021-04-28 13:50 ` [PATCH v2 4/4] nvmem: snvs_lpgpr: support two bytes NVMEM cell size Nandor Han

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=20210429205310.GA1729011@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nandor.han@vaisala.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