aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/include/drm/bridge
diff options
context:
space:
mode:
authorHeiko Stuebner <heiko@sntech.de>2018-09-12 14:47:35 +0200
committerHeiko Stuebner <heiko@sntech.de>2018-09-28 11:49:33 +0200
commit8faff37409fb47d86c839bb2da9f2cff371a3ef1 (patch)
treed1f250136174568a70e8003418fbd12925f93a65 /include/drm/bridge
parentdrm: stm: implement get_scanout_position function (diff)
downloadwireguard-linux-8faff37409fb47d86c839bb2da9f2cff371a3ef1.tar.xz
wireguard-linux-8faff37409fb47d86c839bb2da9f2cff371a3ef1.zip
drm/bridge: dw-hdmi: allow forcing vendor phy-type
In some IP implementations the reading of the phy-type may be broken. One example are the Rockchip rk3228 and rk3328 socs that use a separate vendor-type phy from Innosilicon but still report the HDMI20_TX type. So allow the glue driver to force the vendor-phy for these cases. In the future it may be necessary to allow forcing other types, but for now we'll keep it simply to the case actually seen in the wild. changes in v3: - only allow forcing vendor type, as suggested by Laurent Signed-off-by: Heiko Stuebner <heiko@sntech.de> Tested-by: Robin Murphy <robin.murphy@arm.com> Reviewed-by: Andrzej Hajda <a.hajda@samsung.com> Reviewed-by: Zheng Yang <zhengyang@rock-chips.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180912124740.20343-2-heiko@sntech.de Link: https://patchwork.freedesktop.org/patch/msgid/20180912124740.20343-3-heiko@sntech.de
Diffstat (limited to 'include/drm/bridge')
-rw-r--r--include/drm/bridge/dw_hdmi.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/drm/bridge/dw_hdmi.h b/include/drm/bridge/dw_hdmi.h
index ccb5aa8468e0..9c56412bb2cf 100644
--- a/include/drm/bridge/dw_hdmi.h
+++ b/include/drm/bridge/dw_hdmi.h
@@ -133,6 +133,7 @@ struct dw_hdmi_plat_data {
const struct dw_hdmi_phy_ops *phy_ops;
const char *phy_name;
void *phy_data;
+ unsigned int phy_force_vendor;
/* Synopsys PHY support */
const struct dw_hdmi_mpll_config *mpll_cfg;