From: Jonathan Cameron <jic23@kernel.org>
To: "David Lechner (TI)" <dlechner@baylibre.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Linus Walleij" <linusw@kernel.org>,
"Bartosz Golaszewski" <brgl@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, "Chris Hall" <c-hall@ti.com>,
"Patrick Edwards" <pedwards@ti.com>,
"Kurt Borja" <kuurtb@gmail.com>
Subject: Re: [PATCH v2 0/2] iio: adc: ti-ads112c14: add gpio support
Date: Sun, 18 Oct 2026 02:58:36 +0100 [thread overview]
Message-ID: <20261018025836.00de5da4@jic23-hlaptop> (raw)
In-Reply-To: <20261009-iio-adc-ti-ads112c14-gpio-v2-0-3231a795fa63@baylibre.com>
On Fri, 09 Oct 2026 18:25:50 -0500
"David Lechner (TI)" <dlechner@baylibre.com> wrote:
> Add GPIO controller support to the TI ADS112C14 driver. The first patch
> is a small cleanup to make the GPIO register field macros usable with a
> GPIO offset. The second patch adds the GPIO support.
>
> Signed-off-by: David Lechner (TI) <dlechner@baylibre.com>
I took a look and have nothing to add to existing discussion points.
So from my point of view waiting for a slightly tweaked v3.
(At least Bartosz' first comment + whatever outcome of discussion is)
Thanks,
Jonathan
prev parent reply other threads:[~2026-10-18 1:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 23:25 David Lechner (TI)
2026-10-09 23:25 ` [PATCH v2 1/2] iio: adc: ti-ads112c14: parameterize GPIO register field macros David Lechner (TI)
2026-10-10 9:00 ` Bartosz Golaszewski
2026-10-09 23:25 ` [PATCH v2 2/2] iio: adc: ti-ads112c14: add gpio support David Lechner (TI)
2026-10-10 9:00 ` Bartosz Golaszewski
2026-10-10 13:46 ` David Lechner
2026-10-13 14:05 ` Andy Shevchenko
2026-10-15 13:01 ` David Lechner
2026-10-15 13:37 ` Andy Shevchenko
2026-10-15 14:04 ` David Lechner
2026-10-15 18:16 ` Andy Shevchenko
2026-10-13 14:07 ` Andy Shevchenko
2026-10-15 13:02 ` David Lechner
2026-10-18 1:58 ` 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=20261018025836.00de5da4@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=brgl@kernel.org \
--cc=c-hall@ti.com \
--cc=dlechner@baylibre.com \
--cc=kuurtb@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=pedwards@ti.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
all inboxes | Powered by JetHome®