From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 9/9] iio: adis16136: Add ADIS16137 support
Date: Sat, 8 Aug 2015 15:10:31 +0100 [thread overview]
Message-ID: <55C60DD7.90006@kernel.org> (raw)
In-Reply-To: <1438781901-28000-10-git-send-email-lars@metafoo.de>
On 05/08/15 14:38, Lars-Peter Clausen wrote:
> The ADIS16137 is register map compatible to the ADIS16136, but has a
> different scale factor for the gyroscope output.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Applied - as usual initially pushed out as testing to let the autobuilder
do all the hardwork (remember when one locally built the patches for
a couple of architectures before pushing everything? - isn't it nice now
to do a cursory check and let the experts take over ;)
Thanks
Jonathan
> ---
> drivers/iio/gyro/adis16136.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/iio/gyro/adis16136.c b/drivers/iio/gyro/adis16136.c
> index 591bd55..26de876 100644
> --- a/drivers/iio/gyro/adis16136.c
> +++ b/drivers/iio/gyro/adis16136.c
> @@ -473,6 +473,7 @@ enum adis16136_id {
> ID_ADIS16133,
> ID_ADIS16135,
> ID_ADIS16136,
> + ID_ADIS16137,
> };
>
> static const struct adis16136_chip_info adis16136_chip_info[] = {
> @@ -488,6 +489,10 @@ static const struct adis16136_chip_info adis16136_chip_info[] = {
> .precision = IIO_DEGREE_TO_RAD(450),
> .fullscale = 24623,
> },
> + [ID_ADIS16137] = {
> + .precision = IIO_DEGREE_TO_RAD(1000),
> + .fullscale = 24609,
> + },
> };
>
> static int adis16136_probe(struct spi_device *spi)
> @@ -557,6 +562,7 @@ static const struct spi_device_id adis16136_ids[] = {
> { "adis16133", ID_ADIS16133 },
> { "adis16135", ID_ADIS16135 },
> { "adis16136", ID_ADIS16136 },
> + { "adis16137", ID_ADIS16137 },
> { }
> };
> MODULE_DEVICE_TABLE(spi, adis16136_ids);
>
prev parent reply other threads:[~2015-08-08 14:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 13:38 [PATCH 0/9] iio: adis updates Lars-Peter Clausen
2015-08-05 13:38 ` [PATCH 1/9] iio: adis16400: Fix adis16448 gyroscope scale Lars-Peter Clausen
2015-08-08 11:48 ` Jonathan Cameron
2015-08-05 13:38 ` [PATCH 2/9] iio: Add inverse unit conversion macros Lars-Peter Clausen
2015-08-08 11:51 ` Jonathan Cameron
2015-08-05 13:38 ` [PATCH 3/9] iio: adis16480: Fix scale factors Lars-Peter Clausen
2015-08-08 11:52 ` Jonathan Cameron
2015-08-05 13:38 ` [PATCH 4/9] iio: adis16400: adis16300 has product ID and serial number Lars-Peter Clausen
2015-08-08 11:54 ` Jonathan Cameron
2015-08-05 13:38 ` [PATCH 5/9] iio: adis16400: Add ADIS16305 support Lars-Peter Clausen
2015-08-08 11:54 ` Jonathan Cameron
2015-08-05 13:38 ` [PATCH 6/9] iio: adis16260: Add ADIS16266 support Lars-Peter Clausen
2015-08-08 11:58 ` Jonathan Cameron
2015-08-05 13:38 ` [PATCH 7/9] iio: adis16400: Add ADIS16367 support Lars-Peter Clausen
2015-08-08 14:08 ` Jonathan Cameron
2015-08-05 13:38 ` [PATCH 8/9] iio: adis16400: Add ADIS16445 support Lars-Peter Clausen
2015-08-08 14:09 ` Jonathan Cameron
2015-08-05 13:38 ` [PATCH 9/9] iio: adis16136: Add ADIS16137 support Lars-Peter Clausen
2015-08-08 14:10 ` 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=55C60DD7.90006@kernel.org \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).