From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Andreas Kemnade <andreas@kemnade.info>,
p.zabel@pengutronix.de, airlied@linux.ie, daniel@ffwll.ch,
robh+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, alistair@alistair23.me,
samuel@sholland.org, josua.mayer@jm0.eu,
letux-kernel@openphoenux.org
Subject: Re: [RFC PATCH 1/6] dt-bindings: display: imx: Add EPDC
Date: Thu, 17 Feb 2022 10:21:15 +0100 [thread overview]
Message-ID: <36445c86-036e-0942-a9a4-919595886c67@canonical.com> (raw)
In-Reply-To: <20220206080016.796556-2-andreas@kemnade.info>
On 06/02/2022 09:00, Andreas Kemnade wrote:
> Add a binding for the Electrophoretic Display Controller found at least
> in the i.MX6.
> The timing subnode is directly here to avoid having display parameters
> spread all over the plate.
>
> Supplies are organized the same way as in the fbdev driver in the
> NXP/Freescale kernel forks. The regulators used for that purpose,
> like the TPS65185, the SY7636A and MAX17135 have typically a single bit to
> start a bunch of regulators of higher or negative voltage with a
> well-defined timing. VCOM can be handled separately, but can also be
> incorporated into that single bit.
>
> Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> ---
> .../bindings/display/imx/fsl,mxc-epdc.yaml | 159 ++++++++++++++++++
> 1 file changed, 159 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/display/imx/fsl,mxc-epdc.yaml
>
> diff --git a/Documentation/devicetree/bindings/display/imx/fsl,mxc-epdc.yaml b/Documentation/devicetree/bindings/display/imx/fsl,mxc-epdc.yaml
> new file mode 100644
> index 000000000000..7e0795cc3f70
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/imx/fsl,mxc-epdc.yaml
> @@ -0,0 +1,159 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/display/imx/fsl,mxc-epdc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Freescale i.MX6 EPDC
> +
> +maintainers:
> + - Andreas Kemnade <andreas@kemnade.info>
> +
> +description: |
> + The EPDC is a controller for handling electronic paper displays found in
> + i.MX6 SoCs.
> +
> +properties:
> + compatible:
> + enum:
> + - fsl,imx6sl-epdc
> + - fsl,imx6sll-epdc
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: Bus clock
> + - description: Pixel clock
> +
> + clock-names:
> + items:
> + - const: axi
> + - const: pix
> +
> + interrupts:
> + maxItems: 1
> +
> + vscan-holdoff:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maxItems: 1
Except what Rob already said, all these are not arrays, so maxItems is
not appropriate. You can define minimum/maximum values instead.
> +
> + sdoed-width:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maxItems: 1
> +
> + sdoed-delay:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maxItems: 1
> +
> + sdoez-width:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maxItems: 1
> +
> + sdoez-delay:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maxItems: 1
> +
> + gdclk-hp-offs:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maxItems: 1
> +
> + gdsp-offs:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maxItems: 1
> +
> + gdoe-offs:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maxItems: 1
> +
> + gdclk-offs:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maxItems: 1
> +
> + num-ce:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maxItems: 1
> +
> + timing:
> + $ref: /display/panel/panel-timing.yaml#
> +
> + DISPLAY-supply:
> + description:
> + A couple of +/- voltages automatically powered on in a defintive order
Typo, definitive?
> +
> + VCOM-supply:
> + description: compensation voltage
> +
> + V3P3-supply:
All of supplies names - lowercase.
> + description: V3P3 supply
> +
> + epd-thermal-zone:
> + description:
> + Zone to get temperature of the EPD from, practically ambient temperature.
Is it a phandle?
> +
> +
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - clock-names
> + - interrupts
> + - vscan-holdoff
> + - sdoed-width
> + - sdoed-delay
> + - sdoez-width
> + - sdoez-delay
> + - gdclk-hp-offs
> + - gdsp-offs
> + - gdoe-offs
> + - gdclk-offs
> + - num-ce
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/imx6sl-clock.h>
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> + epdc: epdc@20f4000 {
Generic node name, e.g. display-controller
> + compatible = "fsl,imx6sl-epdc";
> + reg = <0x020f4000 0x4000>;
> + interrupts = <0 97 IRQ_TYPE_LEVEL_HIGH>;
s/0/GIC_SPI/
> + clocks = <&clks IMX6SL_CLK_EPDC_AXI>, <&clks IMX6SL_CLK_EPDC_PIX>;
> + clock-names = "axi", "pix";
> +
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-02-17 9:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 8:00 [RFC PATCH 0/6] drm: EPDC driver for i.MX6 Andreas Kemnade
2022-02-06 8:00 ` [RFC PATCH 1/6] dt-bindings: display: imx: Add EPDC Andreas Kemnade
2022-02-11 15:46 ` Rob Herring
2022-02-14 22:45 ` Andreas Kemnade
2022-02-16 23:52 ` Rob Herring
2022-02-17 9:21 ` Krzysztof Kozlowski [this message]
2022-02-17 11:31 ` Andreas Kemnade
2022-02-17 11:43 ` Krzysztof Kozlowski
2022-03-12 19:23 ` Jonathan Neuschäfer
2022-03-14 22:04 ` Andreas Kemnade
2022-02-06 8:00 ` [RFC PATCH 2/6] drm: Add skeleton for EPDC driver Andreas Kemnade
2022-03-12 19:41 ` Jonathan Neuschäfer
2022-02-06 8:00 ` [RFC PATCH 3/6] drm: mxc-epdc: Add display and waveform initialisation Andreas Kemnade
2022-03-12 20:12 ` Jonathan Neuschäfer
2022-02-06 8:00 ` [RFC PATCH 4/6] drm: mxc-epdc: Add update management Andreas Kemnade
2022-03-12 20:21 ` Jonathan Neuschäfer
2022-02-06 8:00 ` [RFC PATCH 5/6] ARM: dts: imx6sll: add EPDC Andreas Kemnade
2022-02-06 8:00 ` [RFC PATCH 6/6] arm: dts: imx6sl: Add EPDC Andreas Kemnade
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=36445c86-036e-0942-a9a4-919595886c67@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=airlied@linux.ie \
--cc=alistair@alistair23.me \
--cc=andreas@kemnade.info \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=josua.mayer@jm0.eu \
--cc=kernel@pengutronix.de \
--cc=letux-kernel@openphoenux.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=samuel@sholland.org \
--cc=shawnguo@kernel.org \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).