From: <Jianping.Shen@de.bosch.com>
To: <jic23@kernel.org>, <lars@metafoo.de>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<dima.fedrau@gmail.com>, <marcelo.schmitt1@gmail.com>,
<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <Jianping.Shen@de.bosch.com>,
<Christian.Lorenz3@de.bosch.com>,
<Ulrike.Frauendorf@de.bosch.com>, <Kai.Dolde@de.bosch.com>
Subject: [PATCH v4 0/2] iio: imu: smi330: add bosch smi330 driver
Date: Mon, 15 Sep 2025 18:09:32 +0200 [thread overview]
Message-ID: <20250915160934.89208-1-Jianping.Shen@de.bosch.com> (raw)
From: Jianping Shen <Jianping.Shen@de.bosch.com>
Add the iio driver for bosch imu smi330. The smi330 is a combined
three axis angular rate and three axis acceleration sensor module.
This driver provides raw data access for each axis through sysfs,
and tiggered buffer for continuous sampling.
dt-bindings:
v1 -> v2
- Add missing type to drive-open-drain
- Adapt description of drive-open-drain
v2 -> v3
- No Changes
v3 -> v4
- No Changes
imu driver:
v1 -> v2
- Strip back to a more minimal initial driver
v2 -> v3
- reorganize the driver as 1 core module, 1 I2C module, and 1 SPI module.
- remove build time INT pin choice
- change temperature channel definition
- improved reading data from sensor
- simplified timestamp acquisition
- some other minor finding fixes
v3 -> v4
- move #define from header to c file
- add sanity check to i2c message size
- use available_scan_masks to simplfy the copying data to buffer (dependent on [PATCH RFT] iio: Fix core buffer demux failure to account for unwanted channels at tail)
- allow setting output data rate for acc and gyro separately
- some other minor finding fixes
Jianping Shen (2):
dt-bindings: iio: imu: smi330: Add binding
iio: imu: smi330: Add driver
.../bindings/iio/imu/bosch,smi330.yaml | 90 ++
drivers/iio/imu/Kconfig | 1 +
drivers/iio/imu/Makefile | 1 +
drivers/iio/imu/smi330/Kconfig | 39 +
drivers/iio/imu/smi330/Makefile | 7 +
drivers/iio/imu/smi330/smi330.h | 25 +
drivers/iio/imu/smi330/smi330_core.c | 919 ++++++++++++++++++
drivers/iio/imu/smi330/smi330_i2c.c | 133 +++
drivers/iio/imu/smi330/smi330_spi.c | 85 ++
9 files changed, 1300 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/imu/bosch,smi330.yaml
create mode 100644 drivers/iio/imu/smi330/Kconfig
create mode 100644 drivers/iio/imu/smi330/Makefile
create mode 100644 drivers/iio/imu/smi330/smi330.h
create mode 100644 drivers/iio/imu/smi330/smi330_core.c
create mode 100644 drivers/iio/imu/smi330/smi330_i2c.c
create mode 100644 drivers/iio/imu/smi330/smi330_spi.c
--
2.34.1
next reply other threads:[~2025-09-15 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 16:09 Jianping.Shen [this message]
2025-09-15 16:09 ` [PATCH v4 1/2] dt-bindings: iio: imu: smi330: Add binding Jianping.Shen
2025-09-16 19:32 ` Conor Dooley
2025-09-15 16:09 ` [PATCH v4 2/2] iio: imu: smi330: Add driver Jianping.Shen
2025-09-27 14:44 ` 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=20250915160934.89208-1-Jianping.Shen@de.bosch.com \
--to=jianping.shen@de.bosch.com \
--cc=Christian.Lorenz3@de.bosch.com \
--cc=Kai.Dolde@de.bosch.com \
--cc=Ulrike.Frauendorf@de.bosch.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dima.fedrau@gmail.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=robh@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