From: Dmitry Osipenko <digetx@gmail.com>
To: David Heidelberg <david@ixit.cz>,
Thierry Reding <thierry.reding@gmail.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: ~okias/devicetree@lists.sr.ht, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: display: bridge: document Toshiba TC358768 cells and panel node
Date: Wed, 15 Dec 2021 20:39:16 +0300 [thread overview]
Message-ID: <4fbabde7-e3f2-fe6a-db3b-182ddbbdf73e@gmail.com> (raw)
In-Reply-To: <20211215152712.72502-1-david@ixit.cz>
15.12.2021 18:27, David Heidelberg пишет:
> Properties #address-cells and #size-cells are valid.
> The bridge node can also contains panel node.
>
> Signed-off-by: David Heidelberg <david@ixit.cz>
> ---
> .../bindings/display/bridge/toshiba,tc358768.yaml | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/display/bridge/toshiba,tc358768.yaml b/Documentation/devicetree/bindings/display/bridge/toshiba,tc358768.yaml
> index eacfe7165083..3186d9dffd98 100644
> --- a/Documentation/devicetree/bindings/display/bridge/toshiba,tc358768.yaml
> +++ b/Documentation/devicetree/bindings/display/bridge/toshiba,tc358768.yaml
> @@ -69,6 +69,16 @@ properties:
> - port@0
> - port@1
>
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> +patternProperties:
> + "^panel@[0-3]$":
> + $ref: ../panel/panel-common.yaml
The panel is always fixed to port 1, isn't it? Shouldn't it be just
port@1 here?
next prev parent reply other threads:[~2021-12-15 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 15:27 [PATCH] dt-bindings: display: bridge: document Toshiba TC358768 cells and panel node David Heidelberg
2021-12-15 17:39 ` Dmitry Osipenko [this message]
2021-12-15 22:27 ` Rob Herring
2021-12-16 15:13 ` Rob Herring
2021-12-16 16:42 ` Dmitry Osipenko
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=4fbabde7-e3f2-fe6a-db3b-182ddbbdf73e@gmail.com \
--to=digetx@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=~okias/devicetree@lists.sr.ht \
/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).