public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: "Duje Mihanović" <duje@dujemihanovic.xyz>
To: Conor Dooley <conor@kernel.org>
Cc: Markuss Broks <markuss.broks@gmail.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Karel Balej <balejk@matfyz.cz>,
	David Wronek <david@mainlining.org>,
	phone-devel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	linux-input@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: input: touchscreen: imagis: add missing minItems
Date: Mon, 25 Aug 2025 20:57:57 +0200	[thread overview]
Message-ID: <5917367.DvuYhMxLoT@radijator> (raw)
In-Reply-To: <20250825-capillary-viral-b7448ca6a57e@spud>

On Monday, 25 August 2025 18:42:38 Central European Summer Time Conor Dooley wrote:
> On Sun, Aug 24, 2025 at 06:12:05PM +0200, Duje Mihanović wrote:
> > The binding currently expects exactly 5 keycodes, which matches the
> > chip's theoretical maximum but probably not the number of touch keys on
> > any phone using the IST3032C. Add a minItems value of 2 to prevent
> > dt-validate complaints.
> 
> Does this mean that there are devicetrees in the wild that use < 5
> keycodes?

Indeed.

> > 
> > +  - |
> > +    #include <dt-bindings/input/linux-event-codes.h>
> > +    #include <dt-bindings/interrupt-controller/irq.h>
> > +    i2c {
> > +      #address-cells = <1>;
> > +      #size-cells = <0>;
> > +      touchscreen@50 {
> > +        compatible = "imagis,ist3032c";
> > +        reg = <0x50>;
> > +        interrupt-parent = <&gpio>;
> > +        interrupts = <72 IRQ_TYPE_EDGE_FALLING>;
> > +        vdd-supply = <&ldo2>;
> > +        touchscreen-size-x = <480>;
> > +        touchscreen-size-y = <800>;
> > +        linux,keycodes = <KEY_APPSELECT>, <KEY_BACK>;
> 
> Does this really need a dedicated example? Why can't the property go
> into the existing one?

Only the IST3032C is currently known to support these keys and this is enforced
by the binding, so it wouldn't really make sense to add it to the 3038C
example.

Regards,
--
Duje




  reply	other threads:[~2025-08-25 18:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-24 16:12 [PATCH] dt-bindings: input: touchscreen: imagis: add missing minItems Duje Mihanović
2025-08-25 16:42 ` Conor Dooley
2025-08-25 18:57   ` Duje Mihanović [this message]
2025-08-26 17:38     ` Conor Dooley
2025-09-04 14:33       ` Dmitry Torokhov

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=5917367.DvuYhMxLoT@radijator \
    --to=duje@dujemihanovic.xyz \
    --cc=balejk@matfyz.cz \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=david@mainlining.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markuss.broks@gmail.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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