From: Jonathan Cameron <jic23@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Peter Rosin <peda@axentia.se>,
Naresh Solanki <naresh.solanki@9elements.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
mazziesaccount@gmail.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: iio: afe: voltage-divider: Add io-channel-cells
Date: Sat, 27 Jan 2024 16:55:42 +0000 [thread overview]
Message-ID: <20240127165542.6eeb23e9@jic23-huawei> (raw)
In-Reply-To: <20240127-capitol-cabbage-7a9b67112a28@spud>
On Sat, 27 Jan 2024 16:48:04 +0000
Conor Dooley <conor@kernel.org> wrote:
> On Sat, Jan 27, 2024 at 02:49:20PM +0000, Jonathan Cameron wrote:
>
> > > > It's all in the description of the binding...
> > >
> > > Obviously it was not sufficiently clear, it's not as if I didn't look at
> > > it...
> >
> > Given this device fits in both categories, perhaps a tiny bit of
> > additional documentation would help?
>
> That would be nice.
>
> > '#io-channels-cells':
> > description:
> > In addition to consuming the measurement services of an ADC,
> > the voltage divider can act as an provider of measurement
> > services to other devices.
> > const: 1
>
> But I am not sure that that covers things. I think an example, like
> Peter gave, would be good?
Ok. An example is fine.
next prev parent reply other threads:[~2024-01-27 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 11:55 [PATCH] dt-bindings: iio: afe: voltage-divider: Add io-channel-cells Naresh Solanki
2024-01-26 16:16 ` Conor Dooley
2024-01-26 16:25 ` Naresh Solanki
2024-01-26 16:51 ` Conor Dooley
2024-01-26 17:40 ` Naresh Solanki
2024-01-26 22:14 ` Conor Dooley
2024-01-27 9:40 ` Peter Rosin
2024-01-27 11:03 ` Conor Dooley
2024-01-27 14:49 ` Jonathan Cameron
2024-01-27 16:48 ` Conor Dooley
2024-01-27 16:55 ` Jonathan Cameron [this message]
2024-01-26 22:16 ` Peter Rosin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240127165542.6eeb23e9@jic23-huawei \
--to=jic23@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=naresh.solanki@9elements.com \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.