From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: jic23@kernel.org, linux-iio@vger.kernel.org
Cc: srinivas.pandruvada@linux.intel.com, knaack.h@gmx.de,
lars@metafoo.de, pmeerw@pmeerw.net, laurentiu.palcu@intel.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] iio: accel: BMC150: fix scale value for 16G
Date: Thu, 28 Aug 2014 11:35:04 +0300 [thread overview]
Message-ID: <1409214906-27038-2-git-send-email-laurentiu.palcu@intel.com> (raw)
In-Reply-To: <1409214906-27038-1-git-send-email-laurentiu.palcu@intel.com>
According to documentation ([1] - page 27), the range for 16G is
7.81mg/LSB. Converted to SI, this is:
7.81 * 10^-3 * 9.80665 m/s^2 / LSB = 0.0765899365 m/s^2 / LSB
[1] http://ae-bst.resource.bosch.com/media/products/dokumente/bmc150/BST-BMC150-DS000-04.pdf
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
---
drivers/iio/accel/bmc150-accel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/accel/bmc150-accel.c b/drivers/iio/accel/bmc150-accel.c
index 23ae334..ccb6cf8 100644
--- a/drivers/iio/accel/bmc150-accel.c
+++ b/drivers/iio/accel/bmc150-accel.c
@@ -173,7 +173,7 @@ static const struct {
} bmc150_accel_scale_table[] = { {9610, BMC150_ACCEL_DEF_RANGE_2G},
{19122, BMC150_ACCEL_DEF_RANGE_4G},
{38344, BMC150_ACCEL_DEF_RANGE_8G},
- {77057, BMC150_ACCEL_DEF_RANGE_16G} };
+ {76590, BMC150_ACCEL_DEF_RANGE_16G} };
static const struct {
int sleep_dur;
--
1.9.1
next prev parent reply other threads:[~2014-08-28 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 8:35 [PATCH 0/3] iio: accel: BMC150: add support for more Bosch chips Laurentiu Palcu
2014-08-28 8:35 ` Laurentiu Palcu [this message]
2014-08-28 8:35 ` [PATCH 2/3] iio: accel: BMC150: fix issues when CONFIG_PM_RUNTIME is not set Laurentiu Palcu
2014-08-28 8:35 ` [PATCH 3/3] iio: accel: BMC150: add support for other Bosch chips Laurentiu Palcu
2014-08-28 9:21 ` Laurentiu Palcu
2014-08-28 9:26 ` Peter Meerwald
2014-08-28 10:46 ` Laurentiu Palcu
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=1409214906-27038-2-git-send-email-laurentiu.palcu@intel.com \
--to=laurentiu.palcu@intel.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=srinivas.pandruvada@linux.intel.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).