From: Jonathan Cameron <jic23@kernel.org>
To: andy.shevchenko@gmail.com
Cc: linux-iio@vger.kernel.org, David Lechner <dlechner@baylibre.com>,
Peter Zijlstra <peterz@infradead.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH 02/10] iio: dummy: Use automatic lock and direct mode cleanup.
Date: Sun, 4 Feb 2024 17:41:47 +0000 [thread overview]
Message-ID: <20240204174147.19c5a334@jic23-huawei> (raw)
In-Reply-To: <Zb-7ZUbZ65G-LoNW@surfacebook.localdomain>
On Sun, 4 Feb 2024 18:29:25 +0200
andy.shevchenko@gmail.com wrote:
> Sun, Jan 28, 2024 at 03:05:29PM +0000, Jonathan Cameron kirjoitti:
> > From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> >
> > Given we now have iio_device_claim_direct_scoped() to perform automatic
> > releasing of direct mode at exit from the scope that follows it, this can
> > be used in conjunction with guard(mutex) etc remove a lot of special case
> > handling.
> >
> > Note that in this particular example code, there is no real reason you can't
> > read channels via sysfs at the same time as filling the software buffer.
> > To make it look more like a real driver constrain raw and processed
> > channel reads from occurring whilst the buffer is in use.
>
> ...
>
> > + iio_device_claim_direct_scoped(return -EBUSY, indio_dev) {
> > + guard(mutex)(&st->lock);
> > + switch (chan->type) {
> > + case IIO_VOLTAGE:
> > + if (chan->output) {
> > + /* Set integer part to cached value */
> > + *val = st->dac_val;
> > + return IIO_VAL_INT;
> > + } else if (chan->differential) {
> > + if (chan->channel == 1)
> > + *val = st->differential_adc_val[0];
> > + else
> > + *val = st->differential_adc_val[1];
> > + return IIO_VAL_INT;
> > + } else {
> > + *val = st->single_ended_adc_val;
> > + return IIO_VAL_INT;
> > + }
>
> Now you may go further and use only single return statement here.
True though this is an example driver and it's only really coincidence those returns
are the same so I'd rather keep it as explicitly matching *val with the return.
>
> > + case IIO_ACCEL:
> > + *val = st->accel_val;
> > + return IIO_VAL_INT;
> > + default:
> > + return -EINVAL;
> > }
>
> ...
>
> > + unreachable();
>
> Hmm... Is it really required? Why?
Try compiling without it. (I'm running with C=1 W=1 but think this will show up anyway.
Seems it can't tell we never leave the for loop.
>
In file included from ./include/linux/preempt.h:11,
from ./include/linux/spinlock.h:56,
from ./include/linux/mmzone.h:8,
from ./include/linux/gfp.h:7,
from ./include/linux/slab.h:16,
from drivers/iio/dummy/iio_simple_dummy.c:15:
drivers/iio/dummy/iio_simple_dummy.c: In function ‘iio_dummy_read_raw’:
./include/linux/cleanup.h:173:9: warning: this statement may fall through [-Wimplicit-fallthrough=]
173 | for (CLASS(_name, scope)(args), \
| ^~~
./include/linux/iio/iio.h:667:9: note: in expansion of macro ‘scoped_cond_guard’
667 | scoped_cond_guard(iio_claim_direct_try, fail, iio_dev)
| ^~~~~~~~~~~~~~~~~
drivers/iio/dummy/iio_simple_dummy.c:289:17: note: in expansion of macro ‘iio_device_claim_direct_scoped’
289 | iio_device_claim_direct_scoped(return -EBUSY, indio_dev) {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/iio/dummy/iio_simple_dummy.c:316:9: note: here
316 | case IIO_CHAN_INFO_PROCESSED:
| ^~~~
> ...
>
> P.S> I hope you are using --histogram diff algo when preparing patches.
>
next prev parent reply other threads:[~2024-02-04 17:41 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
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 [this message]
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=20240204174147.19c5a334@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=andy.shevchenko@gmail.com \
--cc=dlechner@baylibre.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox