From: Lothar Rubusch <l.rubusch@gmail.com>
To: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, eraretuya@gmail.com,
l.rubusch@gmail.com
Subject: [PATCH v2 0/3] iio: adxl345: add spi-3wire
Date: Fri, 22 Mar 2024 00:37:10 +0000 [thread overview]
Message-ID: <20240322003713.6918-1-l.rubusch@gmail.com> (raw)
Move driver wide constants and fields into the header. Reduce
redundant info struct definitions. Allow to pass a function
pointer from SPI/I2C specific probe, and smaller refactorings.
Apply regmap_update_bits() in the core file replaces the
regmap_write() to format_data.
Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
---
V1 -> V2: split into spi-3wire and refactoring
Lothar Rubusch (3):
iio: accel: adxl345: Update adxl345
iio: accel: adxl345: Add spi-3wire feature
dt-bindings: iio: accel: adxl345: Add spi-3wire
.../bindings/iio/accel/adi,adxl345.yaml | 2 +
drivers/iio/accel/adxl345.h | 44 ++++++-
drivers/iio/accel/adxl345_core.c | 117 ++++++++++--------
drivers/iio/accel/adxl345_i2c.c | 30 ++---
drivers/iio/accel/adxl345_spi.c | 38 +++---
5 files changed, 146 insertions(+), 85 deletions(-)
--
2.25.1
next reply other threads:[~2024-03-22 0:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 0:37 Lothar Rubusch [this message]
2024-03-22 0:37 ` [PATCH v2 1/3] iio: accel: adxl345: Update adxl345 Lothar Rubusch
2024-03-22 5:51 ` Krzysztof Kozlowski
2024-03-22 5:53 ` Krzysztof Kozlowski
2024-03-22 7:18 ` Nuno Sá
2024-03-23 12:16 ` Lothar Rubusch
2024-03-24 13:48 ` Jonathan Cameron
2024-03-22 7:16 ` Nuno Sá
2024-03-22 0:37 ` [PATCH v2 2/3] iio: accel: adxl345: Add spi-3wire feature Lothar Rubusch
2024-03-22 0:37 ` [PATCH v2 3/3] dt-bindings: iio: accel: adxl345: Add spi-3wire Lothar Rubusch
2024-03-22 2:17 ` Rob Herring
2024-03-23 12:04 ` Lothar Rubusch
2024-03-23 14:27 ` Krzysztof Kozlowski
2024-03-23 17:44 ` Lothar Rubusch
2024-03-25 7:47 ` Krzysztof Kozlowski
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=20240322003713.6918-1-l.rubusch@gmail.com \
--to=l.rubusch@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eraretuya@gmail.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).