Linux-IIO Archive mirror
 help / color / mirror / Atom feed
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 v3 0/6] iio: accel: adxl345: Add spi-3wire feature
Date: Sat, 23 Mar 2024 12:20:24 +0000	[thread overview]
Message-ID: <20240323122030.21800-1-l.rubusch@gmail.com> (raw)

Pass a function setup() as pointer from SPI/I2C specific modules
to the core module. Implement setup() to pass the spi-3wire bus
option, if declared in the device-tree.

In the core module, then update data_format register
configuration bits instead of overwriting it. The changes allow
to remove a data_range field, remove I2C and SPI redundant info
instances and replace them by a common info array instance.

Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
---
V1 -> V2: split into spi-3wire and refactoring
V2 -> V3: split further, focus on needed changesets

Lothar Rubusch (6):
  iio: accel: adxl345: Pass function pointer to core
  iio: accel: adxl345: Make data_format obsolete
  iio: accel: adxl345: Add the spi-3wire
  iio: accel: adxl345: Remove single info instances
  iio: accel: adxl345: Group bus configuration
  dt-bindings: iio: accel: adxl345: Add spi-3wire

 .../bindings/iio/accel/adi,adxl345.yaml       |  2 +
 drivers/iio/accel/adxl345.h                   | 13 ++++-
 drivers/iio/accel/adxl345_core.c              | 48 +++++++++++++++----
 drivers/iio/accel/adxl345_i2c.c               | 22 +++------
 drivers/iio/accel/adxl345_spi.c               | 32 ++++++-------
 5 files changed, 75 insertions(+), 42 deletions(-)

-- 
2.25.1


             reply	other threads:[~2024-03-23 12:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-23 12:20 Lothar Rubusch [this message]
2024-03-23 12:20 ` [PATCH v3 1/6] iio: accel: adxl345: Pass function pointer to core Lothar Rubusch
2024-03-23 12:20 ` [PATCH v3 2/6] iio: accel: adxl345: Make data_range obsolete Lothar Rubusch
2024-03-23 12:20 ` [PATCH v3 3/6] iio: accel: adxl345: Add spi-3wire option Lothar Rubusch
2024-03-24 13:32   ` Jonathan Cameron
2024-03-24 18:59     ` Lothar Rubusch
2024-03-25 14:46       ` Jonathan Cameron
2024-03-23 12:20 ` [PATCH v3 4/6] iio: accel: adxl345: Remove single info instances Lothar Rubusch
2024-03-24 13:35   ` Jonathan Cameron
2024-03-24 19:06     ` Lothar Rubusch
2024-03-25 14:48       ` Jonathan Cameron
2024-03-23 12:20 ` [PATCH v3 5/6] iio: accel: adxl345: Group bus configuration Lothar Rubusch
2024-03-24 13:37   ` Jonathan Cameron
2024-03-23 12:20 ` [PATCH v3 6/6] dt-bindings: iio: accel: adxl345: Add spi-3wire Lothar Rubusch
2024-03-23 14:28   ` Krzysztof Kozlowski
2024-03-24 13:39 ` [PATCH v3 0/6] iio: accel: adxl345: Add spi-3wire feature Jonathan Cameron
2024-03-24 19:20   ` Lothar Rubusch
2024-03-25 14:51     ` 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=20240323122030.21800-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).