From: Jonathan Cameron <jic23@kernel.org>
To: Ludovic Desroches <ludovic.desroches@microchip.com>
Cc: Eugen Hristev <eugen.hristev@microchip.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-iio@vger.kernel.org>,
<nicolas.ferre@microchip.com>,
Maxime Ripard <maxime.ripard@bootlin.com>
Subject: Re: [PATCH v2 2/2] iio: adc: at91: fix wrong channel number in triggered buffer mode
Date: Sat, 29 Sep 2018 12:31:51 +0100 [thread overview]
Message-ID: <20180929123151.1fd0f9ec@archlinux> (raw)
In-Reply-To: <20180925131757.gjk2t277twhji5ns@M43218.corp.atmel.com>
On Tue, 25 Sep 2018 15:17:57 +0200
Ludovic Desroches <ludovic.desroches@microchip.com> wrote:
> On Mon, Sep 24, 2018 at 10:51:44AM +0300, Eugen Hristev wrote:
> > When channels are registered, the hardware channel number is not the
> > actual iio channel number.
> > This is because the driver is probed with a certain number of accessible
> > channels. Some pins are routed and some not, depending on the description of
> > the board in the DT.
> > Because of that, channels 0,1,2,3 can correspond to hardware channels
> > 2,3,4,5 for example.
> > In the buffered triggered case, we need to do the translation accordingly.
> > Fixed the channel number to stop reading the wrong channel.
> >
> > Fixes 0e589d5fb "ARM: AT91: IIO: Add AT91 ADC driver."
> > Cc: Maxime Ripard <maxime.ripard@bootlin.com>
> > Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
> Acked-by: Ludovic Desroches <ludovic.desroches@microchip.com>
Applied to the togreg branch of iio.git and pushed out as testing for the
autobuilders to play with it.
Thanks,
Jonathan
>
> > ---
> > Changes in v2:
> > - Added 'const' spec to the declaration to avoid build warning
> >
> > drivers/iio/adc/at91_adc.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/adc/at91_adc.c b/drivers/iio/adc/at91_adc.c
> > index e3be88e..75d2f73 100644
> > --- a/drivers/iio/adc/at91_adc.c
> > +++ b/drivers/iio/adc/at91_adc.c
> > @@ -248,12 +248,14 @@ static irqreturn_t at91_adc_trigger_handler(int irq, void *p)
> > struct iio_poll_func *pf = p;
> > struct iio_dev *idev = pf->indio_dev;
> > struct at91_adc_state *st = iio_priv(idev);
> > + struct iio_chan_spec const *chan;
> > int i, j = 0;
> >
> > for (i = 0; i < idev->masklength; i++) {
> > if (!test_bit(i, idev->active_scan_mask))
> > continue;
> > - st->buffer[j] = at91_adc_readl(st, AT91_ADC_CHAN(st, i));
> > + chan = idev->channels + i;
> > + st->buffer[j] = at91_adc_readl(st, AT91_ADC_CHAN(st, chan->channel));
> > j++;
> > }
> >
> > --
> > 2.7.4
> >
next prev parent reply other threads:[~2018-09-29 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 7:51 [PATCH v2 1/2] iio: adc: at91: fix acking DRDY irq on simple conversions Eugen Hristev
2018-09-24 7:51 ` [PATCH v2 2/2] iio: adc: at91: fix wrong channel number in triggered buffer mode Eugen Hristev
2018-09-24 20:25 ` Jonathan Cameron
2018-09-25 13:17 ` Ludovic Desroches
2018-09-29 11:31 ` Jonathan Cameron [this message]
2018-09-24 20:23 ` [PATCH v2 1/2] iio: adc: at91: fix acking DRDY irq on simple conversions Jonathan Cameron
2018-09-25 13:17 ` Ludovic Desroches
2018-09-29 11:31 ` 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=20180929123151.1fd0f9ec@archlinux \
--to=jic23@kernel.org \
--cc=eugen.hristev@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=maxime.ripard@bootlin.com \
--cc=nicolas.ferre@microchip.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).