From: Marilene Andrade Garcia <marilene.agarcia@gmail.com>
To: Conor Dooley <conor@kernel.org>,
Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
"Kim Seer Paller" <kimseer.paller@analog.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"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>,
"Marcelo Schmitt" <Marcelo.Schmitt@analog.com>,
"Ceclan Dumitru" <dumitru.ceclan@analog.com>,
"Jonathan Santos" <Jonathan.Santos@analog.com>,
"Dragos Bogdan" <dragos.bogdan@analog.com>
Subject: Re: [PATCH v11 1/3] dt-bindings: iio: adc: add max14001
Date: Sun, 21 Sep 2025 18:49:46 -0300 [thread overview]
Message-ID: <18aec78d-7664-4555-a318-fe945dd84780@gmail.com> (raw)
In-Reply-To: <20250921-paralegal-styling-17b66d975dcf@spud>
On 21/09/2025 18:22, Conor Dooley wrote:
> On Sat, Sep 20, 2025 at 06:44:52PM -0300, Marcelo Schmitt wrote:
>> ...
>>>
>>>>> + interrupts:
>>>>> + minItems: 1
>>>>> + items:
>>>>> + - description: |
>>>>> + Asserts high when ADC readings exceed the upper threshold and low
>>>>> + when below the lower threshold. Must be connected to the COUT pin.
>>>>> + - description: |
>>>>> + Alert output that asserts low during a number of different error
>>>>> + conditions. The interrupt source must be attached to FAULT pin.
>>>
>>> These descriptions read wrong to me. They __are__ the COUT and FAULT
>>> pins, given what David responded to above, not something that can be
>>> connected to these pins (if they were, they would be represented as
>>> -gpios rather than interrupts most likely). Unless you mean that these
>>> pins can have some other use and are only available on the COUT/FAULT
>>> pins when some register value is set - but even in that case saying
>>> "must be" doesn't fit since the interrupt property could be used to
>>> configure the device accordingly.
>>
>> COUT and FAULT are just two pins on the ADC chip that can be used to generate
>> interrupts. Would a description like the one below sound better?
>>
>> interrupts:
>> minItems: 1
>> items:
>> - description: |
>> cout: Comparator output signal that asserts high when ADC readings
>> exceed the upper threshold and low when readings fall below the lower
>> threshold.
>
> I think you should mention the pin name here, like you did below.
> "asserts high on the COUT pin" or w/e.
>
>> - description: |
>> fault: When fault reporting is enabled, the FAULT pin is asserted low
>> whenever one of the monitored fault conditions occurs.
>>
>> Best regards,
>> Marcelo
Ok, I will change that for v12. Thanks.
Best Regards,
Marilene
next prev parent reply other threads:[~2025-09-21 21:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 22:14 [PATCH v11 0/3] Add MAX14001/MAX14002 support Marilene Andrade Garcia
2025-09-15 22:16 ` [PATCH v11 1/3] dt-bindings: iio: adc: add max14001 Marilene Andrade Garcia
2025-09-16 16:40 ` David Lechner
2025-09-16 19:20 ` Conor Dooley
2025-09-20 21:44 ` Marcelo Schmitt
2025-09-21 21:22 ` Conor Dooley
2025-09-21 21:49 ` Marilene Andrade Garcia [this message]
2025-09-15 22:16 ` [PATCH v11 2/3] iio: adc: max14001: New driver Marilene Andrade Garcia
2025-09-16 7:57 ` Andy Shevchenko
2025-09-16 18:04 ` David Lechner
2025-09-16 18:25 ` David Lechner
2025-09-17 8:10 ` Andy Shevchenko
2025-09-17 8:12 ` Andy Shevchenko
2025-09-17 13:21 ` David Lechner
2025-09-17 13:14 ` David Lechner
2025-09-23 0:56 ` Marilene Andrade Garcia
2025-09-23 14:27 ` David Lechner
2025-09-24 2:40 ` Marilene Andrade Garcia
2025-09-15 22:16 ` [PATCH v11 3/3] iio: ABI: Add voltage mean raw attribute Marilene Andrade Garcia
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=18aec78d-7664-4555-a318-fe945dd84780@gmail.com \
--to=marilene.agarcia@gmail.com \
--cc=Jonathan.Santos@analog.com \
--cc=Marcelo.Schmitt@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=dragos.bogdan@analog.com \
--cc=dumitru.ceclan@analog.com \
--cc=jic23@kernel.org \
--cc=kimseer.paller@analog.com \
--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