From: Rui Miguel Silva <rui.silva@linaro.org>
To: mchehab@kernel.org, sakari.ailus@linux.intel.com,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>
Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ryan Harkin <ryan.harkin@linaro.org>,
Rui Miguel Silva <rui.silva@linaro.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
linux-media@vger.kernel.org
Subject: [PATCH v7 11/12] media: staging/imx: add i.MX7 entries to TODO file
Date: Fri, 10 Aug 2018 15:20:44 +0100 [thread overview]
Message-ID: <20180810142045.27657-12-rui.silva@linaro.org> (raw)
In-Reply-To: <20180810142045.27657-1-rui.silva@linaro.org>
Add some i.MX7 related entries to TODO file.
Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
---
drivers/staging/media/imx/TODO | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/drivers/staging/media/imx/TODO b/drivers/staging/media/imx/TODO
index aeeb15494a49..6f29b5ca5324 100644
--- a/drivers/staging/media/imx/TODO
+++ b/drivers/staging/media/imx/TODO
@@ -45,3 +45,12 @@
Which means a port must not contain mixed-use endpoints, they
must all refer to media links between V4L2 subdevices.
+
+- i.MX7: all of the above, since it uses the imx media core
+
+- i.MX7: use Frame Interval Monitor
+
+- i.MX7: runtime testing with parallel sensor, links setup and streaming
+
+- i.MX7: runtime testing with different formats, for the time only 10-bit bayer
+ is tested
--
2.18.0
next prev parent reply other threads:[~2018-08-10 14:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 14:20 [PATCH v7 00/12] media: staging/imx7: add i.MX7 media driver Rui Miguel Silva
2018-08-10 14:20 ` [PATCH v7 01/12] media: staging/imx: refactor imx media device probe Rui Miguel Silva
2018-08-10 14:20 ` [PATCH v7 02/12] media: staging/imx: rearrange group id to take in account IPU Rui Miguel Silva
2018-08-10 14:20 ` [PATCH v7 03/12] media: staging/imx7: add imx7 CSI subdev driver Rui Miguel Silva
2018-08-10 14:20 ` [PATCH v7 04/12] media: staging/imx7: add MIPI CSI-2 receiver subdev for i.MX7 Rui Miguel Silva
2018-08-10 14:20 ` [PATCH v7 05/12] media: dt-bindings: add bindings for i.MX7 media driver Rui Miguel Silva
2018-11-07 10:41 ` Sakari Ailus
2018-08-10 14:20 ` [PATCH v7 06/12] ARM: dts: imx7s: add mipi phy power domain Rui Miguel Silva
2018-08-10 14:20 ` [PATCH v7 07/12] ARM: dts: imx7s: add multiplexer controls Rui Miguel Silva
2018-08-10 14:20 ` [PATCH v7 08/12] ARM: dts: imx7: Add video mux, csi and mipi_csi and connections Rui Miguel Silva
2018-08-10 14:20 ` [PATCH v7 09/12] ARM: dts: imx7s-warp: add ov2680 sensor node Rui Miguel Silva
2018-08-10 14:20 ` [PATCH v7 10/12] media: imx7.rst: add documentation for i.MX7 media driver Rui Miguel Silva
2018-08-10 14:20 ` Rui Miguel Silva [this message]
2018-08-10 14:20 ` [PATCH v7 12/12] media: video-mux: add bayer formats Rui Miguel Silva
2018-11-07 9:58 ` [PATCH v7 00/12] media: staging/imx7: add i.MX7 media driver Hans Verkuil
2018-11-07 10:04 ` 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=20180810142045.27657-12-rui.silva@linaro.org \
--to=rui.silva@linaro.org \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=ryan.harkin@linaro.org \
--cc=sakari.ailus@linux.intel.com \
/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).