From: Dumitru Ceclan via B4 Relay <devnull+dumitru.ceclan.analog.com@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: mitrutzceclan@gmail.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Dumitru Ceclan <dumitru.ceclan@analog.com>
Subject: [PATCH v3 2/3] iio: adc: ad7173: order chipID by value
Date: Mon, 12 Aug 2024 11:13:15 +0300 [thread overview]
Message-ID: <20240812-ad4113-v3-2-046e785dd253@analog.com> (raw)
In-Reply-To: <20240812-ad4113-v3-0-046e785dd253@analog.com>
From: Dumitru Ceclan <dumitru.ceclan@analog.com>
The chipIDs defines were supposed to be ordered by value, one was out of
order. Fix the order.
Signed-off-by: Dumitru Ceclan <dumitru.ceclan@analog.com>
---
drivers/iio/adc/ad7173.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/adc/ad7173.c b/drivers/iio/adc/ad7173.c
index a854f2d30174..a2bfc28932a5 100644
--- a/drivers/iio/adc/ad7173.c
+++ b/drivers/iio/adc/ad7173.c
@@ -76,8 +76,8 @@
(x) == AD7173_AIN_REF_NEG)
#define AD7172_2_ID 0x00d0
-#define AD7175_ID 0x0cd0
#define AD7176_ID 0x0c90
+#define AD7175_ID 0x0cd0
#define AD7175_2_ID 0x0cd0
#define AD7172_4_ID 0x2050
#define AD7173_ID 0x30d0
--
2.43.0
next prev parent reply other threads:[~2024-08-12 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 8:13 [PATCH v3 0/3] Add support for AD4113 Dumitru Ceclan via B4 Relay
2024-08-12 8:13 ` [PATCH v3 1/3] dt-bindings: adc: ad7173: add support for ad4113 Dumitru Ceclan via B4 Relay
2024-08-12 8:13 ` Dumitru Ceclan via B4 Relay [this message]
2024-08-12 8:13 ` [PATCH v3 3/3] iio: " Dumitru Ceclan via B4 Relay
2024-08-17 10:19 ` [PATCH v3 0/3] Add support for AD4113 Jonathan Cameron
2024-09-08 10:41 ` Jonathan Cameron
2024-09-09 7:44 ` 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=20240812-ad4113-v3-2-046e785dd253@analog.com \
--to=devnull+dumitru.ceclan.analog.com@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dumitru.ceclan@analog.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=mitrutzceclan@gmail.com \
--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