From: Philipp Zabel <p.zabel@pengutronix.de>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org, kernel@pengutronix.de,
Grant Likely <grant.likely@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH v3 0/9] imx-drm dt bindings
Date: Mon, 24 Feb 2014 16:36:37 +0100 [thread overview]
Message-ID: <1393256197.3091.49.camel@pizza.hi.pengutronix.de> (raw)
In-Reply-To: <1392723370-4772-1-git-send-email-p.zabel@pengutronix.de>
Am Dienstag, den 18.02.2014, 12:36 +0100 schrieb Philipp Zabel:
> Hi,
>
> here is an updated and more complete version of the imx-drm DT binding
> series. These patches apply on top of Russell's second preview of the
> imx-drm cleanup series on v3.14-rc2. 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 v3 also connections between display interface ports and encoders are
> used to find all necessary components, so that only the display interfaces
> have to be configured in the imx-drm node. This allows to move the imx-drm
> node into the SoC level dtsi. I've also updated the existing i.MX51 and
> i.MX53 device trees this time and updated/added the devicetree binding
> documentation.
>
> Patch 2/9 adds a temporary copy of the v4l2_of parser functions. Those
> are going to be moved to some place where they can be used by drm drivers,
> eventually, so those local copies can be dropped again.
Russell has sent a pull request for the imx-drm component support series
now, and we're at v3.13-rc4 already. This patch series still applies on
top of
git://ftp.arm.linux.org.uk/~rmk/linux-arm.git imx-drm-staging
I'd appreciate some feedback on this. Or shall I resend without the RFC?
regards
Philipp
> regards
> Philipp
>
> Lucas Stach (1):
> staging: imx-drm-core: don't request probe deferral in
> imx_drm_encoder_parse_of
>
> Philipp Zabel (8):
> staging: imx-drm: Add temporary copies of v4l2-of parsing functions
> staging: imx-drm-core: Use OF graph to find components and connections
> between encoder and crtcs
> staging: imx-drm: Document updated imx-drm device tree bindings
> staging: imx-drm: Document imx-hdmi device tree bindings
> ARM: dts: imx51: Add IPU ports and endpoints, move imx-drm node to
> dtsi
> ARM: dts: imx53: Add IPU DI ports and endpoints, move imx-drm node to
> dtsi
> ARM: dts: imx6qdl: Add IPU DI ports and endpoints, move imx-drm node
> to dtsi
> staging: imx-drm: Update TODO
>
> .../bindings/staging/imx-drm/fsl-imx-drm.txt | 48 ++++-
> .../devicetree/bindings/staging/imx-drm/hdmi.txt | 53 +++++
> .../devicetree/bindings/staging/imx-drm/ldb.txt | 20 +-
> arch/arm/boot/dts/imx51-apf51dev.dts | 11 +-
> arch/arm/boot/dts/imx51-babbage.dts | 28 ++-
> arch/arm/boot/dts/imx51.dtsi | 22 ++-
> arch/arm/boot/dts/imx53-m53evk.dts | 17 +-
> arch/arm/boot/dts/imx53-mba53.dts | 15 +-
> arch/arm/boot/dts/imx53-qsb.dts | 17 +-
> arch/arm/boot/dts/imx53.dtsi | 64 +++++-
> arch/arm/boot/dts/imx6dl.dtsi | 22 +--
> arch/arm/boot/dts/imx6q-sabresd.dts | 4 -
> arch/arm/boot/dts/imx6q.dtsi | 124 +++++++++++-
> arch/arm/boot/dts/imx6qdl-sabresd.dtsi | 6 -
> arch/arm/boot/dts/imx6qdl.dtsi | 138 ++++++++++++-
> drivers/staging/imx-drm/Makefile | 2 +-
> drivers/staging/imx-drm/TODO | 5 -
> drivers/staging/imx-drm/imx-drm-core.c | 217 ++++++++++++++-------
> drivers/staging/imx-drm/imx-drm-of.c | 132 +++++++++++++
> drivers/staging/imx-drm/imx-drm.h | 11 +-
> drivers/staging/imx-drm/imx-hdmi.c | 2 +-
> drivers/staging/imx-drm/imx-ldb.c | 4 +-
> drivers/staging/imx-drm/ipuv3-crtc.c | 47 ++++-
> 23 files changed, 842 insertions(+), 167 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/staging/imx-drm/hdmi.txt
> create mode 100644 drivers/staging/imx-drm/imx-drm-of.c
>
prev parent reply other threads:[~2014-02-24 15:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 11:36 [RFC PATCH v3 0/9] imx-drm dt bindings Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 1/9] staging: imx-drm-core: don't request probe deferral in imx_drm_encoder_parse_of Philipp Zabel
2014-02-24 15:49 ` Russell King - ARM Linux
2014-02-24 16:56 ` Philipp Zabel
2014-02-24 17:03 ` Philipp Zabel
2014-02-24 17:06 ` Russell King - ARM Linux
2014-02-24 17:41 ` Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 2/9] staging: imx-drm: Add temporary copies of v4l2-of parsing functions Philipp Zabel
2014-02-24 15:52 ` Russell King - ARM Linux
2014-02-24 17:31 ` Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 3/9] staging: imx-drm-core: Use OF graph to find components and connections between encoder and crtcs Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 4/9] staging: imx-drm: Document updated imx-drm device tree bindings Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 5/9] staging: imx-drm: Document imx-hdmi " Philipp Zabel
[not found] ` <1392723370-4772-1-git-send-email-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-02-18 11:36 ` [RFC PATCH v3 6/9] ARM: dts: imx51: Add IPU ports and endpoints, move imx-drm node to dtsi Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 9/9] staging: imx-drm: Update TODO Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 7/9] ARM: dts: imx53: Add IPU DI ports and endpoints, move imx-drm node to dtsi Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 8/9] ARM: dts: imx6qdl: " Philipp Zabel
2014-02-24 15:36 ` Philipp Zabel [this message]
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=1393256197.3091.49.camel@pizza.hi.pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
/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).