mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Jonathan Santos <Jonathan.Santos@analog.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	Michael.Hennerich@analog.com, lars@metafoo.de, jic23@kernel.org,
	dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	marcelo.schmitt1@gmail.com
Subject: Re: [PATCH v2 1/4] dt-bindings: iio: adc: ad7768-1: add new supported parts
Date: Sun, 31 Aug 2025 15:12:29 +0200	[thread overview]
Message-ID: <e98ed14b-ed97-4e1c-a758-97b9bfc8ded4@kernel.org> (raw)
In-Reply-To: <aLPE3yiSTReS7B2J@JSANTO12-L01.ad.analog.com>

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?

BTW, any idea why your reply-to header is completely corrupted (copies
in-reply-to...)?


Best regards,
Krzysztof

  reply	other threads:[~2025-08-31 13:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-24  4:09 Jonathan Santos
2025-08-24 11:20 ` Krzysztof Kozlowski
2025-08-31  3:43   ` Jonathan Santos
2025-08-31 13:12     ` Krzysztof Kozlowski [this message]
2025-09-02 13:27       ` Jonathan Santos

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=e98ed14b-ed97-4e1c-a758-97b9bfc8ded4@kernel.org \
    --to=krzk@kernel.org \
    --cc=Jonathan.Santos@analog.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.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=marcelo.schmitt1@gmail.com \
    --cc=nuno.sa@analog.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

all inboxes | Powered by JetHome®