From: Jonathan Cameron <jic23@kernel.org>
To: inv.git-commit@tdk.com
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
lars@metafoo.de, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org,
Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
Subject: Re: [PATCH 1/2] dt-bindings: iio: imu: mpu6050: Add iam20680ht/hp bindings to mpu6050
Date: Sat, 28 Sep 2024 16:55:52 +0100 [thread overview]
Message-ID: <20240928165552.6d4c2f6a@jic23-huawei> (raw)
In-Reply-To: <20240920133615.167726-2-inv.git-commit@tdk.com>
On Fri, 20 Sep 2024 13:36:14 +0000
inv.git-commit@tdk.com wrote:
> From: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
>
> IAM-20680HT & HP are 2 variants of IAM-20680 fully compatible.
> They just have better specs, temperature range and a bigger FIFO.
Is that fifo size discoverable? If not then I'd describe
them as 'backwards compatible' but not 'fully' compatible.
So the binding is fine, as an aware driver would use the
more specific choice anyway and hence deal with that fifo
size change correctly. Someone who paid for this part
probably wants their bigger fifo.
Otherwise this looks fine to me as does the next patch.
Jonathan
>
> Signed-off-by: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
> ---
> .../devicetree/bindings/iio/imu/invensense,mpu6050.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml b/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml
> index 587ff2bced2d..a8d30ef015fa 100644
> --- a/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml
> +++ b/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml
> @@ -36,6 +36,11 @@ properties:
> - items:
> - const: invensense,icm20608d
> - const: invensense,icm20608
> + - items:
> + - enum:
> + - invensense,iam20680hp
> + - invensense,iam20680ht
> + - const: invensense,iam20680
>
> reg:
> maxItems: 1
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-09-28 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 13:36 [PATCH 0/2] Add support of IAM-20680 HP & HT inv.git-commit
2024-09-20 13:36 ` [PATCH 1/2] dt-bindings: iio: imu: mpu6050: Add iam20680ht/hp bindings to mpu6050 inv.git-commit
2024-09-20 13:39 ` Krzysztof Kozlowski
2024-09-20 14:39 ` Jean-Baptiste Maneyrol
2024-09-28 15:50 ` Jonathan Cameron
2024-09-28 15:55 ` Jonathan Cameron [this message]
2024-09-20 13:36 ` [PATCH 2/2] iio: imu: inv_mpu6050: add support for IAM-20680HT/HP inv.git-commit
-- strict thread matches above, loose matches on Subject: below --
2024-09-19 14:27 [PATCH 0/2] Add support of IAM-20680 HP & HT inv.git-commit
2024-09-19 14:27 ` [PATCH 1/2] dt-bindings: iio: imu: mpu6050: Add iam20680ht/hp bindings to mpu6050 inv.git-commit
2024-09-20 11:19 ` Krzysztof Kozlowski
2024-09-20 13:34 ` 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=20240928165552.6d4c2f6a@jic23-huawei \
--to=jic23@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inv.git-commit@tdk.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@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