From: Puranjay Mohan <puranjay12@gmail.com>
To: Michael.Hennerich@analog.com, alexandru.ardelean@analog.com,
jic23@kernel.org, devicetree@vger.kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
lars@metafoo.de, Dragos.Bogdan@analog.com,
Darius.Berghe@analog.com
Cc: Puranjay Mohan <puranjay12@gmail.com>
Subject: [PATCH v1 0/2] iio: accel: add support for ADXL355
Date: Wed, 21 Jul 2021 15:22:33 +0530 [thread overview]
Message-ID: <20210721095235.218519-1-puranjay12@gmail.com> (raw)
Add the dt-bindings and the driver for ADXL355 3-axis MEMS Accelerometer.
Changes since v0:
1. Move adxl355_hpf_3db_table to adxl355_data structure. This is done to make
sure that each device gets its own table.
2. Make local regmap definitions private to adxl355_core.c.
3. Other minor coding style changes.
Puranjay Mohan (2):
dt-bindings: iio: accel: Add ADXL355 in trivial-devices
iio: accel: Add driver support for ADXL355
.../devicetree/bindings/trivial-devices.yaml | 2 +
MAINTAINERS | 7 +
drivers/iio/accel/Kconfig | 29 +
drivers/iio/accel/Makefile | 3 +
drivers/iio/accel/adxl355.h | 83 +++
drivers/iio/accel/adxl355_core.c | 541 ++++++++++++++++++
drivers/iio/accel/adxl355_i2c.c | 63 ++
drivers/iio/accel/adxl355_spi.c | 66 +++
8 files changed, 794 insertions(+)
create mode 100644 drivers/iio/accel/adxl355.h
create mode 100644 drivers/iio/accel/adxl355_core.c
create mode 100644 drivers/iio/accel/adxl355_i2c.c
create mode 100644 drivers/iio/accel/adxl355_spi.c
--
2.30.1
next reply other threads:[~2021-07-21 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 9:52 Puranjay Mohan [this message]
2021-07-21 9:52 ` [PATCH v1 1/2] dt-bindings: iio: accel: Add ADXL355 in trivial-devices Puranjay Mohan
2021-07-21 9:52 ` [PATCH v1 2/2] iio: accel: Add driver support for ADXL355 Puranjay Mohan
2021-07-21 10:46 ` Alexandru Ardelean
2021-07-21 11:40 ` Puranjay Mohan
2021-07-21 12:05 ` Alexandru Ardelean
2021-07-21 14:11 ` kernel test robot
2021-07-21 14:11 ` kernel test robot
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=20210721095235.218519-1-puranjay12@gmail.com \
--to=puranjay12@gmail.com \
--cc=Darius.Berghe@analog.com \
--cc=Dragos.Bogdan@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.ardelean@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.