From: Rui Miguel Silva <rui.silva@linaro.org>
To: Shawn Guo <shawnguo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
devicetree@vger.kernel.org,
Rui Miguel Silva <rui.silva@linaro.org>
Subject: [PATCH 0/5] ARM: imx7s: add media nodes
Date: Tue, 19 Mar 2019 16:59:58 +0000 [thread overview]
Message-ID: <20190319170003.21261-1-rui.silva@linaro.org> (raw)
This series is a continuation of the
[PATCH v14 00/13] media: staging/imx7: add i.MX7 media driver [0] series.
All code patches and bindings are already merged, missing only this dts patches.
The main difference from the version in the previous series is as
commented by Laurent:
- split of dtsi and dts in 2 patches
- push endpoints to imx7s.dtsi
Cheers,
Rui
[0] https://lore.kernel.org/linux-media/20190206151328.21629-1-rui.silva@linaro.org/
Rui Miguel Silva (5):
ARM: dts: imx7s: add mipi phy power domain
ARM: dts: imx7s: add multiplexer controls
ARM: dts: imx7s: Add video mux, csi and mipi_csi
ARM: dts: imx7s-warp: add csi and mipi_csi node
ARM: dts: imx7s-warp: add ov2680 sensor node
arch/arm/boot/dts/imx7s-warp.dts | 55 ++++++++++++++++++++
arch/arm/boot/dts/imx7s.dtsi | 87 +++++++++++++++++++++++++++++++-
2 files changed, 140 insertions(+), 2 deletions(-)
--
2.21.0
next reply other threads:[~2019-03-19 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 16:59 Rui Miguel Silva [this message]
2019-03-19 16:59 ` [PATCH 1/5] ARM: dts: imx7s: add mipi phy power domain Rui Miguel Silva
2019-03-19 17:00 ` [PATCH 2/5] ARM: dts: imx7s: add multiplexer controls Rui Miguel Silva
2019-03-19 17:00 ` [PATCH 3/5] ARM: dts: imx7s: Add video mux, csi and mipi_csi Rui Miguel Silva
2019-03-26 8:23 ` Shawn Guo
2019-03-19 17:00 ` [PATCH 4/5] ARM: dts: imx7s-warp: add csi and mipi_csi node Rui Miguel Silva
2019-03-26 8:25 ` Shawn Guo
2019-03-19 17:00 ` [PATCH 5/5] ARM: dts: imx7s-warp: add ov2680 sensor node Rui Miguel Silva
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=20190319170003.21261-1-rui.silva@linaro.org \
--to=rui.silva@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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).