drm/rockchip: hdmi support for rk3328
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest7 of 8 patches 13 repliesIn review
- v18 of 9 patches 5 repliesSuperseded
Changes in v2 from the cover letter
- 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
7 of 8 patches are in this archive. The cover letter announces 8.
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 2/8 | phy: add Rockchip Innosilicon hdmi phydrivers/ drivers/ drivers/ | +1217 | 0 replies | |
| 3/8 | drm/bridge: dw-hdmi: allow overriding of phy-type readingdrivers/ include/ | +4 | 5 replies | |
| 4/8 | drm/rockchip: dw_hdmi: Allow outputs that don't need output switchingdrivers/ | +4 | 2 replies | |
| 5/8 | dt-bindings: allow optional phys in Rockchip dw_hdmi bindingDocumentation/ | +2 | 1 reply | |
| 6/8 | drm/rockchip: dw_hdmi: allow including external physdrivers/ | +10 | 0 replies | |
| 7/8 | drm/rockchip: dw_hdmi: store rockchip_hdmi reference in phy_data objectdrivers/ | +7 | 1 reply | |
| 8/8 | drm/rockchip: dw_hdmi: add dw-hdmi support for the rk3328Documentation/ drivers/ | +107 | 3 replies |
Reviews trailers per patch
1 of 7 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Rob Herring | Laurent Pinchart | Robin Murphy |
|---|---|---|---|
| Series | R-b | T-b | |
| 2/8 | |||
| 3/8 | T-b | ||
| 4/8 | |||
| 5/8 | R-b | ||
| 6/8 | |||
| 7/8 | |||
| 8/8 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 3 reviewers.
Cover letter [PATCH v2 0/8] drm/rockchip: hdmi support for rk3328
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.
I've put both the phy driver and dw-hdmi changes into one series just to showcase how everything comes together, but would of course still expect things to go through the separate phy and drm trees once deemed ready.
So patches 1+2 are expected to go through the phy-tree and the rest should go through the drm tree.
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 overriding of phy-type reading 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
Zheng Yang (2):
dt-bindings: add binding for Rockchip hdmi phy using an Innosilicon IP
phy: add Rockchip Innosilicon hdmi phy
.../bindings/display/rockchip/dw_hdmi-rockchip.txt | 3 + .../bindings/phy/phy-rockchip-inno-hdmi.txt | 42 + drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 4 +- drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 130 ++- drivers/phy/rockchip/Kconfig | 7 + drivers/phy/rockchip/Makefile | 1 + drivers/phy/rockchip/phy-rockchip-inno-hdmi.c | 1209 ++++++++++++++++++++ include/drm/bridge/dw_hdmi.h | 1 + 8 files changed, 1393 insertions(+), 4 deletions(-) create mode 100644 Documentation/devicetree/bindings/phy/phy-rockchip-inno-hdmi.txt create mode 100644 drivers/phy/rockchip/phy-rockchip-inno-hdmi.c
Signature · 6 lines
2.15.1 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html