From: Heiko Stuebner <heiko@sntech.de>
To: architt@codeaurora.org, a.hajda@samsung.com
Cc: mark.rutland@arm.com, Jose.Abreu@synopsys.com,
algea.cao@rock-chips.com, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
Laurent.pinchart@ideasonboard.com,
linux-arm-kernel@lists.infradead.org, zhengyang@rock-chips.com
Subject: [PATCH v3 0/6] drm/rockchip: hdmi support for rk3328
Date: Tue, 15 May 2018 15:47:30 +0200 [thread overview]
Message-ID: <20180515134736.5824-1-heiko@sntech.de> (raw)
The rk3228/rk3229 and rk3328 socs started using a new type of hdmi-phy
from Innosilicon that resides completely separate from the dw-hdmi block
and gets accessed via mmio.
Additionally the rk3328 dw-hdmi does not report the vendor-phy type
but a different one instead, so add the possibility to override the
phy type when the glue driver knows better than the ip block itself.
changes in v3:
- split off phy driver into a separate series
- only allow forcing vendor phy type
- wording fixes and other nits
changes in v2:
- phy: prevent overflow in tmdsclk calculation
as reported by Martin Cerveny
- phy: use unsigned long for all tmdsclk rate uses
- phy: simplify tmds rate calculation
- dropped patch exporting some dw-hdmi phy functions
as a similar patch entered drm-misc already
Heiko Stuebner (6):
drm/bridge: dw-hdmi: allow forcing vendor phy-type
drm/rockchip: dw_hdmi: Allow outputs that don't need output switching
dt-bindings: allow optional phys in Rockchip dw_hdmi binding
drm/rockchip: dw_hdmi: allow including external phys
drm/rockchip: dw_hdmi: store rockchip_hdmi reference in phy_data
object
drm/rockchip: dw_hdmi: add dw-hdmi support for the rk3328
.../display/rockchip/dw_hdmi-rockchip.txt | 3 +
drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 4 +-
drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 130 +++++++++++++++++-
include/drm/bridge/dw_hdmi.h | 1 +
4 files changed, 134 insertions(+), 4 deletions(-)
--
2.17.0
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-05-15 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 13:47 Heiko Stuebner [this message]
2018-05-15 13:47 ` [PATCH v3 1/6] drm/bridge: dw-hdmi: allow forcing vendor phy-type Heiko Stuebner
2018-05-15 13:47 ` [PATCH v3 2/6] drm/rockchip: dw_hdmi: Allow outputs that don't need output switching Heiko Stuebner
2018-05-15 13:47 ` [PATCH v3 3/6] dt-bindings: allow optional phys in Rockchip dw_hdmi binding Heiko Stuebner
2018-05-15 13:47 ` [PATCH v3 4/6] drm/rockchip: dw_hdmi: allow including external phys Heiko Stuebner
2018-05-15 13:47 ` [PATCH v3 5/6] drm/rockchip: dw_hdmi: store rockchip_hdmi reference in phy_data object Heiko Stuebner
2018-05-15 13:47 ` [PATCH v3 6/6] drm/rockchip: dw_hdmi: add dw-hdmi support for the rk3328 Heiko Stuebner
2018-05-22 17:13 ` Rob Herring
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=20180515134736.5824-1-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=Jose.Abreu@synopsys.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=algea.cao@rock-chips.com \
--cc=architt@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=zhengyang@rock-chips.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