Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "Sa, Nuno" <Nuno.Sa@analog.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"Hennerich, Michael" <Michael.Hennerich@analog.com>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v4] iio: adis16480: support burst read function
Date: Tue, 18 May 2021 18:35:07 +0100	[thread overview]
Message-ID: <20210518183507.6d6a2e48@jic23-huawei> (raw)
In-Reply-To: <PH0PR03MB6366E94DF97823BE26BD0EBC992C9@PH0PR03MB6366.namprd03.prod.outlook.com>

On Tue, 18 May 2021 14:21:08 +0000
"Sa, Nuno" <Nuno.Sa@analog.com> wrote:

> Hi Jonathan,
> 
> > -----Original Message-----
> > From: Jonathan Cameron <jic23@kernel.org>
> > Sent: Saturday, May 8, 2021 4:57 PM
> > To: Sa, Nuno <Nuno.Sa@analog.com>
> > Cc: linux-iio@vger.kernel.org; Hennerich, Michael
> > <Michael.Hennerich@analog.com>; Lars-Peter Clausen
> > <lars@metafoo.de>
> > Subject: Re: [PATCH v4] iio: adis16480: support burst read function
> > 
> > [External]
> > 
> > On Tue, 4 May 2021 07:16:46 +0000
> > "Sa, Nuno" <Nuno.Sa@analog.com> wrote:
> >   
> > > > -----Original Message-----
> > > > From: Jonathan Cameron <jic23@kernel.org>
> > > > Sent: Saturday, April 24, 2021 1:32 PM
> > > > To: Sa, Nuno <Nuno.Sa@analog.com>
> > > > Cc: linux-iio@vger.kernel.org; Hennerich, Michael
> > > > <Michael.Hennerich@analog.com>; Lars-Peter Clausen
> > > > <lars@metafoo.de>
> > > > Subject: Re: [PATCH v4] iio: adis16480: support burst read function
> > > >
> > > > On Thu, 22 Apr 2021 12:37:35 +0200
> > > > Nuno Sa <nuno.sa@analog.com> wrote:
> > > >  
> > > > > Some supported devices support burst read function. This  
> > provides a  
> > > > method  
> > > > > for reading a batch of data (status, temperature, gyroscopes,
> > > > > accelerometers, time stamp/data counter, and CRC code), which  
> > > > does not  
> > > > > require a stall time between each 16-bit segment and only  
> > requires  
> > > > one  
> > > > > command on the DIN line to initiate. Devices supporting this  
> > mode  
> > > > > are:
> > > > >
> > > > >  * adis16495-1
> > > > >  * adis16495-2
> > > > >  * adis16495-3
> > > > >  * adis16497-1
> > > > >  * adis16497-2
> > > > >  * adis16497-3
> > > > >
> > > > > Reviewed-by: Lars-Peter Clausen <lars@metafoo.de>
> > > > > Signed-off-by: Nuno Sa <nuno.sa@analog.com>  
> > > >
> > > > Looks good to me.  Give me a poke if I seem to have lost it when
> > > > the dependency is in place.
> > > >  
> > >
> > > poking :) ...  
> > Thanks :)
> > Applied to the togreg branch of iio.git and pushed out as testing for
> > all the normal reasons.
> >   
> 
> Was this patch somehow lost? I was trying to sync up ADI internal tree and
> I cannot see this patch either in testing or togreg...
Odd.  Sorry about that. Now applied and pushed out as testing.

Jonathan

> 
> Thanks,
> - Nuno Sá


      reply	other threads:[~2021-05-18 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 10:37 [PATCH v4] iio: adis16480: support burst read function Nuno Sa
2021-04-24 11:32 ` Jonathan Cameron
2021-05-04  7:16   ` Sa, Nuno
2021-05-08 14:57     ` Jonathan Cameron
2021-05-18 14:21       ` Sa, Nuno
2021-05-18 17:35         ` 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=20210518183507.6d6a2e48@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=Nuno.Sa@analog.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.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