public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.Li@nxp.com>
To: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>,
	 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, devicetree@vger.kernel.org,
	 linux-kernel@vger.kernel.org, Frank Li <Frank.Li@nxp.com>,
	 Han Xu <han.xu@nxp.com>
Subject: [PATCH 0/2] iio: gyro: Add support for iam20380 sensor
Date: Wed, 13 Nov 2024 11:05:55 -0500	[thread overview]
Message-ID: <20241113-iam20380-v1-0-cae690c4674d@nxp.com> (raw)

Add iam20380 sensor support.
- add binding doc
- Add support for the Invensense IAM20380 sensor to the MPU6050 driver. It is
  similar to the IAM20680. But IAM20380 only supports gyro and WHOAMI
  register data is difference

Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
Han Xu (2):
      dt-bindings: iio: imu: mpu6050: Add invensense,iam20380 compatible string
      iio: gyro: Add support for iam20380 sensor

 .../bindings/iio/imu/invensense,mpu6050.yaml       |  1 +
 drivers/iio/imu/inv_mpu6050/inv_mpu_core.c         | 25 ++++++++++++++++++++++
 drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c          |  6 ++++++
 drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h          |  2 ++
 4 files changed, 34 insertions(+)
---
base-commit: 28955f4fa2823e39f1ecfb3a37a364563527afbc
change-id: 20241112-iam20380-da900d806bf4

Best regards,
---
Frank Li <Frank.Li@nxp.com>


             reply	other threads:[~2024-11-13 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13 16:05 Frank Li [this message]
2024-11-13 16:05 ` [PATCH 1/2] dt-bindings: iio: imu: mpu6050: Add invensense,iam20380 compatible string Frank Li
2024-11-14 20:09   ` Conor Dooley
2024-11-13 16:05 ` [PATCH 2/2] iio: gyro: Add support for iam20380 sensor Frank Li
2024-11-13 19:28   ` Jean-Baptiste Maneyrol

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=20241113-iam20380-v1-0-cae690c4674d@nxp.com \
    --to=frank.li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=han.xu@nxp.com \
    --cc=jean-baptiste.maneyrol@tdk.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=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