From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Matti Vaittinen" <mazziesaccount@gmail.com>,
"Matti Vaittinen" <matti.vaittinen@fi.rohmeurope.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>,
"David Heidelberg" <david@ixit.cz>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Sukrut Bellary" <sbellary@baylibre.com>,
"Lothar Rubusch" <l.rubusch@gmail.com>
Subject: Re: [PATCH v2 0/4] Support ROHM BD7910[0,1,2,3]
Date: Mon, 18 Aug 2025 20:12:56 +0100 [thread overview]
Message-ID: <20250818201256.7be1092c@jic23-huawei> (raw)
In-Reply-To: <8127b81f-d2a1-4dfc-b8c6-45615ba9e431@baylibre.com>
On Mon, 18 Aug 2025 13:46:12 -0500
David Lechner <dlechner@baylibre.com> wrote:
> On 8/18/25 1:19 PM, Jonathan Cameron wrote:
> > On Mon, 18 Aug 2025 11:11:56 +0300
> > Matti Vaittinen <mazziesaccount@gmail.com> wrote:
> >
> >> Add support for ROHM BD7910[0,1,2,3] ADCs.
> >>
> >> The ROHM BD79100, BD79101, BD79102 and BD79103 are ADCs derived from the
> >> BD79104. According to the data-sheets, the BD79103 is compatible with the
> >> BD79104. Rest of the ICs have different number of analog input channels.
> >>
> >> This series adds support for these ICs using the ti-adc128s052.c.
> >>
> >> NOTE: There has been work on couple of other patch series [1][2] touching
> >> this same driver. I haven't considered those changes because, AFAICS,
> >> there has been no new revisions of these series since mid June.
> >>
> >> [1]: https://lore.kernel.org/all/20250614091504.575685-1-sbellary@baylibre.com/
> >> [2]: https://lore.kernel.org/all/20250625170218.545654-2-l.rubusch@gmail.com/
> >
> > Pretty simple replies to the changes requested in v1 reviews and nice and clean
> > so I'll gamble (a tiny bit) that everyone is happy with this and at least
> > queue it up for build testing.
> >
> Reviewed-by: David Lechner <dlechner@baylibre.com>
>
Thanks. Added to the 3 you hadn't tagged already.
prev parent reply other threads:[~2025-08-18 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 8:11 [PATCH v2 0/4] Support ROHM BD7910[0,1,2,3] Matti Vaittinen
2025-08-18 8:12 ` [PATCH v2 1/4] dt-bindings: iio: adc: Add BD7910[0,1,2,3] Matti Vaittinen
2025-08-18 17:07 ` Conor Dooley
2025-08-18 8:12 ` [PATCH v2 2/4] iio: adc: adc128s052: Simplify matching chip_data Matti Vaittinen
2025-08-18 8:12 ` [PATCH v2 3/4] iio: adc: adc128s052: Rename channel structs Matti Vaittinen
2025-08-18 8:13 ` [PATCH v2 4/4] iio: adc: adc128s052: Support ROHM BD7910[0,1,2,3] Matti Vaittinen
2025-08-18 18:19 ` [PATCH v2 0/4] " Jonathan Cameron
2025-08-18 18:46 ` David Lechner
2025-08-18 19:12 ` Jonathan Cameron [this message]
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=20250818201256.7be1092c@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=l.rubusch@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=sbellary@baylibre.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