From: Michael Walle <michael@walle.cc>
To: Sean Anderson <sean.anderson@seco.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Shawn Guo <shawnguo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Li Yang <leoyang.li@nxp.com>,
linux-kernel@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH 2/8] dt-bindings: nvmem: sfp: Add clock properties
Date: Thu, 21 Apr 2022 20:12:34 +0200 [thread overview]
Message-ID: <4a45db184fbadc278624571dfbeb5004@walle.cc> (raw)
In-Reply-To: <20220421175657.1259024-3-sean.anderson@seco.com>
Am 2022-04-21 19:56, schrieb Sean Anderson:
> 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.
For some context: Sean was adding the SFP support in u-boot and
I referred him to this binding. I didn't need the clock to just
read the data. But Sean is right, we need the clock for the
programming. I was unaware of that. The binding is still yet to
be released with v5.18, thus I think it is still possible to make
the clock mandatory.
> Signed-off-by: Sean Anderson <sean.anderson@seco.com>
Fixes: 6f9817cdcc82 ("dt-bindings: nvmem: add fsl,layerscape-sfp
binding")
-michael
> ---
>
> .../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";
> };
next prev parent reply other threads:[~2022-04-21 18:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 17:56 [PATCH 0/8] nvmem: sfp: binding updates and additions Sean Anderson
2022-04-21 17:56 ` [PATCH 1/8] dt-bindings: nvmem: sfp: Fix typo Sean Anderson
2022-04-21 18:03 ` Michael Walle
2022-04-21 21:55 ` Andrew Lunn
2022-04-21 17:56 ` [PATCH 2/8] dt-bindings: nvmem: sfp: Add clock properties Sean Anderson
2022-04-21 18:12 ` Michael Walle [this message]
2022-04-22 21:27 ` Rob Herring
2022-04-22 13:36 ` Rob Herring
2022-04-22 14:33 ` Sean Anderson
2022-04-21 17:56 ` [PATCH 3/8] dt-bindings: nvmem: sfp: Add TA_PROG_SFP supply Sean Anderson
2022-04-21 21:59 ` Andrew Lunn
2022-04-21 22:06 ` Sean Anderson
2022-04-21 23:02 ` Andrew Lunn
2022-04-21 17:56 ` [PATCH 4/8] dt-bindings: nvmem: sfp: Add compatible binding for TA 2.1 SFPs Sean Anderson
2022-04-21 18:18 ` Michael Walle
2022-04-21 18:47 ` Sean Anderson
2022-04-21 17:56 ` [PATCH 5/8] arm64: dts: ls1028a: Update SFP binding to include clock Sean Anderson
2022-04-21 18:44 ` Michael Walle
2022-04-21 17:56 ` [PATCH 6/8] ARM: dts: layerscape: Add SFP binding for TA 2.1 devices Sean Anderson
2022-04-21 17:56 ` [PATCH 7/8] ARM: dts: Add SFP binding for TA 3.0 devices Sean Anderson
2022-04-21 17:56 ` [PATCH 8/8] nvmem: sfp: Add support for TA 2.1 devices Sean Anderson
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=4a45db184fbadc278624571dfbeb5004@walle.cc \
--to=michael@walle.cc \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sean.anderson@seco.com \
--cc=shawnguo@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).