All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: David Lechner <dlechner@baylibre.com>
Cc: Jonathan Cameron <jic23@kernel.org>, <linux-iio@vger.kernel.org>,
	"Peter Zijlstra" <peterz@infradead.org>
Subject: Re: [PATCH 02/10] iio: dummy: Use automatic lock and direct mode cleanup.
Date: Mon, 29 Jan 2024 11:46:22 +0000	[thread overview]
Message-ID: <20240129114622.00007e1c@Huawei.com> (raw)
In-Reply-To: <CAMknhBFzuoQQDbfJjUkDd8udAkRzhsM_Vs-FyEmaAE_k6QXk3Q@mail.gmail.com>

> > @@ -436,10 +431,10 @@ static int iio_dummy_write_raw(struct iio_dev *indio_dev,
> >                         if (chan->output == 0)
> >                                 return -EINVAL;
> >
> > -                       /* Locking not required as writing single value */
> > -                       mutex_lock(&st->lock);
> > -                       st->dac_val = val;
> > -                       mutex_unlock(&st->lock);
> > +                       scoped_guard(mutex, &st->lock) {
> > +                               /* Locking not required as writing single value */
> > +                               st->dac_val = val;
> > +                       }
> >                         return 0;
> >                 default:
> >                         return -EINVAL;
> > @@ -447,9 +442,9 @@ static int iio_dummy_write_raw(struct iio_dev *indio_dev,
> >         case IIO_CHAN_INFO_PROCESSED:
> >                 switch (chan->type) {
> >                 case IIO_STEPS:
> > -                       mutex_lock(&st->lock);
> > -                       st->steps = val;
> > -                       mutex_unlock(&st->lock);
> > +                       scoped_guard(mutex, &st->lock) {
> > +                               st->steps = val;
> > +                       }
> >                         return 0;
> >                 case IIO_ACTIVITY:
> >                         if (val < 0)
> > @@ -470,30 +465,29 @@ static int iio_dummy_write_raw(struct iio_dev *indio_dev,
> >                 default:
> >                         return -EINVAL;
> >                 }
> > -       case IIO_CHAN_INFO_CALIBSCALE:
> > -               mutex_lock(&st->lock);
> > +       case IIO_CHAN_INFO_CALIBSCALE: {
> > +               guard(mutex)(&st->lock);
> >                 /* Compare against table - hard matching here */
> >                 for (i = 0; i < ARRAY_SIZE(dummy_scales); i++)
> >                         if (val == dummy_scales[i].val &&
> >                             val2 == dummy_scales[i].val2)
> >                                 break;
> >                 if (i == ARRAY_SIZE(dummy_scales))
> > -                       ret = -EINVAL;
> > -               else
> > -                       st->accel_calibscale = &dummy_scales[i];
> > -               mutex_unlock(&st->lock);
> > +                       return  -EINVAL;
> > +               st->accel_calibscale = &dummy_scales[i];
> >                 return ret;  
> 
> Can we change this to `return 0;` and get rid of the `ret = 0`
> initialization at the beginning of the function?

Yes. That would make sense.

> 
> > +       }


  reply	other threads:[~2024-01-29 11:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-28 15:05 [PATCH 00/10] IIO: Use the new cleanup.h magic Jonathan Cameron
2024-01-28 15:05 ` [PATCH 01/10] iio: locking: introduce __cleanup() based direct mode claiming infrastructure Jonathan Cameron
2024-02-04 16:26   ` andy.shevchenko
2024-02-04 17:42     ` Jonathan Cameron
2024-01-28 15:05 ` [PATCH 02/10] iio: dummy: Use automatic lock and direct mode cleanup Jonathan Cameron
2024-01-28 21:52   ` David Lechner
2024-01-29 11:46     ` Jonathan Cameron [this message]
2024-01-29 19:58       ` Jonathan Cameron
2024-01-29 20:05         ` David Lechner
2024-02-04 16:29   ` andy.shevchenko
2024-02-04 17:41     ` Jonathan Cameron
2024-01-28 15:05 ` [PATCH 03/10] iio: accel: adxl367: Use automated cleanup for locks and iio direct mode Jonathan Cameron
2024-01-30 12:53   ` Nuno Sá
2024-02-04 13:48     ` Jonathan Cameron
2024-02-05  8:27       ` Nuno Sá
2024-01-28 15:05 ` [PATCH 04/10] iio: imu: bmi323: Use cleanup handling for iio_device_claim_direct_mode() Jonathan Cameron
2024-01-28 15:05 ` [PATCH 05/10] iio: adc: max1363: Use automatic cleanup for locks and iio mode claiming Jonathan Cameron
2024-01-28 15:05 ` [PATCH 06/10] iio: proximity: sx9360: Use automated cleanup for locks and IIO " Jonathan Cameron
2024-01-28 15:05 ` [PATCH 07/10] iio: proximity: sx9324: " Jonathan Cameron
2024-01-28 15:05 ` [PATCH 08/10] iio: proximity: sx9310: " Jonathan Cameron
2024-01-28 15:05 ` [PATCH 09/10] iio: adc: ad4130: Use automatic cleanup of locks and direct mode Jonathan Cameron
2024-01-28 15:05 ` [PATCH 10/10] iio: adc: ad7091r-base: Use auto cleanup of locks Jonathan Cameron
2024-01-30 14:08 ` [PATCH 00/10] IIO: Use the new cleanup.h magic Nuno Sá
2024-02-04 16:06   ` Jonathan Cameron

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=20240129114622.00007e1c@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=peterz@infradead.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 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.