From: Rob Herring <robh@kernel.org>
To: Yakir Yang <ykk@rock-chips.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH v2 5/6] dt-bindings: add Sharp LQ123P1JX31 panel binding
Date: Fri, 10 Jun 2016 08:42:17 -0500 [thread overview]
Message-ID: <20160610134217.GA25881@rob-hp-laptop> (raw)
In-Reply-To: <1465386765-27867-1-git-send-email-ykk@rock-chips.com>
On Wed, Jun 08, 2016 at 07:52:45PM +0800, Yakir Yang wrote:
> The Sharp LQ123P1JX31 is an 12.3" 2400x1600 TFT-LCD panel
> connected using eDP interfaces.
>
> Signed-off-by: Yakir Yang <ykk@rock-chips.com>
> ---
> Changes in v2:
> - Add dt-bindings of Sharp LQ123P1JX31 panel in v2
>
> .../devicetree/bindings/display/panel/sharp,lq123p1jx31.txt | 7 +++++++
> 1 file changed, 7 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/display/panel/sharp,lq123p1jx31.txt
>
> diff --git a/Documentation/devicetree/bindings/display/panel/sharp,lq123p1jx31.txt b/Documentation/devicetree/bindings/display/panel/sharp,lq123p1jx31.txt
> new file mode 100644
> index 0000000..81938c0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/panel/sharp,lq123p1jx31.txt
> @@ -0,0 +1,7 @@
> +Sharp 12.3" (2400x1600 pixels) TFT LCD panel
> +
> +Required properties:
> +- compatible: should be "sharp,lq123p1jx31,"
^
Need to drop the comma.
No regulators or resets or pwms?
Rob
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-06-10 13:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 11:52 [PATCH v2 1/6] dt-bindings: add LG LP097QX1-SPA1 panel binding Yakir Yang
2016-06-08 11:52 ` [PATCH v2 2/6] drm/panel: simple: Add support for LG LP097QX1-SPA1 2048x1536 panel Yakir Yang
[not found] ` <1465386753-27730-1-git-send-email-ykk-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-08 12:20 ` Emil Velikov
2016-06-10 13:26 ` Thierry Reding
2016-06-12 2:09 ` Yakir Yang
2016-06-08 11:52 ` [PATCH v2 3/6] dt-bindings: add Samsung LSN122DL01-C01 panel binding Yakir Yang
2016-06-08 11:52 ` [PATCH v2 4/6] drm/panel: simple: Add support for Samsung LSN122DL01-C01 2560x1600 panel Yakir Yang
[not found] ` <1465386762-27816-1-git-send-email-ykk-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-10 0:04 ` Stéphane Marchesin
2016-06-12 2:05 ` Yakir Yang
2016-06-08 11:52 ` [PATCH v2 5/6] dt-bindings: add Sharp LQ123P1JX31 panel binding Yakir Yang
2016-06-08 16:31 ` Doug Anderson
2016-06-10 13:42 ` Rob Herring [this message]
2016-06-10 16:40 ` Doug Anderson
2016-06-10 17:54 ` Rob Herring
2016-06-10 18:08 ` Doug Anderson
2016-06-12 2:14 ` Yakir Yang
2016-06-08 11:52 ` [PATCH v2 6/6] drm/panel: simple: Add support for Sharp LQ123P1JX31 2400x1600 panel Yakir Yang
2016-06-08 16:35 ` Doug Anderson
2016-06-10 16:11 ` Doug Anderson
2016-06-12 2:12 ` Yakir Yang
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=20160610134217.GA25881@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=ykk@rock-chips.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 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).