From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Andrzej Hajda <a.hajda@samsung.com>,
Swapnil Kashinath Jakhade <sjakhade@cadence.com>,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCHv2] dt-bindings: dp-connector: add binding for DisplayPort connector
Date: Thu, 17 Sep 2020 14:22:29 +0300 [thread overview]
Message-ID: <20200917112229.GR6112@intel.com> (raw)
In-Reply-To: <20200917055210.22868-1-tomi.valkeinen@ti.com>
On Thu, Sep 17, 2020 at 08:52:10AM +0300, Tomi Valkeinen wrote:
> Add binding for DisplayPort connector. A few notes:
>
> * Similar to hdmi-connector, it has hpd-gpios as an optional property,
> as the HPD could also be handled by, e.g., the DP bridge.
>
> * dp-pwr-supply, which provides 3.3V on DP_PWR pin, is optional, as it
> is not strictly required: standard DP cables do not even have the pin
> connected.
>
> * Connector type. Full size and mini connectors are identical except for
> the connector size and form, so I believe there is no functional need
> for this property. But similar to 'label' property, it might be used
> to present information about the connector to the userspace.
>
> * No eDP. There's really no "eDP connector", as it's always a custom
> made connection between the DP and the DP panel. So possibly there is
> no need for edp-connector binding, but even if there is, I don't want
> to guess what it could look like, and could it be part of the
> dp-connector binding.
>
> * No DP++. I'm not familiar with DP++, but I think it's all handled by
> the DP bridge, and does not need any new properties to the dp-connector.
You might need an i2c bus for this. It's up to the source device
to either hook up just AUX CH, or both AUX CH and DDC to a DP++
connector. If just AUX CH is wired up you are limited to using
only type2 DP dual mode adapters, whereas if you also have DDC
the crappier type1 adapters will also work.
I guess it's possible some bridges might handle all that for you.
But eg. on i915 we always set up both AUX CH and DDC, and some
extra circuitry on the board will isolate one or the other
depending on what kind of dongle/cable gets plugged in
(identified via the CONFIG pins).
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2020-09-17 11:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 5:52 [PATCHv2] dt-bindings: dp-connector: add binding for DisplayPort connector Tomi Valkeinen
2020-09-17 11:22 ` Ville Syrjälä [this message]
2020-09-17 12:39 ` Tomi Valkeinen
2020-09-17 21:35 ` Ville Syrjälä
2020-09-23 16:17 ` Rob Herring
2020-09-23 17:15 ` Tomi Valkeinen
2020-09-23 20:00 ` Rob Herring
2020-09-24 7:56 ` Tomi Valkeinen
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=20200917112229.GR6112@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sjakhade@cadence.com \
--cc=tomi.valkeinen@ti.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).