From: Rob Herring <robh@kernel.org>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: devicetree@vger.kernel.org,
Jernej Skrabec <jernej.skrabec@siol.net>,
Neil Armstrong <narmstrong@baylibre.com>,
Jonas Karlman <jonas@kwiboo.se>, Sekhar Nori <nsekhar@ti.com>,
dri-devel@lists.freedesktop.org,
Andrzej Hajda <a.hajda@samsung.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Swapnil Kashinath Jakhade <sjakhade@cadence.com>,
Nikhil Devshatwar <nikhil.nd@ti.com>
Subject: Re: [PATCH v4 1/2] dt-bindings: dp-connector: add binding for DisplayPort connector
Date: Mon, 30 Nov 2020 19:09:49 -0700 [thread overview]
Message-ID: <20201201020949.GA3495918@robh.at.kernel.org> (raw)
In-Reply-To: <20201130112919.241054-2-tomi.valkeinen@ti.com>
On Mon, 30 Nov 2020 13:29:18 +0200, 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, although the eDP spec
> does offer a few suggested pin setups. 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++. DP++ might need an i2c bus added
> to the bindings.
>
> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> .../display/connector/dp-connector.yaml | 56 +++++++++++++++++++
> 1 file changed, 56 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/display/connector/dp-connector.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-12-01 2:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 11:29 [PATCH v4 0/2] drm: add DisplayPort connector Tomi Valkeinen
2020-11-30 11:29 ` [PATCH v4 1/2] dt-bindings: dp-connector: add binding for " Tomi Valkeinen
2020-12-01 2:09 ` Rob Herring [this message]
2020-11-30 11:29 ` [PATCH v4 2/2] drm/bridge: display-connector: add DP support Tomi Valkeinen
2020-12-03 11:52 ` [PATCH v4 0/2] drm: add DisplayPort connector Tomi Valkeinen
2020-12-03 21:24 ` Sam Ravnborg
2020-12-08 9:14 ` 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=20201201020949.GA3495918@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=a.hajda@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=laurent.pinchart@ideasonboard.com \
--cc=narmstrong@baylibre.com \
--cc=nikhil.nd@ti.com \
--cc=nsekhar@ti.com \
--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).