From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: fnkl.kernel@gmail.com
Cc: marcan@marcan.st, sven@svenpeter.dev, alyssa@rosenzweig.io,
dmitry.torokhov@gmail.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, asahi@lists.linux.dev,
rydberg@bitmath.org, linux-arm-kernel@lists.infradead.org,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, fnkl.kernel@gmail.com
Subject: Re: [PATCH RFC 1/4] dt-bindings: input: touchscreen: Add Z2 controller bindings.
Date: Fri, 24 Feb 2023 11:55:43 +0100 [thread overview]
Message-ID: <87r0ufs574.fsf@bloch.sibelius.xs4all.nl> (raw)
In-Reply-To: <20230223-z2-for-ml-v1-1-028f2b85dc15@gmail.com> (message from Sasha Finkelstein via B4 Relay on Fri, 24 Feb 2023 11:20:06 +0100)
> Date: Fri, 24 Feb 2023 11:20:06 +0100
> From: Sasha Finkelstein <fnkl.kernel@gmail.com>
Hi Sasha,
> Add bindings for touchscreen controllers attached using the Z2 protocol.
> Those are present in most Apple devices.
>
> Signed-off-by: Sasha Finkelstein <fnkl.kernel@gmail.com>
> ---
> .../input/touchscreen/apple,z2-touchscreen.yaml | 81 ++++++++++++++++++++++
> 1 file changed, 81 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/input/touchscreen/apple,z2-touchscreen.yaml b/Documentation/devicetree/bindings/input/touchscreen/apple,z2-touchscreen.yaml
> new file mode 100644
> index 000000000000..695594494b1e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/input/touchscreen/apple,z2-touchscreen.yaml
> @@ -0,0 +1,81 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/input/touchscreen/apple,z2-touchscreen.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Apple touchscreens attached using the Z2 protocol.
> +
> +maintainers:
> + - asahi@lists.linux.dev
> + - Sasha Finkelstein <fnkl.kernel@gmail.com>
> +
> +description: A series of touschscreen controllers used in Apple products.
> +
> +allOf:
> + - $ref: touchscreen.yaml#
> + - $ref: /schemas/spi/spi-peripheral-props.yaml#
> +
> +properties:
> + compatible:
> + const: apple,z2-touchscreen
> +
> + reg:
> + maxItems: 1
> +
> + interrupts-extended:
> + maxItems: 1
> +
> + reset-gpios:
> + maxItems: 1
> +
> + cs-gpios:
> + maxItems: 1
> +
> + firmware-name:
> + maxItems: 1
What is the motivation for including the firmware name in the device
tree rather than constructing it in the driver like what is done for
the broadcom wireless?
In your example the firmware name includes the directory name. I
think that is a bad idea since it makes assumptions about the
directory layout used for the firmware files on the OS level. And in
particular, forcing the firmware to be in a subdirectory named "apple"
would be awkward for the way we handle firmware in OpenBSD.
> +
> + apple,z2-device-name:
> + description: The name to be used for the input device
> + $ref: /schemas/types.yaml#/definitions/string
> +
> + touchscreen-size-x: true
> + touchscreen-size-y: true
> + spi-max-frequency: true
> +
> +required:
> + - compatible
> + - interrupts-extended
> + - reset-gpios
> + - cs-gpios
> + - firmware-name
> + - apple,z2-device-name
> + - touchscreen-size-x
> + - touchscreen-size-y
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + touchscreen@0 {
> + compatible = "apple,z2-touchscreen";
> + reg = <0>;
> + spi-max-frequency = <11500000>;
> + reset-gpios = <&pinctrl_ap 139 0>;
> + cs-gpios = <&pinctrl_ap 109 0>;
> + interrupts-extended = <&pinctrl_ap 194 IRQ_TYPE_EDGE_FALLING>;
> + firmware-name = "apple/dfrmtfw-j293.bin";
> + touchscreen-size-x = <23045>;
> + touchscreen-size-y = <640>;
> + apple,z2-device-name = "MacBookPro17,1 Touch Bar";
> + };
> + };
> +
> +...
>
> --
> Git-137.1)
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2023-02-24 10:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 10:20 [PATCH RFC 0/4] Driver for Apple Z2 touchscreens Sasha Finkelstein via B4 Relay
2023-02-24 10:20 ` [PATCH RFC 1/4] dt-bindings: input: touchscreen: Add Z2 controller bindings Sasha Finkelstein via B4 Relay
2023-02-24 10:55 ` Mark Kettenis [this message]
2023-02-24 11:04 ` Sasha Finkelstein
2023-02-24 11:08 ` Sven Peter
2023-02-28 2:58 ` Hector Martin
2023-02-28 20:53 ` Mark Kettenis
2023-03-01 3:13 ` Hector Martin
2023-02-24 11:03 ` Sven Peter
2023-02-24 11:08 ` Sasha Finkelstein
2023-02-27 22:23 ` Rob Herring
2023-02-27 19:51 ` Rob Herring
2023-02-27 20:06 ` Sasha Finkelstein
2023-02-27 22:14 ` Rob Herring
2023-02-27 22:25 ` Sasha Finkelstein
2023-02-28 3:05 ` Hector Martin
2023-02-24 10:20 ` [PATCH RFC 2/4] input: apple_z2: Add a driver for Apple Z2 touchscreens Sasha Finkelstein via B4 Relay
2023-03-09 3:04 ` Jeff LaBundy
2023-02-24 10:20 ` [PATCH RFC 3/4] arm64: dts: apple: t8103: Add touchbar bindings Sasha Finkelstein via B4 Relay
2023-02-24 10:20 ` [PATCH RFC 4/4] MAINTAINERS: Add entries for Apple Z2 touchscreen driver Sasha Finkelstein via B4 Relay
2023-02-28 2:43 ` [PATCH RFC 0/4] Driver for Apple Z2 touchscreens Hector Martin
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=87r0ufs574.fsf@bloch.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=fnkl.kernel@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=robh+dt@kernel.org \
--cc=rydberg@bitmath.org \
--cc=sven@svenpeter.dev \
/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
all inboxes | Powered by JetHome®