From: Lucas Stach <l.stach@pengutronix.de>
To: Marek Vasut <marex@denx.de>, dri-devel@lists.freedesktop.org
Cc: devicetree@vger.kernel.org,
Neil Armstrong <narmstrong@baylibre.com>,
Jonas Karlman <jonas@kwiboo.se>, Rob Herring <robh+dt@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Sam Ravnborg <sam@ravnborg.org>,
Maxime Ripard <maxime@cerno.tech>
Subject: Re: [PATCH V3 01/12] dt-bindings: display: bridge: tc358867: Document DPI output support
Date: Mon, 28 Mar 2022 22:11:00 +0200 [thread overview]
Message-ID: <e99b7eed19ec396d3af8834830a33eab0abccccf.camel@pengutronix.de> (raw)
In-Reply-To: <20220224195817.68504-2-marex@denx.de>
Am Donnerstag, dem 24.02.2022 um 20:58 +0100 schrieb Marek Vasut:
> The TC358767/TC358867/TC9595 are all capable of operating in multiple
> modes, DPI-to-(e)DP, DSI-to-(e)DP, DSI-to-DPI. Document support for the
> DPI output port, which can now be connected both as input and output.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Jonas Karlman <jonas@kwiboo.se>
> Cc: Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
> Cc: Maxime Ripard <maxime@cerno.tech>
> Cc: Neil Armstrong <narmstrong@baylibre.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Cc: devicetree@vger.kernel.org
> To: dri-devel@lists.freedesktop.org
Reviewed-by: Lucas Stach <l.stach@pengutronix.de>
> ---
> V2: - Rebase on next-20220217
> V3: - No change
> ---
> .../devicetree/bindings/display/bridge/toshiba,tc358767.yaml | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/bridge/toshiba,tc358767.yaml b/Documentation/devicetree/bindings/display/bridge/toshiba,tc358767.yaml
> index f1541cc052977..5cfda6f2ba69c 100644
> --- a/Documentation/devicetree/bindings/display/bridge/toshiba,tc358767.yaml
> +++ b/Documentation/devicetree/bindings/display/bridge/toshiba,tc358767.yaml
> @@ -61,8 +61,8 @@ properties:
> port@1:
> $ref: /schemas/graph.yaml#/properties/port
> description: |
> - DPI input port. The remote endpoint phandle should be a
> - reference to a valid DPI output endpoint node
> + DPI input/output port. The remote endpoint phandle should be a
> + reference to a valid DPI output or input endpoint node.
>
> port@2:
> $ref: /schemas/graph.yaml#/properties/port
next prev parent reply other threads:[~2022-03-28 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220224195817.68504-1-marex@denx.de>
2022-02-24 19:58 ` [PATCH V3 01/12] dt-bindings: display: bridge: tc358867: Document DPI output support Marek Vasut
2022-02-24 22:42 ` Rob Herring
2022-03-28 20:11 ` Lucas Stach [this message]
2022-02-24 19:58 ` [PATCH V3 02/12] dt-bindings: display: bridge: tc358867: Document DSI data-lanes property Marek Vasut
2022-02-24 22:42 ` Rob Herring
2022-03-28 20:11 ` Lucas Stach
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=e99b7eed19ec396d3af8834830a33eab0abccccf.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonas@kwiboo.se \
--cc=marex@denx.de \
--cc=maxime@cerno.tech \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
/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).