[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230227222309.GB1048218-robh@kernel.org>
Date: Mon, 27 Feb 2023 16:23:09 -0600
From: Rob Herring <robh@...nel.org>
To: Sasha Finkelstein <fnkl.kernel@...il.com>
Cc: Sven Peter <sven@...npeter.dev>, Hector Martin <marcan@...can.st>,
Alyssa Rosenzweig <alyssa@...enzweig.io>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
- <asahi@...ts.linux.dev>, Henrik Rydberg <rydberg@...math.org>,
linux-arm-kernel@...ts.infradead.org, linux-input@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC 1/4] dt-bindings: input: touchscreen: Add Z2
controller bindings.
On Fri, Feb 24, 2023 at 12:08:42PM +0100, Sasha Finkelstein wrote:
> On Fri, 24 Feb 2023 at 12:04, Sven Peter <sven@...npeter.dev> wrote:
> > Now that I thought about this again after the brief discussion we already had:
> > Do we even need to specify the device name? Is there any reason we can't just
> > always use something like "Apple Z2 TouchBar"?
> A similar protocol is used for primary touchscreen on idevices, which
Similar? So close, but somehow different.
> need different
> userspace handling. This is to make the driver potentially useful for
> people who run
> linux on checkra1n-able devices.
It is sounding to me like you need different compatibles. Don't try to
parameterize the differences with properties. Unless you can define all
the differences up front (hint: you can't).
Rob
Powered by blists - more mailing lists