From: Hsin-Yi Wang <hsinyi@chromium.org>
To: dri-devel@lists.freedesktop.org
Cc: Archit Taneja <architt@codeaurora.org>,
Nicolas Boichat <drinkcat@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Thierry Reding <treding@nvidia.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Matthias Brugger <mbrugger@suse.com>,
p.zabel@pengutronix.de, linux-kernel@vger.kernel.org
Subject: [PATCH 3/4] dt-bindings: drm/bridge: analogix-anx78xx: support bypass GPIO
Date: Mon, 9 Dec 2019 20:20:12 +0800 [thread overview]
Message-ID: <20191209122013.178564-4-hsinyi@chromium.org> (raw)
In-Reply-To: <20191209122013.178564-1-hsinyi@chromium.org>
Support optional feature: bypass GPIO.
Some SoC (eg. mt8173) have a hardware mux that connects to 2 ports:
anx7688 and hdmi. When the GPIO is active, the bridge is bypassed.
Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
---
.../bindings/display/bridge/anx7688.txt | 40 ++++++++++++++++++-
1 file changed, 39 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/display/bridge/anx7688.txt b/Documentation/devicetree/bindings/display/bridge/anx7688.txt
index 78b55bdb18f7..44185dcac839 100644
--- a/Documentation/devicetree/bindings/display/bridge/anx7688.txt
+++ b/Documentation/devicetree/bindings/display/bridge/anx7688.txt
@@ -15,10 +15,13 @@ Required properties:
Optional properties:
- Video port for HDMI input, using the DT bindings defined in [1].
+ - bypass-gpios : External GPIO. If this GPIO is active, we assume
+ the bridge is bypassed (e.g. by a mux).
+ - pinctrl-0, pinctrl-names: the pincontrol settings to configure bypass GPIO.
[1]: Documentation/devicetree/bindings/media/video-interfaces.txt
-Example:
+Example 1:
anx7688: anx7688@2c {
compatible = "analogix,anx7688";
@@ -30,3 +33,38 @@ Example:
};
};
};
+
+Example 2:
+
+ anx7688: anx7688@2c {
+ compatible = "analogix,anx7688";
+ status = "okay";
+ reg = <0x2c>;
+ ddc-i2c-bus = <&hdmiddc0>;
+
+ bypass-gpios = <&pio 36 GPIO_ACTIVE_HIGH>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&hdmi_mux_pins>;
+
+ ports {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ port@0 { /* input */
+ reg = <0>;
+
+ anx7688_in: endpoint {
+ remote-endpoint = <&hdmi_out_anx>;
+ };
+ };
+
+ port@1 { /* output */
+ reg = <1>;
+
+ anx7688_out: endpoint {
+ remote-endpoint = <&hdmi_connector_in>;
+ };
+ };
+ };
+ };
+
--
2.24.0.393.g34dc348eaf-goog
next prev parent reply other threads:[~2019-12-09 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 12:20 [PATCH 0/4] drm: bridge: anx7688 and an optional feature Hsin-Yi Wang
2019-12-09 12:20 ` [PATCH 1/4] dt-bindings: drm/bridge: analogix-anx7688: Add ANX7688 transmitter binding Hsin-Yi Wang
2019-12-09 12:20 ` [PATCH 2/4] drm: bridge: anx7688: Add anx7688 bridge driver support Hsin-Yi Wang
2019-12-09 12:20 ` Hsin-Yi Wang [this message]
2019-12-09 12:20 ` [PATCH 4/4] drm: bridge: anx7688: Support bypass GPIO feature Hsin-Yi Wang
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=20191209122013.178564-4-hsinyi@chromium.org \
--to=hsinyi@chromium.org \
--cc=architt@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=drinkcat@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=p.zabel@pengutronix.de \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=treding@nvidia.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).