public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Marek Vasut <marek.vasut@mailbox.org>
Cc: linux-input@vger.kernel.org, Frank Li <Frank.Li@nxp.com>,
	Conor Dooley <conor+dt@kernel.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Job Noorman <job@noorman.info>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: touchscreen: trivial-touch: Drop 'interrupts' requirement for old Ilitek
Date: Sat, 17 Jan 2026 19:34:02 +0100	[thread overview]
Message-ID: <578745f0-0865-4195-9237-6d41c7fd55f2@kernel.org> (raw)
In-Reply-To: <38a146cf-8eee-4fbb-8783-231108a01b54@mailbox.org>

On 17/01/2026 16:33, Marek Vasut wrote:
> On 1/17/26 12:22 PM, Krzysztof Kozlowski wrote:
>> On Sat, Jan 17, 2026 at 01:12:02AM +0100, Marek Vasut wrote:
>>> The old Ilitek touch controllers V3 and V6 can operate without
>>> interrupt line, in polling mode. Drop the 'interrupts' property
>>> requirement for those four controllers. To avoid overloading the
>>> trivial-touch, fork the old Ilitek V3/V6 touch controller binding
>>> into separate document.
>>
>> One if: block is fine, so IMO, this should stay in original binding
>> especially that more devices like some azoteq or semtech might have same
>> rule of not requiring interrupt line. Anyway, no big deal.
> I am not sure about the other non-ilitek devices, but the fruitboards do 
> use at least goodix and etm/edt touch controllers without interrupt line 
> too, those I have on my desk (those two have separate, more extensive, 
> binding document). I also suspect we will see more of those touch 
> controllers with optional interrupt line, so if we do, I think we can 
> re-combine the binding documents again ?

Yes.

Best regards,
Krzysztof

  reply	other threads:[~2026-01-17 18:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-17  0:12 [PATCH v4 1/3] dt-bindings: touchscreen: trivial-touch: Drop 'interrupts' requirement for old Ilitek Marek Vasut
2026-01-17  0:12 ` [PATCH v4 2/3] Input: ili210x - convert to dev_err_probe() Marek Vasut
2026-01-17 11:22   ` Krzysztof Kozlowski
2026-01-20 10:20   ` Geert Uytterhoeven
2026-01-20 18:25   ` Dmitry Torokhov
2026-01-17  0:12 ` [PATCH v4 3/3] Input: ili210x - add support for polling mode Marek Vasut
2026-01-18 17:19   ` Frank Li
2026-01-20 18:31   ` Dmitry Torokhov
2026-01-20 22:50     ` Marek Vasut
2026-01-21  5:23       ` Dmitry Torokhov
2026-01-21 22:42         ` Marek Vasut
2026-01-21 22:53           ` Dmitry Torokhov
2026-01-21 23:12             ` Marek Vasut
2026-01-17 11:22 ` [PATCH v4 1/3] dt-bindings: touchscreen: trivial-touch: Drop 'interrupts' requirement for old Ilitek Krzysztof Kozlowski
2026-01-17 15:33   ` Marek Vasut
2026-01-17 18:34     ` Krzysztof Kozlowski [this message]
2026-01-20 10:23       ` Geert Uytterhoeven

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=578745f0-0865-4195-9237-6d41c7fd55f2@kernel.org \
    --to=krzk@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=job@noorman.info \
    --cc=krzk+dt@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=marek.vasut@mailbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox