[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aLbwtONZDkC/01gY@JSANTO12-L01.ad.analog.com>
Date: Tue, 2 Sep 2025 10:27:16 -0300
From: Jonathan Santos <jonath4nns@...il.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: linux-kernel@...r.kernel.org,
Jonathan Santos <Jonathan.Santos@...log.com>,
linux-iio@...r.kernel.org, devicetree@...r.kernel.org,
Michael.Hennerich@...log.com, lars@...afoo.de, jic23@...nel.org,
dlechner@...libre.com, nuno.sa@...log.com, andy@...nel.org,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
marcelo.schmitt1@...il.com
Subject: Re: [PATCH v2 1/4] dt-bindings: iio: adc: ad7768-1: add new
supported parts
On 08/31, Krzysztof Kozlowski wrote:
> On 31/08/2025 05:43, Jonathan Santos wrote:
> >>> maxItems: 1
> >>> @@ -58,6 +66,18 @@ properties:
> >>> description:
> >>> ADC reference voltage supply
> >>>
> >>> + adi,gain-milli:
> >>> + description: |
> >>> + Specifies the gain applied by the Analog Anti-Aliasing Filter (AAF) to the
> >>> + ADC input (in milli units). The hardware gain is determined by which input
> >>
> >>
> >> I don't think there is no such thing as "milli units". milli is SI
> >> prefix, not unit. So "units" is the unit? Or how exactly?
> >>
> >> Basis points were before since 2022 so I don't get why these other
> >> bindings introduced in 2024 could not use it?
> >>
> >> Anyway, if you ever do not apply reviewers comment, then your commit msg
> >> should explain this. Otherwise you get the same discussion here.
> >>
> >
> > Yes, you are right. We shouldn't use milli as suffix. However, may I
> > suggest another option?
> >
> > I believe -permille is more appropriate because it represents a 1/1000
> > proportion, which gives the precision we need to cover all values.
> >
> > so it would be something like: adi,aaf-gain-permille
> >
> > Is that ok for you?
> >
> > Thanks for the feedback,
> > Jonathan S.
>
>
> What's wrong with existing unit I pointed out before?
>
Nothing wrong, just thought permille would be a clearer unit than basis
point for the user. But i can proceed with bp, no problem.
> BTW, any idea why your reply-to header is completely corrupted (copies
> in-reply-to...)?
>
Yes, i was including the in-reply- to, sorry about that.
>
> Best regards,
> Krzysztof
Powered by blists - more mailing lists