linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org,
	Sean Anderson <sean.anderson@seco.com>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: [PATCH 12/16] dt-bindings: nvmem: sfp: Add clock properties
Date: Fri, 29 Apr 2022 17:26:57 +0100	[thread overview]
Message-ID: <20220429162701.2222-13-srinivas.kandagatla@linaro.org> (raw)
In-Reply-To: <20220429162701.2222-1-srinivas.kandagatla@linaro.org>

From: Sean Anderson <sean.anderson@seco.com>

To program fuses, it is necessary to set the fuse programming time. This
is determined based on the value of the platform clock. Add a clock
property.

Because this property is necessary for programming, it is made
mandatory. Since these bindings have not yet been present in a stable
release (though they are on track for 5.18), it is not an ABI break to
change them in this manner.

Signed-off-by: Sean Anderson <sean.anderson@seco.com>
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
---
 .../bindings/nvmem/fsl,layerscape-sfp.yaml         | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/Documentation/devicetree/bindings/nvmem/fsl,layerscape-sfp.yaml b/Documentation/devicetree/bindings/nvmem/fsl,layerscape-sfp.yaml
index b7798e903191..54086f50157d 100644
--- a/Documentation/devicetree/bindings/nvmem/fsl,layerscape-sfp.yaml
+++ b/Documentation/devicetree/bindings/nvmem/fsl,layerscape-sfp.yaml
@@ -24,15 +24,29 @@ properties:
   reg:
     maxItems: 1
 
+  clocks:
+    maxItems: 1
+    description:
+      The SFP clock. Typically, this is the platform clock divided by 4.
+
+  clock-names:
+    const: sfp
+
 required:
   - compatible
   - reg
+  - clock-names
+  - clocks
 
 unevaluatedProperties: false
 
 examples:
   - |
+    #include <dt-bindings/clock/fsl,qoriq-clockgen.h>
     efuse@1e80000 {
         compatible = "fsl,ls1028a-sfp";
         reg = <0x1e80000 0x8000>;
+        clocks = <&clockgen QORIQ_CLK_PLATFORM_PLL
+                            QORIQ_CLK_PLL_DIV(4)>;
+        clock-names = "sfp";
     };
-- 
2.21.0


  parent reply	other threads:[~2022-04-29 16:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 16:26 [PATCH 00/16] nvmem: patches (set 1) for 5.19 Srinivas Kandagatla
2022-04-29 16:26 ` [PATCH 01/16] nvmem: core: support passing DT node in cell info Srinivas Kandagatla
2022-04-29 16:26 ` [PATCH 02/16] nvmem: brcm_nvram: find Device Tree nodes for NVMEM cells Srinivas Kandagatla
2022-04-29 16:26 ` [PATCH 03/16] MAINTAINERS: Add apple efuses nvmem files to ARM/APPLE MACHINE Srinivas Kandagatla
2022-04-29 16:26 ` [PATCH 04/16] dt-bindings: nvmem: Add apple,efuses Srinivas Kandagatla
2022-04-29 16:26 ` [PATCH 05/16] nvmem: Add Apple eFuse driver Srinivas Kandagatla
2022-04-29 16:26 ` [PATCH 06/16] nvmem: bcm-ocotp: mark ACPI device ID table as maybe unused Srinivas Kandagatla
2022-04-29 16:26 ` [PATCH 07/16] nvmem: sunplus-ocotp: drop useless probe confirmation Srinivas Kandagatla
2022-04-29 16:26 ` [PATCH 08/16] nvmem: sunplus-ocotp: staticize sp_otp_v0 Srinivas Kandagatla
2022-04-29 16:26 ` [PATCH 09/16] nvmem: qfprom: using pm_runtime_resume_and_get instead of pm_runtime_get_sync Srinivas Kandagatla
2022-04-29 16:26 ` [PATCH 10/16] nvmem: brcm_nvram: check for allocation failure Srinivas Kandagatla
2022-04-29 16:26 ` [PATCH 11/16] dt-bindings: nvmem: sfp: Fix typo Srinivas Kandagatla
2022-04-29 16:26 ` Srinivas Kandagatla [this message]
2022-04-29 16:26 ` [PATCH 13/16] dt-bindings: nvmem: sfp: Add TA_PROG_SFP supply Srinivas Kandagatla
2022-04-29 16:26 ` [PATCH 14/16] dt-bindings: nvmem: sfp: Add compatible binding for TA 2.1 SFPs Srinivas Kandagatla
2022-04-29 16:27 ` [PATCH 15/16] nvmem: sfp: Use regmap Srinivas Kandagatla
2022-04-29 16:27 ` [PATCH 16/16] nvmem: sfp: Add support for TA 2.1 devices Srinivas Kandagatla
2022-05-09 13:47 ` [PATCH 00/16] nvmem: patches (set 1) for 5.19 Greg KH
2022-05-10  9:29   ` 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=20220429162701.2222-13-srinivas.kandagatla@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sean.anderson@seco.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).