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 2F9B0C4828D for ; Tue, 6 Feb 2024 18:43:24 +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-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=Q1ZrXduoCcDCmFkOnrrvsTj1vz0C9JoijARXt3WQe+M=; b=fxwf9cCjmsFbCF D3TnDCW9pUIYBD3GNZRdhrn0t4nydZAQK3SN3SvbcbogBhBI+COPNy2q9kgG7I8pRZJmLGbzYXzvR sSkleizvxMJG6rKunMSEN+vAROAs0wgrT2BGbhuvYNQ9pDmvqc9LeFEv0Dvx6VwG0lSwaB5bYLjSc oEnC81ydRfH2CWpTLIzR7PgsrGIUDuHyHc4VxX1sALhvG1iiBY9DyNOoAHlChwNGrcDbNtOrGRCLC zrUMhl14ghaYZucZy6xmsPoY1Z7iRBmsPS7Ykwqgf9adcbBCVLZQvPCll7L25KtWm0gH9kx3bj0fn moKRfNKL+fKTmxasGRug==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rXQPa-00000008YIC-2ao8; Tue, 06 Feb 2024 18:43:14 +0000 Received: from sin.source.kernel.org ([2604:1380:40e1:4800::1]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1rXQPX-00000008YGz-1g7c for linux-arm-kernel@lists.infradead.org; Tue, 06 Feb 2024 18:43:12 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id C7C60CE1726; Tue, 6 Feb 2024 18:43:09 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B1E06C433C7; Tue, 6 Feb 2024 18:43:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1707244989; bh=b8iiNmOxD0YSZRAXkjUpo5Bj7K1mUidd9Bi4uo8nVYE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=YYatzYeTjSOJMl3yYbLE926+PErs/nE/D8+JB+OZLPPymTr2qQp0fE8/NfA1Kkq7p 6B6Ok33LCm9VU/Y/g+tz4MZoDf9IAH2hTq38poE/STBvgOKXRbpeZHlqXGuxlezhhq 3XM6jO0cnIjaXypc2XERjyS3qlEB0rJ17M7o/pGbbm1DaDoPLekeABJUqXaqeQjbD9 Heux0j0VHAvbGpDtWI2dw6gxtvnHzjwp1PcQP69q5zo5nT6lqYLbTTaVbW8G0KCck0 qXPRimIzR8CWO7g+7yTnbO5Q0rCjjd4CvnQsaUmMAm9tKQsAAeqAPpPAWgMSZR7EhG jwjRU4jop5E3g== Date: Tue, 6 Feb 2024 18:43:05 +0000 From: Rob Herring To: Markus Schneider-Pargmann Cc: Nishanth Menon , Vignesh Raghavendra , Tero Kristo , Krzysztof Kozlowski , Conor Dooley , Srinivas Kandagatla , Santosh Shilimkar , Andrew Davis , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/4] dt-bindings: hwinfo: ti,k3-socinfo: Add nvmem-cells Message-ID: <20240206184305.GA1875492-robh@kernel.org> References: <20240206143711.2410135-1-msp@baylibre.com> <20240206143711.2410135-3-msp@baylibre.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20240206143711.2410135-3-msp@baylibre.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240206_104311_637110_0D53B1D9 X-CRM114-Status: GOOD ( 17.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-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Feb 06, 2024 at 03:37:09PM +0100, Markus Schneider-Pargmann wrote: > The information k3-socinfo requires is stored in an efuse area. This > area is required by other devices/drivers as well, so using nvmem-cells > can be a cleaner way to describe which information are used. > > If nvmem-cells are supplied, the address range is not required. > Cells chipvariant, chippartno and chipmanufacturer are introduced to > cover all required information. > > Signed-off-by: Markus Schneider-Pargmann > Reviewed-by: Andrew Davis > --- > .../bindings/hwinfo/ti,k3-socinfo.yaml | 23 ++++++++++++++++++- > 1 file changed, 22 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/hwinfo/ti,k3-socinfo.yaml b/Documentation/devicetree/bindings/hwinfo/ti,k3-socinfo.yaml > index dada28b47ea0..f085b7275b7d 100644 > --- a/Documentation/devicetree/bindings/hwinfo/ti,k3-socinfo.yaml > +++ b/Documentation/devicetree/bindings/hwinfo/ti,k3-socinfo.yaml > @@ -26,9 +26,24 @@ properties: > reg: > maxItems: 1 > > + nvmem-cells: > + $ref: /schemas/types.yaml#/definitions/phandle-array > + > + nvmem-cell-names: > + items: > + - const: chipvariant > + - const: chippartno > + - const: chipmanufacturer > + > required: > - compatible > - - reg > + > +oneOf: > + - required: > + - reg > + - required: > + - nvmem-cells > + - nvmem-cell-names > > additionalProperties: false > > @@ -38,3 +53,9 @@ examples: > compatible = "ti,am654-chipid"; > reg = <0x43000014 0x4>; > }; > + - | > + chipid: chipid@14 { > + compatible = "ti,am654-chipid"; This isn't compatible if you have a completely different way to access it. > + nvmem-cells = <&chip_variant>, <&chip_partno>, <&chip_manufacturer>; > + nvmem-cell-names = "chipvariant", "chippartno", "chipmanufacturer"; > + }; > -- > 2.43.0 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel