From: Rob Herring <robh@kernel.org>
To: Adam Ford <aford173@gmail.com>
Cc: dri-devel@lists.freedesktop.org, linux-omap@vger.kernel.org,
adam.ford@logicpd.com, Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 2/3] dt-bindings: Add Logic PD Type 28 display panel
Date: Wed, 9 Oct 2019 18:31:30 -0500 [thread overview]
Message-ID: <20191009233130.GA1002@bogus> (raw)
In-Reply-To: <20191001233923.16514-5-aford173@gmail.com>
On Tue, Oct 01, 2019 at 06:39:22PM -0500, Adam Ford wrote:
> This patch adds documentation of device tree bindings for the WVGA panel
> Logic PD Type 28 display.
>
> Signed-off-by: Adam Ford <aford173@gmail.com>
> ---
> V4: Update per Rob H's suggestions and copy other panel yaml example from 5.4-rc1
> V3: Correct build errors from 'make dt_binding_check'
The example still fails to build here.
> V2: Use YAML instead of TXT for binding
>
> diff --git a/Documentation/devicetree/bindings/display/panel/logicpd,type28.yaml b/Documentation/devicetree/bindings/display/panel/logicpd,type28.yaml
> new file mode 100644
> index 000000000000..e2c62e8f1db4
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/panel/logicpd,type28.yaml
> @@ -0,0 +1,42 @@
> +# SPDX-License-Identifier: GPL-2.0
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/display/panel/logicpd,type28.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Logic PD Type 28 4.3" WQVGA TFT LCD panel
> +
> +maintainers:
> + - Adam Ford <aford173@gmail.com>
> +
> +allOf:
> + - $ref: panel-common.yaml#
> +
> +properties:
> + compatible:
> + const: logicpd,type28
> +
> + power-supply: true
> + enable-gpios: true
> + backlight: true
> + port: true
> +
> +required:
> + - compatible
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + lcd0: display {
> + compatible = "logicpd,type28";
> + enable-gpios = <&gpio5 27 GPIO_ACTIVE_HIGH>;
> + backlight = <&backlight>;
> + port {
> + lcd_in: endpoint {
> + remote-endpoint = <&dpi_out>;
> + };
> + };
> + };
> +
> +...
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-10-09 23:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 23:39 [PATCH V4 1/3] drm/panel: simple: Add Logic PD Type 28 display support Adam Ford
2019-10-01 23:39 ` [PATCH V4 2/3] dt-bindings: Add Logic PD Type 28 display panel Adam Ford
2019-10-01 23:39 ` [PATCH V4 3/3] ARM: logicpd-torpedo-37xx-devkit-28: Reference new DRM panel Adam Ford
2019-10-01 23:39 ` Adam Ford
2019-10-01 23:39 ` [PATCH V4 1/3] drm/panel: simple: Add Logic PD Type 28 display support Adam Ford
2019-10-01 23:39 ` Adam Ford
2019-10-01 23:39 ` [PATCH V4 2/3] dt-bindings: Add Logic PD Type 28 display panel Adam Ford
2019-10-09 23:31 ` Rob Herring [this message]
2019-10-15 23:04 ` Adam Ford
2019-10-16 13:15 ` Rob Herring
2019-10-16 13:55 ` Adam Ford
2019-10-01 23:39 ` [PATCH V4 3/3] ARM: logicpd-torpedo-37xx-devkit-28: Reference new DRM panel Adam Ford
2019-10-01 23:39 ` Adam Ford
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=20191009233130.GA1002@bogus \
--to=robh@kernel.org \
--cc=adam.ford@logicpd.com \
--cc=aford173@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.