linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/5] drm: add support for Cadence MHDP DPI/DP bridge.
Date: Thu, 13 Sep 2018 14:31:45 +0200	[thread overview]
Message-ID: <11916444.D1tlAhbW8U@phil> (raw)
In-Reply-To: <1535451894-2518-1-git-send-email-dkos@cadence.com>

Am Dienstag, 28. August 2018, 12:24:43 CEST schrieb Damian Kos:
> Hello!
> 
> This is the series of patches that will add support for the Cadence's DPI/DP
> bridge. Please note that this is a preliminary version of the driver and there
> will be more patches in the future with updates, fixes and improvements.
> Please keep that in mind when looking at FIXME/TODO/XXX comments.
> 
> Initially, MHDP driver was developed as a DRM bridge driver and was planed to
> be placed in drivers/gpu/drm/bridge/mhdp.c.  However, there was already
> a driver for Cadence's DP controller developed by RockChip, but that driver
> uses the different DRM framework and looks like a part of a bigger system.
> Both controllers (including firmware) are quite different internally
> (MST/FEC/DSC support, link training done by driver, additional commands, IRQ's
> etc.) but they have similar register map, except for Framer/Streamer (which is
> noticeably different), so they appear similar.
> 
> The following patches contain:
> - Moving common code to drivers/gpu/drm/bridge/cdns-mhdp-common.* and
>   modifying it a bit (mostly new prefixes for functions and data types) so it
>   can be used by two, higher level, drivers.
> - Modifying existing RockChip's DP driver to use the common code after changes
>   made to it (use the new cdns_mhdp_device structure and new function names).
> - Modifying DRM helpers a bit. Some are required for new driver, some are
>   updates from DP 1.2 to 1.3 or 1.4.
> - Adding documentation for device tree bindings.
> - Adding preliminary Cadence DPI/DP bridge driver.
> 
> Some of the things that will be added later on include (but are not limited
> to):
> - Support for Cadence SD0801 PHY (PHY's driver should be on the way by now)
> - MST support
> - DSC support
> - FEC support
> - HDCP support

with te Kconfig issue in patch5 fixed, this series tested on
rk3288 (analogix-dp) and rk3399 (analogix-dp + cadence-dp)
Everything seems to work that worked before.

Tested-by: Heiko Stuebner <heiko@sntech.de>

  parent reply	other threads:[~2018-09-13 12:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 10:24 [PATCH v3 0/5] drm: add support for Cadence MHDP DPI/DP bridge Damian Kos
2018-08-28 10:24 ` [PATCH v3 1/5] drm/rockchip: prepare common code for cdns and rk dpi/dp driver Damian Kos
2018-09-13 10:00   ` Andrzej Hajda
2018-09-13 10:15     ` Damian Kos
2018-08-28 10:24 ` [PATCH v3 2/5] drm/dp: fix link probing for devices supporting DP 1.4+ Damian Kos
2018-09-13 11:08   ` Andrzej Hajda
2018-08-28 10:24 ` [PATCH v3 3/5] drm/dp: make dp_link_status and dp_get_lane_status usable from outside of the core Damian Kos
2018-09-13 11:20   ` Andrzej Hajda
2018-08-28 10:24 ` [PATCH v3 4/5] dt-bindings: drm/bridge Document Cadence MHDP DPI/DP bridge bindings Damian Kos
2018-08-29  0:28   ` Rob Herring
2018-09-13 11:23   ` Andrzej Hajda
2018-08-28 10:24 ` [PATCH v3 5/5] drm/bridge: add preliminary driver for cadence dpi/dp bridge Damian Kos
2018-09-13 12:30   ` Heiko Stuebner
2018-09-13 12:31 ` Heiko Stuebner [this message]
2018-09-18 13:18   ` [PATCH v3 0/5] drm: add support for Cadence MHDP DPI/DP bridge Damian Kos

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=11916444.D1tlAhbW8U@phil \
    --to=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).