From: Sam Ravnborg <sam@ravnborg.org>
To: Vinay Simha B N <simhavcs@gmail.com>
Cc: Neil Armstrong <narmstrong@baylibre.com>,
Ken-Sue.Tan@taec.toshiba.com, Chris.Cheng@taec.toshiba.com,
Bhushan.Patel@taec.toshiba.com,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, David Airlie <airlied@linux.ie>,
open list <linux-kernel@vger.kernel.org>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v5 1/2] dt-binding: Add DSI/LVDS TC358775 bridge bindings
Date: Wed, 1 Jul 2020 13:20:01 +0200 [thread overview]
Message-ID: <20200701112001.GA652928@ravnborg.org> (raw)
In-Reply-To: <CAGWqDJ51_QRHLP0mUyaCJCiKMJkGmbwuR9y2rZ=t=Mo7gCdb1w@mail.gmail.com>
Hi Vinay.
On Wed, Jul 01, 2020 at 03:14:09PM +0530, Vinay Simha B N wrote:
> sam,
>
> I rechecked, but did not find any indents are too spaced.
> This is taken from a working dts tree.
>
port@1 {
| reg = <1>;
| dsi0_out: endpoint {
| remote-endpoint = <&d2l_in_test>;
| data-lanes = <0 1 2 3>;
| };
};
};
};
See above, something is wrong with the indent in the examples.
> I had given two examples for a purpose. One for single lvds
> configuration single link mode,
> another is for dual lvds configurations dual-link mode and port mappings.
Please provide a proper description of the single link and dual link
modes in the descriptions of the bindings.
The examples shall support the bindings, they shall not include
information that is not covered in the bindings.
Sam
prev parent reply other threads:[~2020-07-01 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 7:03 [PATCH v5 1/2] dt-binding: Add DSI/LVDS TC358775 bridge bindings Vinay Simha BN
2020-07-01 9:19 ` Sam Ravnborg
2020-07-01 9:44 ` Vinay Simha B N
2020-07-01 11:20 ` Sam Ravnborg [this message]
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=20200701112001.GA652928@ravnborg.org \
--to=sam@ravnborg.org \
--cc=Bhushan.Patel@taec.toshiba.com \
--cc=Chris.Cheng@taec.toshiba.com \
--cc=Ken-Sue.Tan@taec.toshiba.com \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=simhavcs@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 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).