[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250925-swimming-overspend-ddf7ab4a252c@spud>
Date: Thu, 25 Sep 2025 20:46:38 +0100
From: Conor Dooley <conor@...nel.org>
To: Frank Li <Frank.li@....com>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
"open list:INPUT (KEYBOARD, MOUSE, JOYSTICK, TOUCHSCREEN)..." <linux-input@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" <devicetree@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>, imx@...ts.linux.dev
Subject: Re: [PATCH 1/1] dt-bindings: touchscreen: move ar1021.txt to
maxim,max11801.yaml
On Thu, Sep 25, 2025 at 03:28:56PM -0400, Frank Li wrote:
> On Thu, Sep 25, 2025 at 08:20:02PM +0100, Conor Dooley wrote:
> > On Thu, Sep 25, 2025 at 02:56:47PM -0400, Frank Li wrote:
> > > ar1021 have only reg and interrupts property beside touch common
> > > properties. So move context of ar1021.txt into maxim,max11801.yaml.
> >
> > Are these devices even remotely related, other than both being touch
> > devices?
>
> No, just properties is the same. There are many binding files, which bundle
> similar properties's yaml to one file.
>
> we may create trivial-touch.yaml, which similar with trivial-rtc.yaml.
I think putting trivial devices that are completely unrelated into one
file is confusing. It makes it seem like these devices are similar in
programming model etc.
Merging them into a explicitly designated trivial-touch binding would be
an improvement, if there are lots of very similar devices that could
also be merged in together.
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists