From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Cc: Alexandru Ardelean <ardeleanalex@gmail.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: [PATCH 0/9] iio: Move more things from iio_dev to iio_dev_opaque
Date: Mon, 26 Apr 2021 18:49:02 +0100 [thread overview]
Message-ID: <20210426174911.397061-1-jic23@kernel.org> (raw)
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Intent here is to clear out the low hanging fruit so we can focus on the
more interesting elements.
Hopefully this set are all uncontroversial. Lightly tested only but
all fairly mechanical so hopefully I didn't mess up.
As for the others my current thinking is as follows
mlock: Still some instances to clear out of this being used to protect things
it should not be used for. Long run we definitely want to move this one.
scan_timestamp: Can easily use a look up function in drivers that access this
directly, but that feels like an unwanted level of indirection in
iio_push_to_buffers_with_timestamp(). Perhaps worth doing anyway.
scan_bytes is also used in this function.
active_scan_mask and masklength: Both used in valid ways inside drivers.
Could be wrapped up in access functions, but it does seem a little
convoluted.
trig: This is used correctly in lots of drivers, so should stay in
struct iio_dev.
Jonathan Cameron (9):
iio: core: move @id from struct iio_dev to struct iio_dev_opaque
iio: avoid shadowing of variable name in to_iio_dev_opaque()
iio: core: move @driver_module from struct iio_dev to struct
iio_dev_opaque
iio: core: move @trig_readonly from struct iio_dev to struct
iio_dev_opaque
iio: core: move @scan_index_timestamp to struct iio_dev_opaque
iio: core: move @info_exist_lock to struct iio_dev_opaque
iio: core: move @chrdev from struct iio_dev to struct iio_dev_opaque
iio: core: move @flags from struct iio_dev to struct iio_dev_opaque
iio: core: move @clock_id from struct iio_dev to struct iio_dev_opaque
drivers/iio/accel/adxl372.c | 4 +-
drivers/iio/accel/bma180.c | 2 +-
drivers/iio/accel/bmc150-accel-core.c | 4 +-
drivers/iio/accel/kxcjk-1013.c | 4 +-
drivers/iio/accel/mma8452.c | 2 +-
drivers/iio/accel/mxc4005.c | 2 +-
drivers/iio/accel/stk8312.c | 2 +-
drivers/iio/accel/stk8ba50.c | 2 +-
drivers/iio/adc/ad7606.c | 3 +-
drivers/iio/adc/ad7766.c | 3 +-
drivers/iio/adc/ad7768-1.c | 3 +-
drivers/iio/adc/ad_sigma_delta.c | 2 +-
drivers/iio/adc/at91_adc.c | 4 +-
drivers/iio/adc/dln2-adc.c | 3 +-
drivers/iio/adc/ina2xx-adc.c | 3 +-
drivers/iio/adc/ti-ads131e08.c | 2 +-
drivers/iio/adc/xilinx-xadc-core.c | 2 +-
.../buffer/industrialio-triggered-buffer.c | 2 +-
drivers/iio/chemical/atlas-sensor.c | 2 +-
drivers/iio/chemical/ccs811.c | 2 +-
drivers/iio/chemical/scd30_core.c | 3 +-
.../common/hid-sensors/hid-sensor-trigger.c | 2 +-
drivers/iio/gyro/adxrs290.c | 2 +-
drivers/iio/gyro/bmg160_core.c | 4 +-
drivers/iio/gyro/fxas21002c_core.c | 2 +-
drivers/iio/gyro/itg3200_buffer.c | 2 +-
drivers/iio/gyro/mpu3050-core.c | 2 +-
drivers/iio/health/afe4403.c | 2 +-
drivers/iio/health/afe4404.c | 2 +-
drivers/iio/imu/adis_trigger.c | 3 +-
drivers/iio/imu/bmi160/bmi160_core.c | 3 +-
drivers/iio/imu/inv_mpu6050/inv_mpu_trigger.c | 2 +-
drivers/iio/imu/kmx61.c | 2 +-
drivers/iio/industrialio-buffer.c | 12 ++-
drivers/iio/industrialio-core.c | 76 +++++++++++++------
drivers/iio/industrialio-trigger.c | 19 +++--
drivers/iio/industrialio-triggered-event.c | 2 +-
drivers/iio/inkern.c | 46 ++++++-----
drivers/iio/light/acpi-als.c | 3 +-
drivers/iio/light/rpr0521.c | 2 +-
drivers/iio/light/si1145.c | 2 +-
drivers/iio/light/vcnl4000.c | 3 +-
drivers/iio/light/vcnl4035.c | 2 +-
drivers/iio/magnetometer/bmc150_magn.c | 2 +-
drivers/iio/magnetometer/rm3100-core.c | 2 +-
drivers/iio/potentiostat/lmp91000.c | 3 +-
drivers/iio/pressure/zpa2326.c | 3 +-
drivers/iio/proximity/as3935.c | 3 +-
drivers/iio/proximity/sx9310.c | 2 +-
drivers/iio/proximity/sx9500.c | 2 +-
include/linux/iio/iio-opaque.h | 22 +++++-
include/linux/iio/iio.h | 29 +------
52 files changed, 188 insertions(+), 131 deletions(-)
--
2.31.1
next reply other threads:[~2021-04-26 17:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 17:49 Jonathan Cameron [this message]
2021-04-26 17:49 ` [PATCH 1/9] iio: core: move @id from struct iio_dev to struct iio_dev_opaque Jonathan Cameron
2021-04-27 7:44 ` Alexandru Ardelean
2021-04-27 17:16 ` Jonathan Cameron
2021-05-03 11:42 ` Jonathan Cameron
2021-04-26 17:49 ` [PATCH 2/9] iio: avoid shadowing of variable name in to_iio_dev_opaque() Jonathan Cameron
2021-04-27 7:45 ` Alexandru Ardelean
2021-04-26 17:49 ` [PATCH 3/9] iio: core: move @driver_module from struct iio_dev to struct iio_dev_opaque Jonathan Cameron
2021-04-28 6:55 ` Alexandru Ardelean
2021-04-26 17:49 ` [PATCH 4/9] iio: core: move @trig_readonly " Jonathan Cameron
2021-04-27 8:03 ` Alexandru Ardelean
2021-04-26 17:49 ` [PATCH 5/9] iio: core: move @scan_index_timestamp " Jonathan Cameron
2021-04-27 8:03 ` Alexandru Ardelean
2021-04-26 17:49 ` [PATCH 6/9] iio: core: move @info_exist_lock " Jonathan Cameron
2021-04-27 8:04 ` Alexandru Ardelean
2021-04-26 17:49 ` [PATCH 7/9] iio: core: move @chrdev from struct iio_dev " Jonathan Cameron
2021-04-27 8:06 ` Alexandru Ardelean
2021-04-27 17:17 ` Jonathan Cameron
2021-04-26 17:49 ` [PATCH 8/9] iio: core: move @flags " Jonathan Cameron
2021-04-27 8:07 ` Alexandru Ardelean
2021-04-26 17:49 ` [PATCH 9/9] iio: core: move @clock_id " Jonathan Cameron
2021-04-27 8:02 ` Alexandru Ardelean
2021-04-27 17:19 ` Jonathan Cameron
2021-04-27 8:08 ` [PATCH 0/9] iio: Move more things from iio_dev to iio_dev_opaque Alexandru Ardelean
2021-04-27 17:12 ` Jonathan Cameron
2021-04-28 6:55 ` Alexandru Ardelean
2021-05-03 11:53 ` 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=20210426174911.397061-1-jic23@kernel.org \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=ardeleanalex@gmail.com \
--cc=linux-iio@vger.kernel.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