From: Conor Dooley <conor@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: iio: adc: Add ROHM BD79100G
Date: Tue, 13 May 2025 15:39:42 +0100 [thread overview]
Message-ID: <20250513-unpaid-detection-f45c9a06b4c6@spud> (raw)
In-Reply-To: <20250513-coconut-reconfirm-b90590efeb45@spud>
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
On Tue, May 13, 2025 at 03:39:11PM +0100, Conor Dooley wrote:
> On Tue, May 13, 2025 at 11:26:27AM +0300, Matti Vaittinen wrote:
> > The ROHM BD79100G is a 12-bit ADC which can be read over SPI. Device has
> > no MOSI pin. ADC results can be read from MISO by clocking in 16 bits.
> > The 4 leading bits will be zero, last 12 containig the data.
>
> I think it is probably worth mentioning why a rohm device is going into
> this binding (clone?) and that the 12-bit thing is a differentiator that
> is why you're not using a fallback.
Sent too soon, meant to say: with that
Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
> >
> > Device has only VCC supply pin, which acts also as a VFS, determining the
> > voltage for full 12-bits. Specifying it is mandatory.
> >
> > Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
> > ---
> > Documentation/devicetree/bindings/iio/adc/adi,ad7476.yaml | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad7476.yaml b/Documentation/devicetree/bindings/iio/adc/adi,ad7476.yaml
> > index 44c671eeda73..10fb6e14c2d0 100644
> > --- a/Documentation/devicetree/bindings/iio/adc/adi,ad7476.yaml
> > +++ b/Documentation/devicetree/bindings/iio/adc/adi,ad7476.yaml
> > @@ -46,6 +46,7 @@ properties:
> > - ti,ads7867
> > - ti,ads7868
> > - lltc,ltc2314-14
> > + - rohm,bu79100g
> >
> > reg:
> > maxItems: 1
> > @@ -96,6 +97,7 @@ allOf:
> > - ti,adc121s
> > - ti,ads7866
> > - ti,ads7868
> > + - rohm,bu79100g
> > then:
> > required:
> > - vcc-supply
> > --
> > 2.49.0
> >
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-05-13 14:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 8:26 [PATCH 0/2] Support ROHM BU79100G ADC Matti Vaittinen
2025-05-13 8:26 ` [PATCH 1/2] dt-bindings: iio: adc: Add ROHM BD79100G Matti Vaittinen
2025-05-13 14:39 ` Conor Dooley
2025-05-13 14:39 ` Conor Dooley [this message]
2025-05-14 5:36 ` Matti Vaittinen
2025-05-14 6:00 ` Matti Vaittinen
2025-05-13 8:26 ` [PATCH 2/2] iio: adc: ad7476: Support ROHM BU79100G Matti Vaittinen
2025-05-14 7:38 ` Matti Vaittinen
2025-05-14 9:21 ` Matti Vaittinen
2025-05-15 17:06 ` Jonathan Cameron
2025-05-26 6:17 ` Matti Vaittinen
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=20250513-unpaid-detection-f45c9a06b4c6@spud \
--to=conor@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).