From: "Ceclan, Dumitru" <mitrutzceclan@gmail.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
devnull+dumitru.ceclan.analog.com@kernel.org
Cc: Michael.Hennerich@analog.com, conor+dt@kernel.org,
devicetree@vger.kernel.org, dumitru.ceclan@analog.com,
jic23@kernel.org, krzk+dt@kernel.org, lars@metafoo.de,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
robh@kernel.org
Subject: Re: [PATCH v2 2/2] iio: adc: ad7173: add support for ad4113
Date: Fri, 9 Aug 2024 17:40:44 +0300 [thread overview]
Message-ID: <93d79fbd-8d1c-4a80-bf65-d4e597247573@gmail.com> (raw)
In-Reply-To: <37357b8a-1995-473d-a6fb-168fc38e0641@wanadoo.fr>
On 09/08/2024 17:30, Christophe JAILLET wrote:
> Le 09/08/2024 à 12:33, Dumitru Ceclan via B4 Relay a écrit :
>> From: Dumitru Ceclan <dumitru.ceclan-OyLXuOCK7orQT0dZR+AlfA@public.gmane.org>
>>
>> This commit adds support for the AD4113 ADC.
>> The AD4113 is a low power, low noise, 16-bit, Σ-Δ analog-to-digital
>> converter (ADC) that integrates an analog front end (AFE) for four
>> fully differential or eight single-ended inputs.
>>
>> Signed-off-by: Dumitru Ceclan <dumitru.ceclan-OyLXuOCK7orQT0dZR+AlfA@public.gmane.org>
>> ---
>> drivers/iio/adc/ad7173.c | 36 +++++++++++++++++++++++++++++++++++-
>> 1 file changed, 35 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/iio/adc/ad7173.c b/drivers/iio/adc/ad7173.c
>> index a854f2d30174..3ac09d326472 100644
>> --- a/drivers/iio/adc/ad7173.c
>> +++ b/drivers/iio/adc/ad7173.c
>> @@ -3,7 +3,7 @@
>> * AD717x and AD411x family SPI ADC driver
>> *
>> * Supported devices:
>> - * AD4111/AD4112/AD4114/AD4115/AD4116
>> + * AD4111/AD4112/AD4113/AD4114/AD4115/AD4116
>> * AD7172-2/AD7172-4/AD7173-8/AD7175-2
>> * AD7175-8/AD7176-2/AD7177-2
>> *
>> @@ -84,6 +84,7 @@
>> #define AD4111_ID AD7173_ID
>> #define AD4112_ID AD7173_ID
>> #define AD4114_ID AD7173_ID
>> +#define AD4113_ID 0x31D0
>
> Nitpick: others are in lowercase --> 0x31d0
>
>> #define AD4116_ID 0x34d0
>> #define AD4115_ID 0x38d0
>> #define AD7175_8_ID 0x3cd0
>
> Other than that, is there any reason to have this "random" order for these defines?
>
> CJ
>
It's not random, it was requested to order these defines by the ID value:
https://lore.kernel.org/all/CAHp75VcjcgnLkQWim1AVnyeRGFwwKpaWSCvrmqdv41Lx87hMKw@mail.gmail.com/
next prev parent reply other threads:[~2024-08-09 14:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 10:33 [PATCH v2 0/2] Add support for AD4113 Dumitru Ceclan
2024-08-09 10:33 ` Dumitru Ceclan via B4 Relay
2024-08-09 10:33 ` [PATCH v2 1/2] dt-bindings: adc: ad7173: add support for ad4113 Dumitru Ceclan
2024-08-09 10:33 ` Dumitru Ceclan via B4 Relay
2024-08-09 14:21 ` Conor Dooley
2024-08-09 14:32 ` Ceclan, Dumitru
2024-08-09 15:09 ` Conor Dooley
2024-08-17 10:12 ` Jonathan Cameron
2024-08-09 10:33 ` [PATCH v2 2/2] iio: " Dumitru Ceclan
2024-08-09 10:33 ` Dumitru Ceclan via B4 Relay
2024-08-09 12:26 ` Nuno Sá
2024-08-09 12:32 ` Ceclan, Dumitru
2024-08-09 14:12 ` Nuno Sá
2024-08-09 14:30 ` Christophe JAILLET
2024-08-09 14:40 ` Ceclan, Dumitru [this message]
2024-08-09 15:34 ` Christophe JAILLET
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=93d79fbd-8d1c-4a80-bf65-d4e597247573@gmail.com \
--to=mitrutzceclan@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+dumitru.ceclan.analog.com@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.