From: amsfield22@gmail.com (Alison Schofield)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] iio: use regmap to retrieve struct device
Date: Sun, 10 Apr 2016 12:03:50 -0700 [thread overview]
Message-ID: <cover.1460314070.git.amsfield22@gmail.com> (raw)
In-Reply-To: <cover.1459918214.git.amsfield22@gmail.com>
These drivers include both struct regmap and struct device in their
global data. Remove the redundant copy by deleting struct device
from the drivers global data and using regmap API to retrieve when
needed.
This patchset removes all such redundancies in drivers/iio/.
Patches created using Coccinelle plus hand edits for whitespace.
Changes v1->v2:
This set is updated following reviews teaching me that not
all regmaps in global data will be of that device. Discards
and keepers are noted below. No actual code changes just a
remake of the patchset.
Jonathan - I saw you want to let it simmer, just want to
let it simmer cleaner ;)
accel: mma7455
Removing: Joachim ack'd, Jonathan took v1
adc: exynos_adc
Discard: regmap is of PMU parent
adc: qcom-spmi-iadc
adc: qcom-spmi-vadc
Discard: first line of _probe gets regmap from parent
accel: bmc150
gyro: bmg160
Keep: regmap passed into _probe from i2c,spi_probe where
it was initialized for this device
accel: mxc4005
health: afe4403
health: afe4404
Keep: regmap initialized in _probe for this device
Alison Schofield (5):
iio: accel: bmc150: use regmap to retrieve struct device
iio: accel: mxc4005: use regmap to retrieve struct device
iio: health: afe4403: use regmap to retrieve struct device
iio: health: afe4404: use regmap to retrieve struct device
iio: gyro: bmg160: use regmap to retrieve struct device
drivers/iio/accel/bmc150-accel-core.c | 99 +++++++++++++++++++----------------
drivers/iio/accel/mxc4005.c | 26 +++++----
drivers/iio/gyro/bmg160_core.c | 86 +++++++++++++++---------------
drivers/iio/health/afe4403.c | 36 ++++++-------
drivers/iio/health/afe4404.c | 38 +++++++-------
5 files changed, 149 insertions(+), 136 deletions(-)
--
2.1.4
next prev parent reply other threads:[~2016-04-10 19:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 5:15 [PATCH 0/9] iio: use regmap to retrieve struct device Alison Schofield
2016-04-06 5:15 ` [PATCH 1/9] iio: adc: exynos_adc: " Alison Schofield
2016-04-06 7:03 ` Marek Szyprowski
2016-04-06 20:33 ` Alison Schofield
2016-04-07 5:33 ` Marek Szyprowski
2016-04-10 13:45 ` Jonathan Cameron
2016-04-06 5:16 ` [PATCH 2/9] iio: adc: qcom-spmi-iadc: " Alison Schofield
2016-04-10 13:54 ` Jonathan Cameron
2016-04-06 5:17 ` [PATCH 3/9] iio: adc: qcom-spmi-vadc: " Alison Schofield
2016-04-10 13:55 ` Jonathan Cameron
2016-04-06 5:18 ` [PATCH 4/9] iio: accel: bmc150: " Alison Schofield
2016-04-06 5:18 ` [PATCH 5/9] iio: accel: mma7455: " Alison Schofield
2016-04-06 7:35 ` Joachim Eastwood
2016-04-10 13:51 ` Jonathan Cameron
2016-04-06 5:19 ` [PATCH 6/9] iio: accel: mxc4005: " Alison Schofield
2016-04-06 5:20 ` [PATCH 7/9] iio: health: afe4403: " Alison Schofield
2016-04-06 5:20 ` [PATCH 8/9] iio: health: afe4404: " Alison Schofield
2016-04-06 5:21 ` [PATCH 9/9] iio: gyro: bmg160_core: " Alison Schofield
2016-04-10 19:03 ` Alison Schofield [this message]
2016-04-10 19:05 ` [PATCH v2 1/5] iio: accel: bmc150: " Alison Schofield
2016-04-16 19:20 ` Jonathan Cameron
2016-04-18 12:18 ` Tirdea, Irina
2016-04-18 14:59 ` Srinivas Pandruvada
2016-04-18 19:16 ` Jonathan Cameron
2016-04-10 19:06 ` [PATCH v2 2/5] iio: accel: mxc4005: " Alison Schofield
2016-04-16 19:21 ` Jonathan Cameron
2016-04-10 19:07 ` [PATCH v2 3/5] iio: health: afe4403: " Alison Schofield
2016-04-16 19:22 ` Jonathan Cameron
2016-04-10 19:07 ` [PATCH v2 4/5] iio: health: afe4404: " Alison Schofield
2016-04-16 19:22 ` Jonathan Cameron
2016-04-17 18:07 ` Andrew F. Davis
2016-04-10 19:08 ` [PATCH v2 5/5] iio: gyro: bmg160: " Alison Schofield
2016-04-16 19:24 ` Jonathan Cameron
2016-04-18 15:03 ` Srinivas Pandruvada
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=cover.1460314070.git.amsfield22@gmail.com \
--to=amsfield22@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).