Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp2446955pxv; Sat, 3 Jul 2021 09:01:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw9XAG0IdqlTqkBXXdvuEqnyYt76mmvZrrVU9iwtd5ZJf2GNL8RcHlni6TlZL1qwexWQapd X-Received: by 2002:aa7:d48f:: with SMTP id b15mr5943425edr.7.1625328118273; Sat, 03 Jul 2021 09:01:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1625328118; cv=none; d=google.com; s=arc-20160816; b=cz4dCSRCuG8uLamuWWMVW4ZwHMFTC6/r/7ukjelbWUOBVKvON3DUeKNwRGO/sKADS+ kF/sqw0TIpVNa1s2Z5pV4I4Cmf3wII+RptWD838hIvM8Gf4gypSx5nl74kfEIrdLtj3d G3KD0hRdywtA3/1KguKnnK1AIhdh9IpKGh93Iy0VXyp5+fXtbAm+IMvLJKKKhWUc/gBj AIY3DPC88QrvXuARpw/V7GmYKxv1GmLA9toHLGEwKQ4fIapi8P/fBYv/ux7eQ//hqsjc BBeWpEWsmwE6OPQ8RjiLz53NioygSKdGRO+oF4dS8C2b7hx/d4Cd8DEy8yKAnMt2tX/O TMJQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=vuqLW/B3jl6EpGAHSUcxrgLiBqVSZmhpw7PArSYNthM=; b=zhIlFeKphqMuHjQ+afnDonk5Rhtw3Cvrjsw3rg27vfuTlUt79qcUNEnji9HpZiE0LF f8sjvlH4eEgd662qEuYoxPpflERD1t3lCObqfQCVpFbNDytdJX5P8tNz7P2kKTVyetqY BuzhsdsNKy+lkdxDp+ka1pRTIwYxTX70pncBIFvJ1oO7xP8rNZ6pHqpRqRY7z5rbT8pE dNwOMZbLJd7Ok6rykBYuwkFLmLtQYHNFU1pWFh1VUhq6HflmeECZuMyyEYiyDEBCqlui PBHL7eapwLnuIJY88xgkoXKs9OkNdHfZszg+qFtqHyrHfJcbdnVszvajforhjqx5qt9F xqhg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v21si291680edx.3.2021.07.03.09.01.35; Sat, 03 Jul 2021 09:01:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230012AbhGCQCz (ORCPT + 99 others); Sat, 3 Jul 2021 12:02:55 -0400 Received: from mail.kernel.org ([198.145.29.99]:39890 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229818AbhGCQCy (ORCPT ); Sat, 3 Jul 2021 12:02:54 -0400 Received: from jic23-huawei (cpc108967-cmbg20-2-0-cust86.5-4.cable.virginm.net [81.101.6.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 33CA961935; Sat, 3 Jul 2021 16:00:19 +0000 (UTC) Date: Sat, 3 Jul 2021 17:02:45 +0100 From: Jonathan Cameron To: Andreas Kemnade Cc: lee.jones@linaro.org, robh+dt@kernel.org, lars@metafoo.de, sre@kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org, linux-pm@vger.kernel.org, leonard.crestez@nxp.com, letux-kernel@openphoenux.org Subject: Re: [PATCH 1/4] dt-bindings: mfd: ricoh,rn5t618: ADC related nodes and properties Message-ID: <20210703170245.1d310342@jic23-huawei> In-Reply-To: <20210703084224.31623-2-andreas@kemnade.info> References: <20210703084224.31623-1-andreas@kemnade.info> <20210703084224.31623-2-andreas@kemnade.info> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 3 Jul 2021 10:42:21 +0200 Andreas Kemnade wrote: > Add ADC related nodes and properties. This will allow to wire > up ADC channels to consumers, especially to measure input voltages > by the power subdevice. > > Signed-off-by: Andreas Kemnade > --- > .../bindings/mfd/ricoh,rn5t618.yaml | 53 +++++++++++++++++++ > 1 file changed, 53 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mfd/ricoh,rn5t618.yaml b/Documentation/devicetree/bindings/mfd/ricoh,rn5t618.yaml > index 032a7fb0b4a7..185f87a14a54 100644 > --- a/Documentation/devicetree/bindings/mfd/ricoh,rn5t618.yaml > +++ b/Documentation/devicetree/bindings/mfd/ricoh,rn5t618.yaml > @@ -73,6 +73,48 @@ properties: > description: | > See Documentation/devicetree/bindings/power/power-controller.txt > > + adc: > + type: object > + > + properties: > + compatible: > + enum: > + - ricoh,rn5t618-adc > + - ricoh,rc5t619-adc > + > + "#io-channel-cells": > + const: 1 > + > + additionalProperties: false > + > + required: > + - compatible > + - "#io-channel-cells" Strictly required? If not used below (where it is optional) then why do we require the ADC driver to provided the services? I don't mind you leave it as it is though if you prefer - it doesn't do any harm! > + > + power: > + type: object > + > + properties: > + compatible: > + enum: > + - ricoh,rn5t618-power > + - ricoh,rc5t619-power > + > + io-channels: > + items: > + - description: ADP Voltage Channel > + - description: USB Voltage Channel > + > + io-channel-names: > + items: > + - const: vadp > + - const: vusb > + > + additionalProperties: false > + > + required: > + - compatible > + > regulators: > type: object > > @@ -96,6 +138,17 @@ examples: > interrupts = <11 IRQ_TYPE_EDGE_FALLING>; > system-power-controller; > > + rn5t618_adc: adc { > + compatible = "ricoh,rn5t618-adc"; > + #io-channel-cells = <1>; > + }; > + > + power { > + compatible = "ricoh,rn5t618-power"; > + io-channels = <&rn5t618_adc 2>, <&rn5t618_adc 3>; > + io-channel-names = "vadp", "vusb"; > + }; > + > regulators { > DCDC1 { > regulator-min-microvolt = <1050000>;