From: Sean Paul <seanpaul@chromium.org>
To: devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
dri-devel@lists.freedesktop.org, robdclark@gmail.com,
daniel@ffwll.ch, airlied@linux.ie, marcheu@chromium.org
Cc: Sean Paul <seanpaul@chromium.org>
Subject: [PATCH v2 0/2] drm: Add drm_bridge and PTN3460 bridge driver
Date: Wed, 14 Aug 2013 16:47:36 -0400 [thread overview]
Message-ID: <1376513258-25703-1-git-send-email-seanpaul@chromium.org> (raw)
This patchset adds the drm_bridge abstraction as well as the PTN3460
DisplayPort to LVDS bridge driver (using drm_bridge, of course).
Changed in v2:
- Added PTN3460 driver to show drm_bridge usage
- Removed connector detect() re-route in favor of implementing the connector
in the bridge driver
- Removed the drm_bridge_helper_funcs and stuck everything in drm_bridge_funcs
- Added driver_private to drm_bridge
Sean Paul (2):
drm: Add drm_bridge
drm/bridge: Add PTN3460 bridge driver
.../devicetree/bindings/drm/bridge/ptn3460.txt | 27 ++
drivers/gpu/drm/Kconfig | 2 +
drivers/gpu/drm/Makefile | 1 +
drivers/gpu/drm/bridge/Kconfig | 5 +
drivers/gpu/drm/bridge/Makefile | 3 +
drivers/gpu/drm/bridge/ptn3460.c | 349 +++++++++++++++++++++
drivers/gpu/drm/drm_crtc.c | 50 +++
drivers/gpu/drm/drm_crtc_helper.c | 89 ++++--
include/drm/bridge/ptn3460.h | 36 +++
include/drm/drm_crtc.h | 55 ++++
10 files changed, 598 insertions(+), 19 deletions(-)
create mode 100644 Documentation/devicetree/bindings/drm/bridge/ptn3460.txt
create mode 100644 drivers/gpu/drm/bridge/Kconfig
create mode 100644 drivers/gpu/drm/bridge/Makefile
create mode 100644 drivers/gpu/drm/bridge/ptn3460.c
create mode 100644 include/drm/bridge/ptn3460.h
--
1.8.3
next reply other threads:[~2013-08-14 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 20:47 Sean Paul [this message]
2013-08-14 20:47 ` [PATCH v2 1/2] drm: Add drm_bridge Sean Paul
2013-08-14 20:47 ` [PATCH v2 2/2] drm/bridge: Add PTN3460 bridge driver Sean Paul
2013-08-15 15:28 ` Thierry Reding
2013-08-15 19:32 ` Sean Paul
2013-08-15 20:42 ` Thierry Reding
2013-08-15 20:51 ` Sean Paul
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=1376513258-25703-1-git-send-email-seanpaul@chromium.org \
--to=seanpaul@chromium.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=marcheu@chromium.org \
--cc=robdclark@gmail.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;
as well as URLs for NNTP newsgroup(s).