Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp4449368ybl; Mon, 9 Dec 2019 11:00:53 -0800 (PST) X-Google-Smtp-Source: APXvYqx+Xkcx8rvWYPG4i73XXOpVDoknITVpmct/lLKcP49WVILD5m0Vfq9FuFf9yvt+mqjfQUDY X-Received: by 2002:a9d:1c8:: with SMTP id e66mr11968346ote.354.1575918053359; Mon, 09 Dec 2019 11:00:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575918053; cv=none; d=google.com; s=arc-20160816; b=NEONsMVjgR72trfRt7A8Dy1oVirygv+coaMqHI50uPcZKv6JUBqDW2Nf/y3OV6L19z NL6mwtSKS0DN7G5E9viXmonREqyQlrCxIXM+iNM7qVldGYsmbyrid4LGM3t07zXDwTVq VYeIA/k+murujNlPPf5xrCnqgOwb15O4G0K8NLXgncVV59EUmfoCDqa/tEvyoKbGd0AW rL8WwzymtsMUHSSKRfniUDV6kUEyk7tcOo3RWexZVYB30NE66//ragy+KC/mZdRh0pTG kiz08JzwlL2wB/DckDiqGsDVs4U3+8mMQUfSAr0GOGxa5TR5zA26lIzh4CSdDbRRLwYC IaHg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:in-reply-to:subject:cc:to:from :date; bh=M/fBd/JBvu8kQrS+EN5f4218hKsxLK6ozrBze96wFQY=; b=fDC518DfGukF/6IruS7ztRhxd1p0bohrYq3qxSw7fhz5QWMb3XU2O9tYiKQoGttgyn CnVhNpUCTiIB9hxrLbgjRQevQ7hEFMVZlDgwcQdQIV66wgtvtu3pXAF+qvZzH+eTeXfe l+dY3wwg2TRErdMFXm34Qf9ZXVXE5k2ury7YbLUDXEvq94pO0jkszcFtXQbe9oNI91Kk 8aXZ2paTM7nAYdhjnP2lCm+6B2G6qKykBOluhPD+Qg12/5k2hMSfO4Jt4OjT7AEuXkSS QQqIcJ1g0wa8oRqySSsG5/T6BSE9n8MRhJFWmx7WhMY+A6o1EekQoMQU3mqvhs5zxdpX zEAQ== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l14si452726otb.108.2019.12.09.11.00.40; Mon, 09 Dec 2019 11:00:53 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726951AbfLITAD (ORCPT + 99 others); Mon, 9 Dec 2019 14:00:03 -0500 Received: from foss.arm.com ([217.140.110.172]:42572 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726365AbfLITAC (ORCPT ); Mon, 9 Dec 2019 14:00:02 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id A89B013FD; Mon, 9 Dec 2019 11:00:01 -0800 (PST) Received: from localhost (unknown [10.37.6.21]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 268113F6CF; Mon, 9 Dec 2019 11:00:01 -0800 (PST) Date: Mon, 09 Dec 2019 18:59:59 +0000 From: Mark Brown To: Benjamin Gaignard Cc: alexandre.torgue@st.com, broonie@kernel.org, devicetree@vger.kernel.org, Fabrice Gasnier , lgirdwood@gmail.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, Mark Brown , mark.rutland@arm.com, robh+dt@kernel.org Subject: Applied "dt-bindings: regulator: Convert stm32 vrefbuf bindings to json-schema" to the regulator tree In-Reply-To: <20191122104536.20283-2-benjamin.gaignard@st.com> Message-Id: X-Patchwork-Hint: ignore Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The patch dt-bindings: regulator: Convert stm32 vrefbuf bindings to json-schema has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.6 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark From 21b2c47161449c44e5a70eab646260aaeceb331c Mon Sep 17 00:00:00 2001 From: Benjamin Gaignard Date: Fri, 22 Nov 2019 11:45:36 +0100 Subject: [PATCH] dt-bindings: regulator: Convert stm32 vrefbuf bindings to json-schema Convert the STM32 regulator vrefbuf binding to DT schema format using json-schema Signed-off-by: Benjamin Gaignard CC: Fabrice Gasnier Reviewed-by: Rob Herring Link: https://lore.kernel.org/r/20191122104536.20283-2-benjamin.gaignard@st.com Signed-off-by: Mark Brown --- .../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.20.1