From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 9D98FC433F5 for ; Thu, 21 Apr 2022 18:13:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: Content-Transfer-Encoding:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:Message-ID:References:In-Reply-To:Subject:Cc:To:From :Date:MIME-Version:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=P0QhIjiKQM/2t0PNjRRs8m1C5p7Uqnep0EzLw4jB/EQ=; b=g3AmAb7rb13Iatqh1WcLv64P1R LHTdPyo7MRxL9T5QugYWVbfPMIwvE9XuhS6qJ7iKRx67gfy7iHkGONw8K1iaeVkqsqotsmd6YnUES l/fyd0olqsPMk2Kkj/FbduzOzvF7b5RvG/6QnNgi9SnanQVvWUgj1fAdTPaAOOvHujILxjZLogiQW +4mt4O/tFNCDdv/RH6KomRnrc9xfXxLylqpN5PyGJNH2WX6PP0/tAyeeV7JeS8OiDxNHYmlOWXema ZJewc8GRl3pJUoMswBH+GpLxzgxbE/8n5KONeHntPvwl6JYCJtCK/boPMD3bGFXLzaXW6IeObwtRO /6ZrF+RQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nhbII-00EbJ2-F1; Thu, 21 Apr 2022 18:12:42 +0000 Received: from ssl.serverraum.org ([176.9.125.105]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nhbIE-00EbHJ-D3 for linux-arm-kernel@lists.infradead.org; Thu, 21 Apr 2022 18:12:39 +0000 Received: from ssl.serverraum.org (web.serverraum.org [172.16.0.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.serverraum.org (Postfix) with ESMTPSA id 59439221D4; Thu, 21 Apr 2022 20:12:34 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2016061301; t=1650564754; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ts6rqzSFl+U/1vZW3tUs1vbFzVMiItVsA9fsXqIDkFI=; b=adtvdiWGqOSS3QqdMftPgNpszCPfNmrbDY3Opm67Pi5H8X3njSmCLVMGFCES+9pthJzGJU P1MAXSrWSSIDI4jxc4NyPEqFFI0EqC4Ve5SgyRDERhfIBD81y9/Pp/Ht/wY2PyduRozp+I 9DV6ZXkkNxUz5zHWviW0gLeUxkEQb60= MIME-Version: 1.0 Date: Thu, 21 Apr 2022 20:12:34 +0200 From: Michael Walle To: Sean Anderson Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, Shawn Guo , Rob Herring , Krzysztof Kozlowski , Li Yang , linux-kernel@vger.kernel.org, Srinivas Kandagatla Subject: Re: [PATCH 2/8] dt-bindings: nvmem: sfp: Add clock properties In-Reply-To: <20220421175657.1259024-3-sean.anderson@seco.com> References: <20220421175657.1259024-1-sean.anderson@seco.com> <20220421175657.1259024-3-sean.anderson@seco.com> User-Agent: Roundcube Webmail/1.4.13 Message-ID: <4a45db184fbadc278624571dfbeb5004@walle.cc> X-Sender: michael@walle.cc X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220421_111238_659445_C8149C02 X-CRM114-Status: GOOD ( 16.38 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org 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 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 > efuse@1e80000 { > compatible = "fsl,ls1028a-sfp"; > reg = <0x1e80000 0x8000>; > + clocks = <&clockgen QORIQ_CLK_PLATFORM_PLL > + QORIQ_CLK_PLL_DIV(4)>; > + clock-names = "sfp"; > }; _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel