From: Krzysztof Kozlowski <krzk@kernel.org>
To: David Lechner <dlechner@baylibre.com>,
Kurt Borja <kuurtb@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Tobias Sperling <tobias.sperling@softing.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH 1/2] dt-bindings: iio: adc: Add TI ADS1018/ADS1118
Date: Sat, 22 Nov 2025 17:14:25 +0100 [thread overview]
Message-ID: <046ece8f-4bcd-4f09-85c3-6bf5427d510c@kernel.org> (raw)
In-Reply-To: <a61ad3ae-b511-4af6-80a2-590fc05b1bfc@baylibre.com>
On 22/11/2025 16:09, David Lechner wrote:
>>> ...
>>>
>>>>>> + interrupts:
>>>>>> + description: DOUT/DRDY (Data Out/Data Ready) line.
>>>>>> + maxitems: 1
>>>>>> +
>>>>>> + drdy-gpios:
>>>>>> + description:
>>>>>> + Extra GPIO line connected to DOUT/DRDY (Data Out/Data Ready). This allows
>>>>>> + distinguishing between latched and real DRDY IRQs.
>>>>>
>>>>> I have feeling that you miss proper handling of IRQs (e.g. active level)
>>>>> on your board.
>>>>
>>>> Can you elaborate? Should I specify active level here?
>>>>
>>>>>
>>> The problem is not about the levels. It is rather that the behavior of the
>>> interrupt when disabled/masked is different on different interrupt controllers.
>>>
>>> On some controllers, if an event happens while disabled/masked, it "remembers"
>>> that and will trigger the interrupt as soon as it is enabled even if the
>>> condition doesn't exist anymore. Not a great hardware design IMHO, but there
>>> is real hardware that does this.
>>
>> Isn't it misconfiguration of trigger as I said before? It should be for
>> example edge, instead of level?
>>
>> Best regards,
>> Krzysztof
>
> No. It it still works like this for edge triggers.
OK, I still have doubts because it feels like we are adding workaround
for controller issues in device bindings. I don't recall how this was
solved (or if it was at all) in other cases, so fine for now for me.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-22 16:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 17:16 [PATCH 0/2] iio: Add support for TI ADS1X18 ADCs Kurt Borja
2025-11-21 17:16 ` [PATCH 1/2] dt-bindings: iio: adc: Add TI ADS1018/ADS1118 Kurt Borja
2025-11-21 18:30 ` Rob Herring (Arm)
2025-11-21 19:10 ` Krzysztof Kozlowski
2025-11-21 20:56 ` Kurt Borja
2025-11-21 22:40 ` David Lechner
2025-11-22 0:25 ` Kurt Borja
2025-11-22 9:34 ` Krzysztof Kozlowski
2025-11-22 15:09 ` David Lechner
2025-11-22 16:14 ` Krzysztof Kozlowski [this message]
2025-11-21 22:32 ` David Lechner
2025-11-22 0:26 ` Kurt Borja
2025-11-21 17:16 ` [PATCH 2/2] iio: adc: Add ti-ads1x18 driver Kurt Borja
2025-11-21 22:33 ` David Lechner
2025-11-22 0:24 ` Kurt Borja
2025-11-22 15:56 ` David Lechner
2025-11-26 20:41 ` Kurt Borja
2025-11-22 10:31 ` kernel test robot
2025-11-21 22:32 ` [PATCH 0/2] iio: Add support for TI ADS1X18 ADCs David Lechner
2025-11-21 23:28 ` Kurt Borja
2025-11-22 0:02 ` David Lechner
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=046ece8f-4bcd-4f09-85c3-6bf5427d510c@kernel.org \
--to=krzk@kernel.org \
--cc=Jonathan.Cameron@huawei.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=kuurtb@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=tobias.sperling@softing.com \
/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