From patchwork Fri Nov 4 16:38:28 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Miquel Raynal X-Patchwork-Id: 13032351 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 BE322C433FE for ; Fri, 4 Nov 2022 16:39:43 +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:MIME-Version:References:In-Reply-To: Message-Id:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=FCprAzc8hh5eNbvnHKdNc1xUsoDAZPlw7Pxf+xcZFxw=; b=xiKin9tOFEESSY k6iDQ3TM2Sb92w6kq18rcAEs9XnX0t4ooIgsA6i3dwzpFPC6Qsp1CBp7pRb2Du3WOX26iMUoDrWKL HDdGTyfvCEQ+5kRjfQQkuAOVH0f8Q4wzxPwpJ98Rm+ivnRvTW2ZsJcZvC/xG03MuV1rvTiVHA1KvT LEdVSiLuMofggXgJiG+mUFfcygWoJMNfWZUZQvZzHFuzqeNCkya6bQi+/awyJIg+/zJiCiKR1Kqqv W5OvEhlcjxXwOQ7l25bQoNs0d2wFKUK/TbIUsONYWn2s7DA7DZeKqkGfdEFv7tJ+3iB7wGrDtZ502 OFbQsQ6LkXgMG+JZoDMQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oqziO-004SCG-QF; Fri, 04 Nov 2022 16:38:44 +0000 Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oqziL-004S9M-QV for linux-arm-kernel@lists.infradead.org; Fri, 04 Nov 2022 16:38:42 +0000 Received: (Authenticated sender: miquel.raynal@bootlin.com) by mail.gandi.net (Postfix) with ESMTPSA id BACF1C0007; Fri, 4 Nov 2022 16:38:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=gm1; t=1667579917; 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=qX2H0ur2OnCIgQeP/+gCTgWmky+YXYnfa5R62aawbFk=; b=itdUWKp0OmmDnDJESvme0X3wZnc7hPuqS3zHyYW+2+mowPgKotWMs9TqhCdXNX0867vDSj AlDVLdR7YwdnvTMHWcBHP3HqhCpbFGD9P8/pDZLCOwYUCArMLneRHT4/aBnMCHqgIET3HU nAltOxSf2nXyu78KxUbEwHXGto/a27CoRB2MvdVtL01jryrnAotDVIbseMWxXN2xqSBcUX HCTTcCm9nwRDp1+2wXJmlabzelDqvGeE4lRILIIdldXHgRPJUQ7c3vd9d18I0rIrB3KsQm e+IOdAy7R3wqh120QlM5wKqxhhXJ/CBCmirCEeQZ3E7kGOLQLGWpmsUDkzNu3g== From: Miquel Raynal To: Rob Herring , Krzysztof Kozlowski , devicetree@vger.kernel.org Cc: Srinivas Kandagatla , , Robert Marko , Luka Perkov , Thomas Petazzoni , Michael Walle , , Bartosz Golaszewski , Christian Eggers , Cory Tusar , Miquel Raynal Subject: [PATCH v3 1/6] dt-bindings: nvmem: Fix example Date: Fri, 4 Nov 2022 17:38:28 +0100 Message-Id: <20221104163833.1289857-2-miquel.raynal@bootlin.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20221104163833.1289857-1-miquel.raynal@bootlin.com> References: <20221104163833.1289857-1-miquel.raynal@bootlin.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221104_093842_031577_B26816B8 X-CRM114-Status: UNSURE ( 9.53 ) X-CRM114-Notice: Please train this message. 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: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Despite not being listed nor required within the top level nvmem yaml file, the "compatible" property is mandatory and is actually enforced by all the nvmem provider bindings. Unfortunately, the lack of compatible in the nvmem.yaml to level description file lead to the example not matching anything and thus not being checked at all. Let's pick a compatible almost randomly (one which is already used with the qfprom label) to make the example at least valid on a semantic point of view and getting it checked. Signed-off-by: Miquel Raynal Acked-by: Rob Herring --- Documentation/devicetree/bindings/nvmem/nvmem.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/nvmem/nvmem.yaml b/Documentation/devicetree/bindings/nvmem/nvmem.yaml index 1eb22dba364c..0455506fc30f 100644 --- a/Documentation/devicetree/bindings/nvmem/nvmem.yaml +++ b/Documentation/devicetree/bindings/nvmem/nvmem.yaml @@ -67,6 +67,7 @@ examples: #include qfprom: eeprom@700000 { + compatible = "qcom,msm8974-qfprom", "qcom,qfprom"; #address-cells = <1>; #size-cells = <1>; reg = <0x00700000 0x100000>;