From: Jonathan Cameron <jic23@kernel.org>
To: Yusuf Alper Bilgin <y.alperbilgin@gmail.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Liam Beguin" <liambeguin@gmail.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: iio: adc: ltc2497: add lltc,ltc2495 bindings
Date: Sat, 16 Aug 2025 11:24:54 +0100 [thread overview]
Message-ID: <20250816112454.37376453@jic23-huawei> (raw)
In-Reply-To: <20250815-ltc2495-v4-1-2d04e6005468@gmail.com>
On Fri, 15 Aug 2025 12:02:02 +0200
Yusuf Alper Bilgin <y.alperbilgin@gmail.com> wrote:
> Update the binding documentation for LTC2497 to include LTC2495 to
> enable support for its internal temperature sensor, which requires a
> different I2C command format and a new IIO channel.
>
> Signed-off-by: Yusuf Alper Bilgin <y.alperbilgin@gmail.com>
See reply to v1.
At least at first look it appears this should have a fallback compatible
as Krzysztof called out.
> ---
> Documentation/devicetree/bindings/iio/adc/lltc,ltc2497.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/adc/lltc,ltc2497.yaml b/Documentation/devicetree/bindings/iio/adc/lltc,ltc2497.yaml
> index 5cc6a96840778473895f436b7e2627d6240b254b..2a3e3dcc6ca7a48a0fccb88d8d42fee34efcff73 100644
> --- a/Documentation/devicetree/bindings/iio/adc/lltc,ltc2497.yaml
> +++ b/Documentation/devicetree/bindings/iio/adc/lltc,ltc2497.yaml
> @@ -17,11 +17,13 @@ description: |
>
> https://www.analog.com/media/en/technical-documentation/data-sheets/2309fd.pdf
>
> + LTC2495:
> LTC2497:
> LTC2499:
> 16bit ADC supporting up to 16 single ended or 8 differential inputs.
> I2C interface.
>
> + https://www.analog.com/media/en/technical-documentation/data-sheets/2495fe.pdf
> https://www.analog.com/media/en/technical-documentation/data-sheets/2497fb.pdf
> https://www.analog.com/media/en/technical-documentation/data-sheets/2499fe.pdf
>
> @@ -29,6 +31,7 @@ properties:
> compatible:
> enum:
> - lltc,ltc2309
> + - lltc,ltc2495
> - lltc,ltc2497
> - lltc,ltc2499
>
>
next prev parent reply other threads:[~2025-08-16 10:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 10:02 [PATCH v4 0/3] Add LTC2495 support Yusuf Alper Bilgin
2025-08-15 10:02 ` [PATCH v4 1/3] dt-bindings: iio: adc: ltc2497: add lltc,ltc2495 bindings Yusuf Alper Bilgin
2025-08-16 10:24 ` Jonathan Cameron [this message]
2025-08-15 10:02 ` [PATCH v4 2/3] iio: adc: ltc2497: add support for LTC2495 Yusuf Alper Bilgin
2025-08-16 10:49 ` Jonathan Cameron
2025-08-15 10:02 ` [PATCH v4 3/3] iio: adc: ltc2497: reorder struct members to fix memory holes Yusuf Alper Bilgin
2025-08-16 10:53 ` Jonathan Cameron
2025-08-16 10:18 ` [PATCH v4 0/3] Add LTC2495 support Jonathan Cameron
2025-08-18 16:11 ` Alper Bilgin
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=20250816112454.37376453@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=liambeguin@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=y.alperbilgin@gmail.com \
/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