All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Linus Walleij	 <linus.walleij@linaro.org>,
	Cosmin Tanislav <cosmin.tanislav@analog.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-gpio@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v2 0/7] iio: convert GPIO chips to using new value setters
Date: Sat, 12 Apr 2025 12:32:53 +0100	[thread overview]
Message-ID: <20250412123253.28a99570@jic23-huawei> (raw)
In-Reply-To: <a160ad15944f28159a0d1145cdf4584fb2972d6d.camel@gmail.com>

On Wed, 09 Apr 2025 15:08:24 +0100
Nuno Sá <noname.nuno@gmail.com> wrote:

> On Wed, 2025-04-09 at 10:40 +0200, Bartosz Golaszewski wrote:
> > struct gpio_chip now has callbacks for setting line values that return
> > an integer, allowing to indicate failures. We're in the process of
> > converting all GPIO drivers to using the new API. This series converts
> > all the IIO GPIO controllers and also contains some additional
> > refactoring patches for ad5592r in preparation for the conversion.
> > 
> > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> > ---  
> 
> LGTM,
> 
> Reviewed-by: Nuno Sá <nuno.sa@analog.com>
> 
Applied with that tweak to patch 2.
Pushed out initially as testing for the build bots to poke at it some more.

Jonathan

> > Changes in v2:
> > - move devm_mutex_init() earlier in probe() to avoid using a goto
> > - rework returning on error in ad5592r_set_channel_modes(): return
> >   immediately instead of saving the return value and going to the bottom
> >   of the function
> > - use scoped_guard() in one more place to fix a build warning reported
> >   by the build bot
> > - Link to v1:
> > https://lore.kernel.org/r/20250407-gpiochip-set-rv-iio-v1-0-8431b003a145@linaro.org
> > 
> > ---
> > Bartosz Golaszewski (7):
> >       iio: dac: ad5592r: destroy mutexes in detach paths
> >       iio: dac: ad5592r: use lock guards
> >       iio: dac: ad5592r: use new GPIO line value setter callbacks
> >       iio: adc: ti-ads7950: use new GPIO line value setter callbacks
> >       iio: adc: ad4130: use new GPIO line value setter callbacks
> >       iio: addac: ad74413r: use new GPIO line value setter callbacks
> >       iio: addac: ad74115: use new GPIO line value setter callbacks
> > 
> >  drivers/iio/adc/ad4130.c       |  10 +--
> >  drivers/iio/adc/ti-ads7950.c   |  17 +++--
> >  drivers/iio/addac/ad74115.c    |  18 +++--
> >  drivers/iio/addac/ad74413r.c   |  28 ++++----
> >  drivers/iio/dac/ad5592r-base.c | 147 ++++++++++++++++++----------------------
> > -
> >  5 files changed, 103 insertions(+), 117 deletions(-)
> > ---
> > base-commit: 0af2f6be1b4281385b618cb86ad946eded089ac8
> > change-id: 20250401-gpiochip-set-rv-iio-b064ce43791d
> > 
> > Best regards,  


      reply	other threads:[~2025-04-12 11:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09  8:40 [PATCH v2 0/7] iio: convert GPIO chips to using new value setters Bartosz Golaszewski
2025-04-09  8:40 ` [PATCH v2 1/7] iio: dac: ad5592r: destroy mutexes in detach paths Bartosz Golaszewski
2025-04-09  8:40 ` [PATCH v2 2/7] iio: dac: ad5592r: use lock guards Bartosz Golaszewski
2025-04-12 11:31   ` Jonathan Cameron
2025-04-09  8:40 ` [PATCH v2 3/7] iio: dac: ad5592r: use new GPIO line value setter callbacks Bartosz Golaszewski
2025-04-09  8:40 ` [PATCH v2 4/7] iio: adc: ti-ads7950: " Bartosz Golaszewski
2025-04-09  8:40 ` [PATCH v2 5/7] iio: adc: ad4130: " Bartosz Golaszewski
2025-04-09  8:40 ` [PATCH v2 6/7] iio: addac: ad74413r: " Bartosz Golaszewski
2025-04-09  8:40 ` [PATCH v2 7/7] iio: addac: ad74115: " Bartosz Golaszewski
2025-04-09 14:08 ` [PATCH v2 0/7] iio: convert GPIO chips to using new value setters Nuno Sá
2025-04-12 11:32   ` 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=20250412123253.28a99570@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=cosmin.tanislav@analog.com \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noname.nuno@gmail.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 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.