From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 0/4] imx-drm dt bindings
Date: Tue, 11 Feb 2014 12:45:40 +0100 [thread overview]
Message-ID: <1392119144-27868-1-git-send-email-p.zabel@pengutronix.de> (raw)
Hi,
these patches apply on top of Russell's second preview of the
imx-drm cleanup series. I have added device tree bindings between
IPU and the encoders as documented in
Documentation/devicetree/bindings/media/video-interfaces.txt
and used those to determine the possible_crtcs and mux_id.
The crtc cookie is replaced with a the port device tree node,
which is unique and therefore allows to get rid of the di_id
comparison. Storing the multiplexer input numbers in the device
tree removes the need to know the ipu_id. This should also allow
to replace IPU2 with LCDIF on i.MX6 Solo more easily.
In v2 I've added temporary copies of the v4l2_of helpers to imx-drm
and tested it on the SolidRun Hummingboard.
regards
Philipp
Philipp Zabel (4):
staging: imx-drm: Add temporary copies of v4l2-of parsing functions
staging: imx-drm-core: Use graph to find connection between crtc and
encoder
staging: imx-drm-core: associate crtc devices with di port nodes
ARM: dts: imx6qdl: Add ports and endpoints to IPU DIs
arch/arm/boot/dts/imx6dl.dtsi | 9 +--
arch/arm/boot/dts/imx6q.dtsi | 115 +++++++++++++++++++++++++--
arch/arm/boot/dts/imx6qdl.dtsi | 137 ++++++++++++++++++++++++++++++++-
drivers/staging/imx-drm/Makefile | 2 +-
drivers/staging/imx-drm/imx-drm-core.c | 82 +++++++++++++-------
drivers/staging/imx-drm/imx-drm-of.c | 106 +++++++++++++++++++++++++
drivers/staging/imx-drm/imx-drm.h | 9 ++-
drivers/staging/imx-drm/imx-hdmi.c | 2 +-
drivers/staging/imx-drm/imx-ldb.c | 4 +-
drivers/staging/imx-drm/ipuv3-crtc.c | 39 +++++++++-
10 files changed, 453 insertions(+), 52 deletions(-)
create mode 100644 drivers/staging/imx-drm/imx-drm-of.c
--
1.8.5.3
next reply other threads:[~2014-02-11 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 11:45 Philipp Zabel [this message]
2014-02-11 11:45 ` [RFC PATCH v2 1/4] staging: imx-drm: Add temporary copies of v4l2-of parsing functions Philipp Zabel
2014-02-11 11:45 ` [RFC PATCH v2 2/4] staging: imx-drm-core: Use graph to find connection between crtc and encoder Philipp Zabel
2014-02-11 11:45 ` [RFC PATCH v2 3/4] staging: imx-drm-core: associate crtc devices with di port nodes Philipp Zabel
2014-02-11 11:45 ` [RFC PATCH v2 4/4] ARM: dts: imx6qdl: Add ports and endpoints to IPU DIs Philipp Zabel
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=1392119144-27868-1-git-send-email-p.zabel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).