From: Marek Vasut <marek.vasut@mailbox.org>
To: Frank Li <Frank.li@nxp.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>
Cc: linux-input@vger.kernel.org, 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 1/2] dt-bindings: touchscreen: trivial-touch: Drop 'interrupts' requirement for old Ilitek
Date: Thu, 15 Jan 2026 03:09:11 +0100 [thread overview]
Message-ID: <68333066-2065-422d-9582-11a4bbb41e59@mailbox.org> (raw)
In-Reply-To: <aWZ0OQpQw814smri@lizhi-Precision-Tower-5810>
On 1/13/26 5:35 PM, Frank Li wrote:
Hello Frank,
>> +++ b/Documentation/devicetree/bindings/input/touchscreen/trivial-touch.yaml
>> @@ -57,13 +57,25 @@ properties:
>>
>> wakeup-source: true
>>
>> -allOf:
>> - - $ref: touchscreen.yaml
>> -
>> required:
>> - compatible
>> - reg
>> - - interrupts
>> +
>> +allOf:
>> + - $ref: touchscreen.yaml
>> + - if:
>> + not:
>> + properties:
>> + compatible:
>> + contains:
>> + enum:
>> + - ilitek,ili210x
>> + - ilitek,ili2117
>> + - ilitek,ili2120
>> + - ilitek,ili251x
>> + then:
>> + required:
>> + - interrupts
>
> Generally, if there are special requirements, move these to dedicated
> yaml file to avoid complex if-else in trivial-touch.yaml.
Done in V2, thanks.
prev parent reply other threads:[~2026-01-15 3:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 23:44 [PATCH 1/2] dt-bindings: touchscreen: trivial-touch: Drop 'interrupts' requirement for old Ilitek Marek Vasut
2026-01-12 23:44 ` [PATCH 2/2] Input: ili210x - add support for polling mode Marek Vasut
2026-01-13 16:41 ` Frank Li
2026-01-14 9:37 ` Geert Uytterhoeven
2026-01-14 15:12 ` Frank Li
2026-01-15 2:10 ` Marek Vasut
2026-01-13 16:35 ` [PATCH 1/2] dt-bindings: touchscreen: trivial-touch: Drop 'interrupts' requirement for old Ilitek Frank Li
2026-01-15 2:09 ` Marek Vasut [this message]
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=68333066-2065-422d-9582-11a4bbb41e59@mailbox.org \
--to=marek.vasut@mailbox.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+renesas@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