public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Alexandru Ardelean <ardeleanalex@gmail.com>
Cc: Nuno Sa <nuno.sa@analog.com>,
	linux-iio <linux-iio@vger.kernel.org>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v2 7/9] iio: adis: add burst_max_speed_hz variable
Date: Sat, 24 Apr 2021 12:26:36 +0100	[thread overview]
Message-ID: <20210424122636.08b212ce@jic23-huawei> (raw)
In-Reply-To: <CA+U=DsqOFY1JbffqOjhcqFQzjeC3sEQc=gHF-AgZwuyfxsandA@mail.gmail.com>

On Fri, 23 Apr 2021 10:34:24 +0300
Alexandru Ardelean <ardeleanalex@gmail.com> wrote:

> On Thu, Apr 22, 2021 at 1:17 PM Nuno Sa <nuno.sa@analog.com> wrote:
> >
> > Typically, in burst mode, the device cannot operate at it's full spi
> > speed. Hence, the spi transfers for burst mode have to take this into
> > account. With this change we avoid a potential race with the spi core as
> > drivers were 'hacking' the device 'max_speed_hz' directly in the
> > trigger handler.
> >  
> 
> Reviewed-by: Alexandru Ardelean <ardeleanalex@gmail.com>

Rest of series looks good to me.  Nice cleanup / fixes ;)

I'll probably take this the slow way though rather than through fixes.
Race has been there a while after all with no reports so it can wait
a cycle.  I'll think about whether to mark them for stable when applying.
On this particular occasion we may want to do an explicit stable email
as the need to pick up the whole series (minus the first 2 I think)
even though some parts of it are not fixes as such but precursor rework.

Thanks,

Jonathan

> 
> 
> > Signed-off-by: Nuno Sa <nuno.sa@analog.com>
> > ---
> >  drivers/iio/imu/adis_buffer.c | 4 ++++
> >  include/linux/iio/imu/adis.h  | 2 ++
> >  2 files changed, 6 insertions(+)
> >
> > diff --git a/drivers/iio/imu/adis_buffer.c b/drivers/iio/imu/adis_buffer.c
> > index dda367071980..82239da2f441 100644
> > --- a/drivers/iio/imu/adis_buffer.c
> > +++ b/drivers/iio/imu/adis_buffer.c
> > @@ -51,9 +51,13 @@ static int adis_update_scan_mode_burst(struct iio_dev *indio_dev,
> >         adis->xfer[0].tx_buf = tx;
> >         adis->xfer[0].bits_per_word = 8;
> >         adis->xfer[0].len = 2;
> > +       if (adis->data->burst_max_speed_hz)
> > +               adis->xfer[0].speed_hz = adis->data->burst_max_speed_hz;
> >         adis->xfer[1].rx_buf = adis->buffer;
> >         adis->xfer[1].bits_per_word = 8;
> >         adis->xfer[1].len = burst_length;
> > +       if (adis->data->burst_max_speed_hz)
> > +               adis->xfer[1].speed_hz = adis->data->burst_max_speed_hz;
> >
> >         spi_message_init(&adis->msg);
> >         spi_message_add_tail(&adis->xfer[0], &adis->msg);
> > diff --git a/include/linux/iio/imu/adis.h b/include/linux/iio/imu/adis.h
> > index f9b728d490b1..cf49997d5903 100644
> > --- a/include/linux/iio/imu/adis.h
> > +++ b/include/linux/iio/imu/adis.h
> > @@ -55,6 +55,7 @@ struct adis_timeout {
> >   *                     this should be the minimum size supported by the device.
> >   * @burst_max_len:     Holds the maximum burst size when the device supports
> >   *                     more than one burst mode with different sizes
> > + * @burst_max_speed_hz:        Maximum spi speed that can be used in burst mode
> >   */
> >  struct adis_data {
> >         unsigned int read_delay;
> > @@ -83,6 +84,7 @@ struct adis_data {
> >         unsigned int burst_reg_cmd;
> >         unsigned int burst_len;
> >         unsigned int burst_max_len;
> > +       unsigned int burst_max_speed_hz;
> >  };
> >
> >  /**
> > --
> > 2.31.1
> >  


  reply	other threads:[~2021-04-24 11:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 10:19 [PATCH v2 0/9] Adis IRQ fixes and minor improvements Nuno Sa
2021-04-22 10:19 ` [PATCH v2 1/9] iio: adis_buffer: do not return ints in irq handlers Nuno Sa
2021-04-24 10:59   ` Jonathan Cameron
2021-04-22 10:19 ` [PATCH v2 2/9] iio: adis16400: " Nuno Sa
2021-04-24 11:00   ` Jonathan Cameron
2021-04-22 10:19 ` [PATCH v2 3/9] iio: adis16475: " Nuno Sa
2021-04-23  6:41   ` Alexandru Ardelean
2021-04-24 11:06     ` Jonathan Cameron
2021-04-26  9:45       ` Sa, Nuno
2021-04-22 10:19 ` [PATCH v2 4/9] iio: adis_buffer: check return value on page change Nuno Sa
2021-04-23  7:14   ` Alexandru Ardelean
2021-04-24 11:07     ` Jonathan Cameron
2021-04-22 10:19 ` [PATCH v2 5/9] iio: adis_buffer: don't push data to buffers on failure Nuno Sa
2021-04-23  7:28   ` Alexandru Ardelean
2021-04-24 11:13     ` Jonathan Cameron
2021-04-22 10:19 ` [PATCH v2 6/9] iio: adis_buffer: update device page after changing it Nuno Sa
2021-04-23  7:32   ` Alexandru Ardelean
2021-04-23 12:20     ` Sa, Nuno
2021-04-23 13:56       ` Alexandru Ardelean
2021-04-24 11:18         ` Jonathan Cameron
2021-04-24 11:19           ` Jonathan Cameron
2021-04-24 11:31             ` Jonathan Cameron
2021-04-26  9:54               ` Sa, Nuno
2021-04-26  9:46           ` Sa, Nuno
2021-04-22 10:19 ` [PATCH v2 7/9] iio: adis: add burst_max_speed_hz variable Nuno Sa
2021-04-23  7:34   ` Alexandru Ardelean
2021-04-24 11:26     ` Jonathan Cameron [this message]
2021-04-22 10:19 ` [PATCH v2 8/9] iio: adis16475: do not directly change spi 'max_speed_hz' Nuno Sa
2021-04-23  7:36   ` Alexandru Ardelean
2021-04-22 10:19 ` [PATCH v2 9/9] iio: adis16400: " Nuno Sa
2021-04-23  7:37   ` Alexandru Ardelean

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=20210424122636.08b212ce@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=ardeleanalex@gmail.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