Received: by 2002:a17:90a:88:0:0:0:0 with SMTP id a8csp12890pja; Fri, 22 Nov 2019 02:48:08 -0800 (PST) X-Google-Smtp-Source: APXvYqzkUu7IsPzzHCUs52PYPB9DRraJflApMGI0cUfZqJpetYrXir0XGTJgeT18i9+buDdJYdE/ X-Received: by 2002:a17:906:2db2:: with SMTP id g18mr2506649eji.163.1574419688432; Fri, 22 Nov 2019 02:48:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574419688; cv=none; d=google.com; s=arc-20160816; b=ldB8TWkJ+qAEU9hfaNlKfI+znWAb/01nhFJx6VP/tBrOFLh6TngaKA755yrBFT+vuE Isk9Cv6Ngv6bwpdF8emZutk6DcmOoiSXckxXAE0naAr7L/wALni50rPQ8Hhtn266Esy5 2wX3+xJmA2oIqNbVmx08OKaWLY6a+nnOGSfpuIud6Ibh4QryS4DjGotg6IyTBJw3hXcx 2LBhyt0+PwbpEe9SioJ2GVxUlykkSwpeAx4L4dVL1+wGQMag7MdKepxGQMQ81+cuJCvo laW85NPVPgckEyhQJMraRoNaHJi4vpGok/lKgzOmE2Th35K/qCKr4fhuiztlxrV8XWvT UERA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:dkim-signature; bh=3uvMaCvyj8tNBEVETH0tKEXxb92y41/JsxGMzqMtSM0=; b=sdP7chH5BEwG2zNIQubVUyI59t+rvXaEbOTuE8moxOA6CVkbkV2jbZjmGP/g1BDu5z xz7tzMb1+AySPyijCQsGislp7xBXhEOKfVT+DdWuvJp10qj+9jugxuneSK9Bmxt1dv7T XKRs5f6hqkwQu99zuTUSbtu/XFJp8Z2Cc7lnR0ykNGKlIqWlB0YWpVx+6nBEbq6hl7M3 FJBZBKjRmVAngz2Z2UnVgBhPOQbkQtWRI8RPMlBu7PzFozDV66lNpZLGhzXLZNxPHWtM PM/CTvU1hrpVXnnTRie5yJMG4voNtvywmhE4iCS9zwkNj3HUqW07Wpetwt6Eq5ZJ0yq8 FcKQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@st.com header.s=STMicroelectronics header.b=Lh7tB1R1; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=st.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r7si4100425edy.16.2019.11.22.02.47.44; Fri, 22 Nov 2019 02:48:08 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@st.com header.s=STMicroelectronics header.b=Lh7tB1R1; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=st.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729586AbfKVKp6 (ORCPT + 99 others); Fri, 22 Nov 2019 05:45:58 -0500 Received: from mx07-00178001.pphosted.com ([62.209.51.94]:7864 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729545AbfKVKpx (ORCPT ); Fri, 22 Nov 2019 05:45:53 -0500 Received: from pps.filterd (m0046037.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id xAMAhMJr011963; Fri, 22 Nov 2019 11:45:40 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=st.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=STMicroelectronics; bh=3uvMaCvyj8tNBEVETH0tKEXxb92y41/JsxGMzqMtSM0=; b=Lh7tB1R1ohJKj4m7G9Csue4E8s4QAaeKoV/JqDc4YtKTvf3p0z4hbVAhT7Bw04eZJAyZ vHxWUxlrDUgcQ+lOdWA+0fSThIFxPTO5kvnC9q11E1pcDf999mHebtt/JVehGb7RvPDn 7JaJSN8NIMln40R12+4BQLEbyIQqmtMDb+0SCYSUFUvhEoVLcqSrBa8mMv+VRpJBg9X5 p+E2k2WIhiAcQvJQD8HWFoQQBeJ6J3Sz/mMMfw0UUF9IZ094ubNcB4Ercoxw7rkOmvRM ZuuPXe7dB//xFr6QqvLAxdbVTsGOqJcWxayp7ET9cLpmrzWaetamDgaGGrKh2ixkgru2 kQ== Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx07-00178001.pphosted.com with ESMTP id 2wa9usrayx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 22 Nov 2019 11:45:40 +0100 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 31F6710002A; Fri, 22 Nov 2019 11:45:40 +0100 (CET) Received: from Webmail-eu.st.com (sfhdag3node3.st.com [10.75.127.9]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id 166482B56BD; Fri, 22 Nov 2019 11:45:40 +0100 (CET) Received: from localhost (10.75.127.50) by SFHDAG3NODE3.st.com (10.75.127.9) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Fri, 22 Nov 2019 11:45:39 +0100 From: Benjamin Gaignard To: , , , , CC: , , , , Benjamin Gaignard , Fabrice Gasnier Subject: [PATCH] dt-bindings: regulator: Convert stm32 vrefbuf bindings to json-schema Date: Fri, 22 Nov 2019 11:45:36 +0100 Message-ID: <20191122104536.20283-2-benjamin.gaignard@st.com> X-Mailer: git-send-email 2.15.0 In-Reply-To: <20191122104536.20283-1-benjamin.gaignard@st.com> References: <20191122104536.20283-1-benjamin.gaignard@st.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.75.127.50] X-ClientProxiedBy: SFHDAG6NODE1.st.com (10.75.127.16) To SFHDAG3NODE3.st.com (10.75.127.9) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-11-22_02:2019-11-21,2019-11-22 signatures=0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Convert the STM32 regulator vrefbuf binding to DT schema format using json-schema Signed-off-by: Benjamin Gaignard CC: Fabrice Gasnier --- .../bindings/regulator/st,stm32-vrefbuf.txt | 20 --------- .../bindings/regulator/st,stm32-vrefbuf.yaml | 52 ++++++++++++++++++++++ 2 files changed, 52 insertions(+), 20 deletions(-) delete mode 100644 Documentation/devicetree/bindings/regulator/st,stm32-vrefbuf.txt create mode 100644 Documentation/devicetree/bindings/regulator/st,stm32-vrefbuf.yaml diff --git a/Documentation/devicetree/bindings/regulator/st,stm32-vrefbuf.txt b/Documentation/devicetree/bindings/regulator/st,stm32-vrefbuf.txt deleted file mode 100644 index 5ddb8500a929..000000000000 --- a/Documentation/devicetree/bindings/regulator/st,stm32-vrefbuf.txt +++ /dev/null @@ -1,20 +0,0 @@ -STM32 VREFBUF - Voltage reference buffer - -Some STM32 devices embed a voltage reference buffer which can be used as -voltage reference for ADCs, DACs and also as voltage reference for external -components through the dedicated VREF+ pin. - -Required properties: -- compatible: Must be "st,stm32-vrefbuf". -- reg: Offset and length of VREFBUF register set. -- clocks: Must contain an entry for peripheral clock. - -Example: - vrefbuf: regulator@58003c00 { - compatible = "st,stm32-vrefbuf"; - reg = <0x58003C00 0x8>; - clocks = <&rcc VREF_CK>; - regulator-min-microvolt = <1500000>; - regulator-max-microvolt = <2500000>; - vdda-supply = <&vdda>; - }; diff --git a/Documentation/devicetree/bindings/regulator/st,stm32-vrefbuf.yaml b/Documentation/devicetree/bindings/regulator/st,stm32-vrefbuf.yaml new file mode 100644 index 000000000000..33cdaeb25aee --- /dev/null +++ b/Documentation/devicetree/bindings/regulator/st,stm32-vrefbuf.yaml @@ -0,0 +1,52 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/regulator/st,stm32-vrefbuf.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: STMicroelectronics STM32 Voltage reference buffer bindings + +description: | + Some STM32 devices embed a voltage reference buffer which can be used as + voltage reference for ADCs, DACs and also as voltage reference for external + components through the dedicated VREF+ pin. + +maintainers: + - Fabrice Gasnier + +allOf: + - $ref: "regulator.yaml#" + +properties: + compatible: + const: st,stm32-vrefbuf + + reg: + maxItems: 1 + + clocks: + maxItems: 1 + + vdda-supply: + description: phandle to the vdda input analog voltage. + +required: + - compatible + - reg + - clocks + - vdda-supply + +examples: + - | + #include + vrefbuf@50025000 { + compatible = "st,stm32-vrefbuf"; + reg = <0x50025000 0x8>; + regulator-min-microvolt = <1500000>; + regulator-max-microvolt = <2500000>; + clocks = <&rcc VREF>; + vdda-supply = <&vdda>; + }; + +... + -- 2.15.0