From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Kumar Gala <galak@codeaurora.org>,
Grant Likely <grant.likely@linaro.org>
Subject: [PATCH RFC 00/15] Armada DRM updates
Date: Sat, 5 Jul 2014 11:37:24 +0100 [thread overview]
Message-ID: <20140705103724.GN21766@n2100.arm.linux.org.uk> (raw)
This patch series updates the Armada DRM driver to be more DT friendly
by converting it to the component helper. This is an incomplete
conversion as we also need to convert the TDA998x as well, hence it
currently retains the existing method of initialisation using the slave
encoder mechanism. The old mechanism will be removed once the
conversion is complete.
This series includes the component updates (patches 1-3 which have been
recently merged into Greg's driver tree, patch 9 which is scheduled to
be merged) and the recently posted DRM OF helper for encoders (patch 8).
Hence patches 1-3 and 9 are only included for reference purposes.
Please direct comments for patch 8 to the previously posted RFC for
that single patch.
The general idea here is to permit each CRTC device to exist as a
separate device node in DT (as it should be) with all the appropriate
properties such as base address, interrupt and pixel clocks.
The encoders (which may be off-SoC) will be specified separately in DT,
and the connectivity specified via the DT's graph bindings.
The diffstat below is for the entire series, which includes the
component helpre updates and the DRM OF helper.
.../bindings/drm/armada/marvell,dove-lcd.txt | 30 +++
arch/arm/boot/dts/dove.dtsi | 14 ++
drivers/base/component.c | 192 +++++++++++++----
drivers/gpu/drm/Makefile | 1 +
drivers/gpu/drm/armada/armada_510.c | 23 +-
drivers/gpu/drm/armada/armada_crtc.c | 188 +++++++++++++++--
drivers/gpu/drm/armada/armada_crtc.h | 9 +-
drivers/gpu/drm/armada/armada_drm.h | 13 +-
drivers/gpu/drm/armada/armada_drv.c | 233 ++++++++++++++-------
drivers/gpu/drm/drm_of.c | 65 ++++++
include/drm/drm_crtc.h | 2 +
include/drm/drm_of.h | 18 ++
include/linux/component.h | 7 +
13 files changed, 642 insertions(+), 153 deletions(-)
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next reply other threads:[~2014-07-05 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 10:37 Russell King - ARM Linux [this message]
[not found] ` <20140705103724.GN21766-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2014-07-05 10:38 ` [PATCH RFC 12/15] dt-bindings: add Marvell Dove LCD controller documentation Russell King
2014-07-05 10:38 ` [PATCH RFC 13/15] drm/armada: permit CRTCs to be registered as separate devices Russell King
2014-07-05 10:39 ` [PATCH RFC 15/15] ARM: dts: dove: add DT LCD controllers Russell King
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=20140705103724.GN21766@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).