public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: cip-dev@lists.cip-project.org
Cc: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
	Chris Paterson <Chris.Paterson2@renesas.com>
Subject: Re: [cip-dev] [PATCH 1/2] dt-bindings: display: Add idk-1110wr binding
Date: Wed, 22 Apr 2020 08:51:20 +0200	[thread overview]
Message-ID: <20200422065120.GA12827@amd> (raw)
In-Reply-To: <OSBPR01MB359064AC4D27A061E7671640AAD50@OSBPR01MB3590.jpnprd01.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 1211 bytes --]

Hi!

> > > Add binding for the idk-1110wr LVDS panel from Advantech.
> > >
> > > Some panel-specific documentation can be found here:
> > > https://buy.advantech.eu/Displays/Embedded-LCD-Kits-LCD-Kit-Modules/model-IDK-1110WR-55WSA1E.htm
> > >
> > > This patch is based on commit d26087162857b12bd9d0424f2dea2cd9654e50a0
> > > upstream ("dt-bindings: display: Add idk-1110wr binding") which adds yaml
> > > bindings.
> > >
> > > Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> >
> > Okay. In future, I believe we can take yaml binding, even for kernel
> > where yaml support is not included. The markup is designed to be
> > human-readable anyway.
> >
> Thanks I shall do that in future. Just for reference in case a yaml binding has a reference to other yaml binding  so should there be a patch for converting to yaml format (for example panel.txt -> panel.yaml) ?
> 

Goal here is to save work, and this is just a documentation, so no, I
don't believe we need to do more conversions.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4594): https://lists.cip-project.org/g/cip-dev/message/4594
Mute This Topic: https://lists.cip-project.org/mt/73158052/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2020-04-22  7:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 19:50 [cip-dev] [PATCH 0/2] Add HiHope RZ/G2M board with idk-1110wr display Lad Prabhakar
2020-04-20 19:50 ` [cip-dev] [PATCH 1/2] dt-bindings: display: Add idk-1110wr binding Lad Prabhakar
2020-04-20 20:15   ` Pavel Machek
2020-04-21  8:19     ` Lad Prabhakar
2020-04-22  6:51       ` Pavel Machek [this message]
2020-04-20 19:50 ` [cip-dev] [PATCH 2/2] arm64: dts: renesas: Add HiHope RZ/G2M board with idk-1110wr display Lad Prabhakar
2020-04-20 20:24 ` [cip-dev] [PATCH 0/2] " Pavel Machek
2020-04-21  8:34   ` Lad Prabhakar
2020-04-22  6:51     ` Pavel Machek

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=20200422065120.GA12827@amd \
    --to=pavel@denx.de \
    --cc=Chris.Paterson2@renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    /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