From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: dri-devel@lists.freedesktop.org
Cc: linux-renesas-soc@vger.kernel.org, Dave Airlie <airlied@gmail.com>
Subject: [GIT PULL FOR v5.3] R-Car DU changes
Date: Sat, 8 Jun 2019 02:47:43 +0300 [thread overview]
Message-ID: <20190607234743.GD5110@pendragon.ideasonboard.com> (raw)
Hi Dave,
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
git://linuxtv.org/pinchartl/media.git tags/du-next-20190608
for you to fetch changes up to 8e8fddab0d0acdefb1ad76852d954b2bbaa3896d:
drm: rcar-du: Skip LVDS1 output on Gen3 when using dual-link LVDS mode (2019-06-08 02:36:04 +0300)
----------------------------------------------------------------
R-Car DU changes for v5.3:
- R8A774A1 SoC support
- LVDS dual-link mode support
- Misc fixes
----------------------------------------------------------------
Biju Das (4):
dt-bindings: display: renesas: du: Document the r8a774a1 bindings
dt-bindings: display: renesas: lvds: Document r8a774a1 bindings
drm: rcar-du: Add R8A774A1 support
drm: rcar-du: lvds: Add r8a774a1 support
Kieran Bingham (1):
drm: rcar-du: writeback: include interface header
Laurent Pinchart (7):
drm: bridge: Add dual_link field to the drm_bridge_timings structure
dt-bindings: display: bridge: thc63lvd1024: Document dual-link operation
drm: bridge: thc63: Report input bus mode through bridge timings
dt-bindings: display: renesas: lvds: Add renesas,companion property
drm: rcar-du: lvds: Remove LVDS double-enable checks
drm: rcar-du: lvds: Add support for dual-link mode
drm: rcar-du: Skip LVDS1 output on Gen3 when using dual-link LVDS mode
.../bindings/display/bridge/renesas,lvds.txt | 19 ++-
.../bindings/display/bridge/thine,thc63lvd1024.txt | 6 +
.../devicetree/bindings/display/renesas,du.txt | 2 +
drivers/gpu/drm/bridge/thc63lvd1024.c | 54 +++++++--
drivers/gpu/drm/rcar-du/rcar_du_drv.c | 30 +++++
drivers/gpu/drm/rcar-du/rcar_du_encoder.c | 12 ++
drivers/gpu/drm/rcar-du/rcar_du_kms.c | 2 +-
drivers/gpu/drm/rcar-du/rcar_du_writeback.c | 1 +
drivers/gpu/drm/rcar-du/rcar_lvds.c | 127 +++++++++++++++------
drivers/gpu/drm/rcar-du/rcar_lvds.h | 5 +
include/drm/drm_bridge.h | 8 ++
11 files changed, 218 insertions(+), 48 deletions(-)
--
Regards,
Laurent Pinchart
next reply other threads:[~2019-06-07 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 23:47 Laurent Pinchart [this message]
2019-06-08 13:46 ` [GIT PULL FOR v5.3] R-Car DU changes, v2 Laurent Pinchart
2019-06-11 11:14 ` Daniel Vetter
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=20190607234743.GD5110@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-renesas-soc@vger.kernel.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