From: Maxime Ripard <maxime@cerno.tech>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Chen-Yu Tsai <wens@csie.org>, Maxime Ripard <maxime@cerno.tech>,
Jernej Skrabec <jernej.skrabec@siol.net>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Daniel Vetter <daniel.vetter@intel.com>,
David Airlie <airlied@linux.ie>
Cc: dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/7] drm/sun4i: Add support for dual-link LVDS on the A20
Date: Fri, 19 Feb 2021 14:59:27 +0100 [thread overview]
Message-ID: <20210219135934.618684-1-maxime@cerno.tech> (raw)
Hi,
This is a fourth attempt at supporting the LVDS dual-link output on the
Allwinner A20.
Let me know what you think,
Maxime
Changes from v3:
- Reintroduce the endpoint sanity check (and make of_graph_get_port_by_id
const in the process)
- Make a few doc fixes
- Fix device_node leakage
- Changed allwinner,lvds-companion to more generic link-companion
- Rebased on 5.11
Changes from v2:
- Added the DT binding description
- Split the patch to enable the A20
- Reworked a bit the error messages
Changes from v1:
- Reworked the DT bindings
- Refactored a bit the panel registration in the tcon code.
Maxime Ripard (7):
of: Make of_graph_get_port_by_id take a const device_node
drm/of: Change the prototype of drm_of_lvds_get_dual_link_pixel_order
dt-bindings: display: sun4i: Add LVDS Dual-Link property
drm/sun4i: tcon: Refactor the LVDS and panel probing
drm/sun4i: tcon: Support the LVDS Dual-Link
drm/sun4i: tcon: Enable the A20 dual-link output
[DO NOT MERGE] ARM: dts: sun7i: Enable LVDS Dual-Link on the
Cubieboard
.../display/allwinner,sun4i-a10-tcon.yaml | 6 +
arch/arm/boot/dts/sun7i-a20-cubieboard2.dts | 69 ++++++++
drivers/gpu/drm/drm_of.c | 138 +++++++++++----
drivers/gpu/drm/rcar-du/rcar_lvds.c | 8 +-
drivers/gpu/drm/sun4i/sun4i_tcon.c | 164 ++++++++++--------
drivers/gpu/drm/sun4i/sun4i_tcon.h | 4 +
drivers/of/property.c | 2 +-
include/drm/drm_of.h | 16 +-
include/linux/of_graph.h | 4 +-
9 files changed, 299 insertions(+), 112 deletions(-)
--
2.29.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-02-19 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 13:59 Maxime Ripard [this message]
2021-02-19 13:59 ` [PATCH v4 1/7] of: Make of_graph_get_port_by_id take a const device_node Maxime Ripard
2021-02-19 13:59 ` [PATCH v4 2/7] drm/of: Change the prototype of drm_of_lvds_get_dual_link_pixel_order Maxime Ripard
2021-02-19 13:59 ` [PATCH v4 3/7] dt-bindings: display: sun4i: Add LVDS Dual-Link property Maxime Ripard
2021-02-19 13:59 ` [PATCH v4 4/7] drm/sun4i: tcon: Refactor the LVDS and panel probing Maxime Ripard
2021-02-19 13:59 ` [PATCH v4 5/7] drm/sun4i: tcon: Support the LVDS Dual-Link Maxime Ripard
2021-02-19 13:59 ` [PATCH v4 6/7] drm/sun4i: tcon: Enable the A20 dual-link output Maxime Ripard
2021-02-19 13:59 ` [PATCH v4 7/7] [DO NOT MERGE] ARM: dts: sun7i: Enable LVDS Dual-Link on the Cubieboard Maxime Ripard
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=20210219135934.618684-1-maxime@cerno.tech \
--to=maxime@cerno.tech \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frowand.list@gmail.com \
--cc=jernej.skrabec@siol.net \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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