From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Matti Vaittinen" <matti.vaittinen@fi.rohmeurope.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Marcelo Schmitt" <marcelo.schmitt@analog.com>,
"Javier Carrasco" <javier.carrasco.cruz@gmail.com>,
"Tobias Sperling" <tobias.sperling@softing.com>,
"Antoniu Miclaus" <antoniu.miclaus@analog.com>,
"Trevor Gamblin" <tgamblin@baylibre.com>,
"Esteban Blanc" <eblanc@baylibre.com>,
"Ramona Alexandra Nechita" <ramona.nechita@analog.com>,
"Hans de Goede" <hansg@kernel.org>,
"Herve Codina" <herve.codina@bootlin.com>,
"Alisa-Dariana Roman" <alisadariana@gmail.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: iio: adc: ROHM BD79112 ADC/GPIO
Date: Sun, 7 Sep 2025 15:37:39 +0300 [thread overview]
Message-ID: <69eb8aaf-2ab4-4e54-89cf-1be51a616258@gmail.com> (raw)
In-Reply-To: <20250907121911.7c2fa1cb@jic23-huawei>
On 07/09/2025 14:19, Jonathan Cameron wrote:
> On Fri, 5 Sep 2025 09:42:18 +0300
> Matti Vaittinen <mazziesaccount@gmail.com> wrote:
>
>> The ROHM BD79112 is an ADC/GPIO with 32 channels. The channel inputs can
>> be used as ADC or GPIO. Using the GPIOs as IRQ sources isn't supported.
>>
>> The ADC is 12-bit, supporting input voltages up to 5.7V, and separate I/O
>> voltage supply. Maximum SPI clock rate is 20 MHz (10 MHz with
>> daisy-chain configuration) and maximum sampling rate is 1MSPS.
>>
>> Add a device tree binding document for the ROHM BD79112.
>>
>> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
>> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
> Trivial comment below. If everything else is good on this version
> it isn't worth a respin.
>
>> +examples:
>> + - |
>> + spi {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + adc: adc@0 {
>> + compatible = "rohm,bd79112";
>> + reg = <0x0>;
>> +
>> + spi-cpha;
>> + spi-cpol;
>> +
>> + vdd-supply = <&dummyreg>;
>> + iovdd-supply = <&dummyreg>;
>> +
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + gpio-controller;
>> + #gpio-cells = <2>;
>> +
>> + channel@0 {
>> + reg = <0>;
>> + };
>> + channel@1 {
>> + reg = <1>;
>> + };
>> + channel@2 {
>> + reg = <2>;
>> + };
>> + channel@3 {
>> + reg = <3>;
> Trivial point but I get bored scrolling.
> Would a smaller set of channels allow you to provide same level
> of testing / documentation?
I suppose yes. Trimming this to maybe 3 channels would be just fine.
I'll re-spin the series anyways so I'll crop this too.
Yours,
-- Matti
next prev parent reply other threads:[~2025-09-07 12:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 6:41 [PATCH v3 0/3] Support ROHM BD79112 ADC Matti Vaittinen
2025-09-05 6:42 ` [PATCH v3 1/3] dt-bindings: iio: adc: ROHM BD79112 ADC/GPIO Matti Vaittinen
2025-09-05 8:10 ` Linus Walleij
2025-09-07 11:19 ` Jonathan Cameron
2025-09-07 12:37 ` Matti Vaittinen [this message]
2025-09-05 6:42 ` [PATCH v3 2/3] iio: adc: Support " Matti Vaittinen
2025-09-05 6:54 ` Andy Shevchenko
2025-09-05 7:10 ` Matti Vaittinen
2025-09-05 12:53 ` Andy Shevchenko
2025-09-07 11:33 ` Jonathan Cameron
2025-09-07 11:42 ` Jonathan Cameron
2025-09-07 20:55 ` Andy Shevchenko
2025-09-08 5:10 ` Matti Vaittinen
2025-09-09 16:24 ` Jonathan Cameron
2025-09-08 20:01 ` kernel test robot
2025-09-05 6:42 ` [PATCH v3 3/3] MAINTAINERS: Support ROHM BD79112 ADC 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=69eb8aaf-2ab4-4e54-89cf-1be51a616258@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=alisadariana@gmail.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=eblanc@baylibre.com \
--cc=hansg@kernel.org \
--cc=herve.codina@bootlin.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt@analog.com \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=nuno.sa@analog.com \
--cc=ramona.nechita@analog.com \
--cc=robh@kernel.org \
--cc=tgamblin@baylibre.com \
--cc=tobias.sperling@softing.com \
/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).