From: Violeta Menendez Gonzalez <violeta.menendez@codethink.co.uk>
To: linux-iio@vger.kernel.org, Peter Meerwald <pmeerw@pmeerw.net>,
Laurentiu Palcu <laurentiu.palcu@intel.com>,
Jonathan Cameron <jic23@kernel.org>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>,
linux-kernel@lists.codethink.co.uk
Subject: BMA250 support
Date: Thu, 10 Sep 2015 16:02:05 +0100 [thread overview]
Message-ID: <55F19B6D.7040205@codethink.co.uk> (raw)
Hi,
I've been taking a look at the accelerometer drivers meaning to add some
features for the chip BMA250.
I've seen that this chip is supported by the bma180 driver [1], and that
there's another driver for bmc150 [2] that supports BMA250E. Looking at
the datasheets [3][4][5] I can't really understand why it is that way,
as BMA250 and BMA250E register map looks exactly the same except for the
FIFO memory, and BMA250 doesn't look similar to BMA180 to me.
After some research on the internet and talking to Ben Dooks (who is
guiding me through this) we couldn't arrive to a conclusion as to why
this is this way. Could anyone clarify this a bit more? Could it make
sense to move support of BMA250 to bmc180 driver?
Thank you for your help
[1] drivers/iio/accel/bma180.c
[2] drivers/iio/accel/bmc150-accel.c
[3]
http://ae-bst.resource.bosch.com/media/products/dokumente/bma250/BST-BMA250-DS002-05.pdf
[4]
http://ae-bst.resource.bosch.com/media/products/dokumente/bma250e/BST-BMA250E-DS004-06.pdf
[5]
http://irtfweb.ifa.hawaii.edu/~tcs3/jumpman/jumppc/1107-BMA180/BMA180-DataSheet-v2.5.pdf
--
Violeta Menéndez González http://www.codethink.co.uk/
Software Engineer Codethink - Providing Genius
next reply other threads:[~2015-09-10 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 15:02 Violeta Menendez Gonzalez [this message]
2015-09-11 8:57 ` BMA250 support Laurentiu Palcu
2015-09-15 10:16 ` Violeta Menendez Gonzalez
2015-09-15 16:11 ` [Linux-kernel] " Ben Hutchings
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=55F19B6D.7040205@codethink.co.uk \
--to=violeta.menendez@codethink.co.uk \
--cc=ben.dooks@codethink.co.uk \
--cc=jic23@kernel.org \
--cc=laurentiu.palcu@intel.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@lists.codethink.co.uk \
--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).