From: "Barnabás Czémán" <trabarni@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
"Barnabás Czémán" <trabarni@gmail.com>,
"Danila Tikhonov" <danila@jiaxyga.com>
Subject: [PATCH v3 0/2] Add support for bosch bmi120
Date: Sun, 05 May 2024 07:36:53 +0200 [thread overview]
Message-ID: <20240505-bmi120-v3-0-15cee3d0b2ef@gmail.com> (raw)
Add support for bosch bmi120.
BMI120 is an energy-efficient version of BMI160. Despite having a different
CHIPID value, this variant seems to be fully compatible with BMI160.
It could be find in many phones like xiaomi-vince or xiaomi-tissot.
Signed-off-by: Barnabás Czémán <trabarni@gmail.com>
---
Changes in v3:
- Make chipids static.
- Link to v2: https://lore.kernel.org/r/20240504-bmi120-v2-0-3b3ce6e1c3c6@gmail.com
Changes in v2:
- Add bosch,bmi120 as a fallback compatible.
- Remove error path if chipid is not found.
- Link to v1: https://lore.kernel.org/r/20240504-bmi120-v1-0-478470a85058@gmail.com
---
Danila Tikhonov (2):
iio: imu: bmi160: add support for bmi120
dt-bindings: iio: imu: bmi160: add bmi120
.../devicetree/bindings/iio/imu/bosch,bmi160.yaml | 6 ++++-
drivers/iio/imu/bmi160/bmi160_core.c | 26 +++++++++++++++++-----
drivers/iio/imu/bmi160/bmi160_i2c.c | 3 +++
drivers/iio/imu/bmi160/bmi160_spi.c | 3 +++
4 files changed, 31 insertions(+), 7 deletions(-)
---
base-commit: 9221b2819b8a4196eecf5476d66201be60fbcf29
change-id: 20240504-bmi120-d3c88dcb3073
Best regards,
--
Barnabás Czémán <trabarni@gmail.com>
next reply other threads:[~2024-05-05 5:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 5:36 Barnabás Czémán [this message]
2024-05-05 5:36 ` [PATCH v3 1/2] iio: imu: bmi160: add support for bmi120 Barnabás Czémán
2024-05-05 5:36 ` [PATCH v3 2/2] dt-bindings: iio: imu: bmi160: add bmi120 Barnabás Czémán
2024-05-05 8:31 ` Krzysztof Kozlowski
2024-05-05 9:56 ` 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=20240505-bmi120-v3-0-15cee3d0b2ef@gmail.com \
--to=trabarni@gmail.com \
--cc=conor+dt@kernel.org \
--cc=danila@jiaxyga.com \
--cc=devicetree@vger.kernel.org \
--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=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).