From: Daniel Baluta <daniel.baluta@intel.com>
To: jic23@kernel.org, irina.tirdea@intel.com
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
daniel.baluta@intel.com, geert@linux-m68k.org,
vlad.dogaru@intel.com, octavian.purdila@intel.com,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: [PATCH 0/2] Introduce SPI support for BMC150 chip
Date: Fri, 15 Apr 2016 17:13:08 +0300 [thread overview]
Message-ID: <1460729590-18886-1-git-send-email-daniel.baluta@intel.com> (raw)
First patch splits the current architecture into a common part
and a bus specific part. Second patch adds SPI support.
We will have 3 modules:
* bmc150_magn.ko - exposes core functionality
* bmc150_magn_i2c.ko - instantiates I2C regmap and uses core
* bmc150_magn_spi.ko - instantiates SPI regmap and uses core
Daniel Baluta (2):
iio: magn: Split bmc150 driver in common/i2c parts
iio: magn: bmc150: Introduce SPI support
drivers/iio/magnetometer/Kconfig | 31 ++++--
drivers/iio/magnetometer/Makefile | 3 +
drivers/iio/magnetometer/bmc150_magn.c | 155 ++++++++++++-----------------
drivers/iio/magnetometer/bmc150_magn.h | 11 ++
drivers/iio/magnetometer/bmc150_magn_i2c.c | 77 ++++++++++++++
drivers/iio/magnetometer/bmc150_magn_spi.c | 68 +++++++++++++
6 files changed, 247 insertions(+), 98 deletions(-)
create mode 100644 drivers/iio/magnetometer/bmc150_magn.h
create mode 100644 drivers/iio/magnetometer/bmc150_magn_i2c.c
create mode 100644 drivers/iio/magnetometer/bmc150_magn_spi.c
--
2.5.0
next reply other threads:[~2016-04-15 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 14:13 Daniel Baluta [this message]
2016-04-15 14:13 ` [PATCH 1/2] iio: magn: Split bmc150 driver in common/i2c parts Daniel Baluta
2016-04-17 10:02 ` Jonathan Cameron
2016-04-18 11:24 ` Tirdea, Irina
2016-04-18 19:44 ` Jonathan Cameron
2016-04-15 14:13 ` [PATCH 2/2] iio: magn: bmc150: Introduce SPI support Daniel Baluta
2016-04-17 10:04 ` 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=1460729590-18886-1-git-send-email-daniel.baluta@intel.com \
--to=daniel.baluta@intel.com \
--cc=geert@linux-m68k.org \
--cc=irina.tirdea@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=octavian.purdila@intel.com \
--cc=pmeerw@pmeerw.net \
--cc=vlad.dogaru@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).