From: "Sa, Nuno" <Nuno.Sa@analog.com>
To: Jonathan Cameron <jic23@kernel.org>
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, 4 May 2021 07:16:46 +0000 [thread overview]
Message-ID: <PH0PR03MB6366E7F728971DAF5B867898995A9@PH0PR03MB6366.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20210424123216.317e9b34@jic23-huawei>
> -----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 :) ...
- Nuno Sá
next prev parent reply other threads:[~2021-05-04 7:17 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 [this message]
2021-05-08 14:57 ` Jonathan Cameron
2021-05-18 14:21 ` Sa, Nuno
2021-05-18 17:35 ` 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=PH0PR03MB6366E7F728971DAF5B867898995A9@PH0PR03MB6366.namprd03.prod.outlook.com \
--to=nuno.sa@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=jic23@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).