linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Nuno Sa <nuno.sa@analog.com>
Cc: <linux-iio@vger.kernel.org>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v3 0/6] Adis IRQ fixes and minor improvements
Date: Tue, 27 Apr 2021 18:26:30 +0100	[thread overview]
Message-ID: <20210427182630.43d15ff0@jic23-huawei> (raw)
In-Reply-To: <20210427085454.30616-1-nuno.sa@analog.com>

On Tue, 27 Apr 2021 10:54:48 +0200
Nuno Sa <nuno.sa@analog.com> wrote:

> The primary goal of this series was to fix the return value on some
> trigger handlers as spotted in [1]. While doing it, I found some minor
> improvements that I think are simple enough to include in this series.
> 
> As for the first 2 patches, I opted to not do any functional change so
> I'm keeping the 'if (!adis->buffer)' check. However, 'adis-buffer' is
> allocated in 'update_scan_mode' hook which means we should be sure that
> the buffer is allocated and the check is really not needed. I did not
> went into the details but is there any way for the trigger handler to be
> called before the 'update_scan_mode' hook? If not, I'm happy in sending
> a v2 where we just remove the 'if'...
> 
> 
> Changes in v2:
>  * Remove the 'if' check for the allocated buffer;
>  * Make sure the adis 'state_lock' is unlocked on error paths;
>  * Fixed the commit message on the first 3 patches.
>  * Dropped ("iio: adis16475: re-set max spi transfer") and added 3 new
> patches (last 3 in the series ) to fix a potential race with the spi core
> as discussed in [2].
> 
> Changes in v3:
>  * Improved commit description on ("iio: adis16475: do not return ints in
> irq handlers");
>  * Reordered patch 2 and 3 so that patch 3 is easier to apply;
>  * Re-arranged the error handling on 'spi_sync()' error path.
> 
> [1]: https://marc.info/?l=linux-iio&m=161815197426882&w=2
> [2]: https://marc.info/?l=linux-iio&m=161884696722142&w=2

Not rushing these in as not comfortable with marking them for stable.
If we want to do a specific stable request at a later date that can
easily explain we need all of them.

Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to poke at them and see if they can find anything we
missed.

Thanks,

Jonathan

> 
> Nuno Sa (6):
>   iio: adis16475: do not return ints in irq handlers
>   iio: adis_buffer: update device page after changing it
>   iio: adis_buffer: don't push data to buffers on failure
>   iio: adis: add burst_max_speed_hz variable
>   iio: adis16475: do not directly change spi 'max_speed_hz'
>   iio: adis16400: do not directly change spi 'max_speed_hz'
> 
>  drivers/iio/imu/adis16400.c   | 15 ++-------------
>  drivers/iio/imu/adis16475.c   |  9 +++------
>  drivers/iio/imu/adis_buffer.c | 16 ++++++++++------
>  include/linux/iio/imu/adis.h  |  2 ++
>  4 files changed, 17 insertions(+), 25 deletions(-)
> 


      parent reply	other threads:[~2021-04-27 17:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27  8:54 [PATCH v3 0/6] Adis IRQ fixes and minor improvements Nuno Sa
2021-04-27  8:54 ` [PATCH v3 1/6] iio: adis16475: do not return ints in irq handlers Nuno Sa
2021-04-27  8:54 ` [PATCH v3 2/6] iio: adis_buffer: update device page after changing it Nuno Sa
2021-04-28  6:58   ` Alexandru Ardelean
2021-04-27  8:54 ` [PATCH v3 3/6] iio: adis_buffer: don't push data to buffers on failure Nuno Sa
2021-04-27  8:54 ` [PATCH v3 4/6] iio: adis: add burst_max_speed_hz variable Nuno Sa
2021-04-27  8:54 ` [PATCH v3 5/6] iio: adis16475: do not directly change spi 'max_speed_hz' Nuno Sa
2021-04-27  8:54 ` [PATCH v3 6/6] iio: adis16400: " Nuno Sa
2021-04-27 17:26 ` 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=20210427182630.43d15ff0@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=nuno.sa@analog.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;
as well as URLs for NNTP newsgroup(s).