From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: linux-iio@vger.kernel.org, drivers@analog.com,
Lars-Peter Clausen <lars@metafoo.de>
Subject: [PATCH 4/4] staging:iio:adis16400: Set the PROD_ID flag for the adis16334
Date: Tue, 30 Oct 2012 11:26:27 +0100 [thread overview]
Message-ID: <1351592787-2934-4-git-send-email-lars@metafoo.de> (raw)
In-Reply-To: <1351592787-2934-1-git-send-email-lars@metafoo.de>
The adis16334 has the PROD_ID register so set the PROD_ID flag in its chip info.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
---
drivers/staging/iio/imu/adis16400_core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/iio/imu/adis16400_core.c b/drivers/staging/iio/imu/adis16400_core.c
index b49858e..abcdc61 100644
--- a/drivers/staging/iio/imu/adis16400_core.c
+++ b/drivers/staging/iio/imu/adis16400_core.c
@@ -1125,6 +1125,7 @@ static struct adis16400_chip_info adis16400_chips[] = {
[ADIS16334] = {
.channels = adis16334_channels,
.num_channels = ARRAY_SIZE(adis16334_channels),
+ .flags = ADIS16400_HAS_PROD_ID,
.gyro_scale_micro = IIO_DEGREE_TO_RAD(50000), /* 0.05 deg/s */
.accel_scale_micro = IIO_G_TO_M_S_2(1000), /* 1 mg */
.temp_scale_nano = 67850000, /* 0.06785 C */
--
1.8.0
next prev parent reply other threads:[~2012-10-30 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 10:26 [PATCH 1/4] staging:iio:adis16400: Fix adis16334 sampling frequency control Lars-Peter Clausen
2012-10-30 10:26 ` [PATCH 2/4] staging:iio:adis16400: Fix product id check Lars-Peter Clausen
2012-10-30 10:26 ` [PATCH 3/4] staging:iio:adis16400: Remove now duplicated chip_table entry Lars-Peter Clausen
2012-10-30 10:26 ` Lars-Peter Clausen [this message]
2012-10-31 11:06 ` [PATCH 1/4] staging:iio:adis16400: Fix adis16334 sampling frequency control 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=1351592787-2934-4-git-send-email-lars@metafoo.de \
--to=lars@metafoo.de \
--cc=drivers@analog.com \
--cc=jic23@cam.ac.uk \
--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).