From: Markus Pargmann <mpa@pengutronix.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Irina Tirdea <irina.tirdea@intel.com>,
Vlad Dogaru <vlad.dogaru@intel.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de, Markus Pargmann <mpa@pengutronix.de>
Subject: [PATCH v4 0/2] iio: bmg160: Add SPI connection
Date: Wed, 19 Aug 2015 14:12:44 +0200 [thread overview]
Message-ID: <1439986366-25291-1-git-send-email-mpa@pengutronix.de> (raw)
Hi,
These are the remaining two patches for the bmg160 driver. These split core
driver from the I2C part and add the SPI regmap setup as separate driver.
Changes in v4:
- Fixed include of bmg160 header
- Changed Kconfig/Makefile setup to automatically select I2C and SPI drivers
dependending on the configurations state of the subsystems. The core driver
is compiled once and can be a module now.
Best regards,
Markus
Markus Pargmann (2):
iio: bmg160: Separate i2c and core driver
iio: bmg160: Add SPI driver
drivers/iio/gyro/Kconfig | 20 +++++--
drivers/iio/gyro/Makefile | 4 +-
drivers/iio/gyro/bmg160.h | 10 ++++
drivers/iio/gyro/{bmg160.c => bmg160_core.c} | 79 +++++-----------------------
drivers/iio/gyro/bmg160_i2c.c | 71 +++++++++++++++++++++++++
drivers/iio/gyro/bmg160_spi.c | 57 ++++++++++++++++++++
6 files changed, 170 insertions(+), 71 deletions(-)
create mode 100644 drivers/iio/gyro/bmg160.h
rename drivers/iio/gyro/{bmg160.c => bmg160_core.c} (94%)
create mode 100644 drivers/iio/gyro/bmg160_i2c.c
create mode 100644 drivers/iio/gyro/bmg160_spi.c
--
2.4.6
next reply other threads:[~2015-08-19 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 12:12 Markus Pargmann [this message]
2015-08-19 12:12 ` [PATCH v4 1/2] iio: bmg160: Separate i2c and core driver Markus Pargmann
2015-08-31 16:05 ` Jonathan Cameron
2015-09-14 14:26 ` Markus Pargmann
2015-08-19 12:12 ` [PATCH v4 2/2] iio: bmg160: Add SPI driver Markus Pargmann
2015-08-31 16:06 ` 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=1439986366-25291-1-git-send-email-mpa@pengutronix.de \
--to=mpa@pengutronix.de \
--cc=irina.tirdea@intel.com \
--cc=jic23@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--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).