From: Marek Vasut <marex@denx.de>
To: Rob Herring <robh@kernel.org>, Maxime Ripard <maxime@cerno.tech>
Cc: Neil Armstrong <narmstrong@baylibre.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Rob Herring <robh+dt@kernel.org>, David Airlie <airlied@linux.ie>,
devicetree@vger.kernel.org,
Jagan Teki <jagan@amarulasolutions.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Jonas Karlman <jonas@kwiboo.se>,
Robert Foss <robert.foss@linaro.org>,
Frank Rowand <frowand.list@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] dt-bindings: display: bridge: Drop requirement on input port for DSI devices
Date: Fri, 1 Apr 2022 03:22:19 +0200 [thread overview]
Message-ID: <b3dcf3fe-63a0-fbef-a3c4-f42e8cd395fe@denx.de> (raw)
In-Reply-To: <YkY+1IZtQ8oSi7wR@robh.at.kernel.org>
On 4/1/22 01:52, Rob Herring wrote:
> On Wed, 23 Mar 2022 16:48:23 +0100, Maxime Ripard wrote:
>> MIPI-DSI devices, if they are controlled through the bus itself, have to
>> be described as a child node of the controller they are attached to.
>>
>> Thus, there's no requirement on the controller having an OF-Graph output
>> port to model the data stream: it's assumed that it would go from the
>> parent to the child.
>>
>> However, some bridges controlled through the DSI bus still require an
>> input OF-Graph port, thus requiring a controller with an OF-Graph output
>> port. This prevents those bridges from being used with the controllers
>> that do not have one without any particular reason to.
>>
>> Let's drop that requirement.
>>
>> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
>> ---
>> .../devicetree/bindings/display/bridge/chipone,icn6211.yaml | 1 -
>> .../devicetree/bindings/display/bridge/toshiba,tc358762.yaml | 1 -
>> 2 files changed, 2 deletions(-)
>>
>
> I tend to agree with port@0 not being needed and really like
> consistency.
The consistent thing to do would be to always use port@0 and OF graph, no ?
next prev parent reply other threads:[~2022-04-01 1:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 15:48 [PATCH] dt-bindings: display: bridge: Drop requirement on input port for DSI devices Maxime Ripard
2022-03-23 20:38 ` Laurent Pinchart
2022-03-24 8:18 ` Maxime Ripard
2022-03-24 13:43 ` Laurent Pinchart
2022-03-24 14:23 ` Maxime Ripard
2022-03-24 14:50 ` Laurent Pinchart
2022-03-30 9:45 ` Maxime Ripard
2022-03-25 10:42 ` Tomi Valkeinen
2022-03-30 10:00 ` Maxime Ripard
2022-03-31 23:52 ` Rob Herring
2022-04-01 1:22 ` Marek Vasut [this message]
2022-04-01 9:58 ` Laurent Pinchart
2022-04-01 17:34 ` Rob Herring
2022-04-01 18:06 ` Marek Vasut
2022-04-01 18:21 ` Rob Herring
2022-04-01 18:25 ` Marek Vasut
2022-04-01 18:33 ` Rob Herring
2022-04-01 18:48 ` Laurent Pinchart
2022-04-01 19:43 ` Rob Herring
2022-04-05 7:52 ` (subset) " Maxime Ripard
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=b3dcf3fe-63a0-fbef-a3c4-f42e8cd395fe@denx.de \
--to=marex@denx.de \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=andrzej.hajda@intel.com \
--cc=daniel.vetter@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=frowand.list@gmail.com \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=maxime@cerno.tech \
--cc=narmstrong@baylibre.com \
--cc=robert.foss@linaro.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.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).