dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: dri-devel@lists.freedesktop.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Andrzej Hajda <a.hajda@samsung.com>,
	Jernej Skrabec <jernej.skrabec@siol.net>,
	Neil Armstrong <narmstrong@baylibre.com>,
	Sam Ravnborg <sam@ravnborg.org>, Jonas Karlman <jonas@kwiboo.se>
Subject: [PATCH v5 0/5] drm/bridge: Update tc358767 and nxp-ptn3460 to support chained bridges
Date: Mon, 27 Jul 2020 19:03:15 +0200	[thread overview]
Message-ID: <20200727170320.959777-1-sam@ravnborg.org> (raw)

This patch-set aims to make connector creation optional
and prepare the bridge drivers for use in a chained setup.

The objective is that all bridge drivers shall support a chained setup
connector creation is moved to the display drivers.
This is just one step on this path.

The general approach for the bridge drivers:
- Introduce bridge operations
- Introduce use of panel bridge and make connector creation optional

v5:
  - Applied reviewed patches, so we went from 15 to 5
  - Fixed bug in connector creation in both drivers

v4:
  - Dropped patch for ti-sn65dsi86. Await full conversion
  - Dropped patch for ti-tpd12s015. It was wrong (Laurent)
  - Drop boe,hv070wsa-100 patch, it was applied
  - Combined a few patches to fix connector created twice (Laurent)
  - Fix memory leak in get_edid (Laurent)
  - Added patch to validate panel descriptions in panel-simple
  - Set bridge.type in relevant drivers
 
v3:
  - Rebase on top of drm-misc-next
  - Address kbuild test robot feedback
 
v2:
  - Updated bus_flags for boe,hv070wsa-100
  - Collected r-b, but did not apply patches yet
  - On the panel side the panel-simple driver gained a default
    connector type for all the dumb panels that do not
    include so in their description.
    With this change panels always provide a connector type,
    and we have the potential to drop most uses of
    devm_drm_panel_bridge_add_typed().
  - Added conversion of a few more bridge drivers

Patches can build but no run-time testing.
So both test and review feedback appreciated!

	Sam


Sam Ravnborg (5):
      drm/bridge: tc358767: add detect bridge operation
      drm/bridge: tc358767: add get_edid bridge operation
      drm/bridge: tc358767: add drm_panel_bridge support
      drm/bridge: nxp-ptn3460: add get_edid bridge operation
      drm/bridge: nxp-ptn3460: add drm_panel_bridge support

 drivers/gpu/drm/bridge/nxp-ptn3460.c | 103 +++++++++++++---------------
 drivers/gpu/drm/bridge/tc358767.c    | 126 +++++++++++++++++++----------------
 2 files changed, 114 insertions(+), 115 deletions(-)


_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2020-07-27 17:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 17:03 Sam Ravnborg [this message]
2020-07-27 17:03 ` [PATCH v5 1/5] drm/bridge: tc358767: add detect bridge operation Sam Ravnborg
2020-07-27 17:03 ` [PATCH v5 2/5] drm/bridge: tc358767: add get_edid " Sam Ravnborg
2020-07-27 17:03 ` [PATCH v5 3/5] drm/bridge: tc358767: add drm_panel_bridge support Sam Ravnborg
2020-07-27 17:12   ` Laurent Pinchart
2020-07-27 17:03 ` [PATCH v5 4/5] drm/bridge: nxp-ptn3460: add get_edid bridge operation Sam Ravnborg
2020-07-27 17:03 ` [PATCH v5 5/5] drm/bridge: nxp-ptn3460: add drm_panel_bridge support Sam Ravnborg
2020-07-27 17:13   ` Laurent Pinchart
2020-07-27 17:26 ` [PATCH v5 0/5] drm/bridge: Update tc358767 and nxp-ptn3460 to support chained bridges Sam Ravnborg

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=20200727170320.959777-1-sam@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=a.hajda@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@siol.net \
    --cc=jonas@kwiboo.se \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=narmstrong@baylibre.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