devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rui Miguel Silva <rui.silva@linaro.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
	sakari.ailus@linux.intel.com,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ryan Harkin <ryan.harkin@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Rui Miguel Silva <rui.silva@linaro.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Steve Longerbeam <slongerbeam@gmail.com>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	mchehab@kernel.org, Shawn Guo <shawnguo@kernel.org>,
	linux-clk@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v6 00/13] media: staging/imx7: add i.MX7 media driver
Date: Thu, 02 Aug 2018 17:45:20 +0100	[thread overview]
Message-ID: <m3a7q4u38f.fsf@linaro.org> (raw)
In-Reply-To: <267173c9-7235-6008-7248-ee06c0db3780@xs4all.nl>

Hi Hans,
On Thu 02 Aug 2018 at 13:37, Hans Verkuil wrote:
> Hi Rui,
>
> On 05/22/18 16:52, Rui Miguel Silva wrote:
>> Hi,
>> This series introduces the Media driver to work with the i.MX7 
>> SoC. it uses the
>> already existing imx media core drivers but since the i.MX7, 
>> contrary to
>> i.MX5/6, do not have an IPU and because of that some changes in 
>> the imx media
>> core are made along this series to make it support that case.
>> 
>> This patches adds CSI and MIPI-CSI2 drivers for i.MX7, along 
>> with several
>> configurations changes for this to work as a capture subsystem. 
>> Some bugs are
>> also fixed along the line. And necessary documentation.
>> 
>> For a more detailed view of the capture paths, pads links in 
>> the i.MX7 please
>> take a look at the documentation in PATCH 14.
>> 
>> The system used to test and develop this was the Warp7 board 
>> with an OV2680
>> sensor, which output format is 10-bit bayer. So, only MIPI 
>> interface was
>> tested, a scenario with an parallel input would nice to have.
>> 
>> *Important note*, this code depends on Steve Longerbeam series 
>> [0]:
>> [PATCH v4 00/13] media: imx: Switch to subdev notifiers
>> which the merging status is not clear to me, but the changes in 
>> there make
>> senses to this series
>> 
>> Bellow goes an example of the output of the pads and links and 
>> the output of
>> v4l2-compliance testing.
>> 
>> The v4l-utils version used is:
>> v4l2-compliance SHA   : 
>> 47d43b130dc6e9e0edc900759fb37649208371e4 from Apr 4th.
>> 
>> The Media Driver fail some tests but this failures are coming 
>> from code out of
>> scope of this series (video-mux, imx-capture), and some from 
>> the sensor OV2680
>> but that I think not related with the sensor driver but with 
>> the testing and
>> core.
>> 
>> The csi and mipi-csi entities pass all compliance tests.
>> 
>> Cheers,
>>     Rui
>> 
>> [0]: 
>> https://www.mail-archive.com/linux-media@vger.kernel.org/msg131186.html
>
> This patch series was delayed quite a bit since the patch series 
> above
> it depends on is still not merged.
>
> But the v6 version of that series will be merged once the 4.20 
> cycle opens:
> https://www.mail-archive.com/linux-media@vger.kernel.org/msg133391.html

Good news.

>
> Sakari has a branch with that series on top of the latest 
> media_tree master:
> https://git.linuxtv.org/sailus/media_tree.git/log/?h=v4l2-fwnode
>
> Can you rebase this imx7 series on top of that? And test it 
> again with the
> *latest* v4l2-compliance? (I've added new checks recently, so 
> you need to
> update this utility)
>
> Please post the output of the v4l2-compliance test (after fixing 
> any issues
> it raises of course), either as a reply to this post or in the 
> cover letter
> of a v7 version of this series if you had to make changes.

Sure, I will rebase on top of Sakari tree and will update the 
compliance
tests and run them again.

>
> This should expedite merging this series for 4.20.
>
> Thanks!
>
> 	Hans

Ok, thanks for this. I will try to do it soon.

---
Cheers,
	Rui

  reply	other threads:[~2018-08-02 16:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22 14:52 [PATCH v6 00/13] media: staging/imx7: add i.MX7 media driver Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 01/13] media: staging/imx: refactor imx media device probe Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 02/13] media: staging/imx: rearrange group id to take in account IPU Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 03/13] media: staging/imx7: add imx7 CSI subdev driver Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 04/13] clk: imx7d: fix mipi dphy div parent Rui Miguel Silva
2018-06-01 19:41   ` Stephen Boyd
2018-05-22 14:52 ` [PATCH v6 05/13] clk: imx7d: reset parent for mipi csi root Rui Miguel Silva
2018-06-01 19:41   ` Stephen Boyd
2018-05-22 14:52 ` [PATCH v6 06/13] media: staging/imx7: add MIPI CSI-2 receiver subdev for i.MX7 Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 07/13] media: dt-bindings: add bindings for i.MX7 media driver Rui Miguel Silva
2018-05-22 16:10   ` Rob Herring
2018-08-02 13:00   ` Sakari Ailus
2018-08-02 16:48     ` Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 08/13] ARM: dts: imx7s: add mipi phy power domain Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 09/13] ARM: dts: imx7s: add multiplexer controls Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 10/13] ARM: dts: imx7: Add video mux, csi and mipi_csi and connections Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 11/13] ARM: dts: imx7s-warp: add ov2680 sensor node Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 12/13] media: imx7.rst: add documentation for i.MX7 media driver Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 13/13] media: staging/imx: add i.MX7 entries to TODO file Rui Miguel Silva
2018-08-02 12:37 ` [PATCH v6 00/13] media: staging/imx7: add i.MX7 media driver Hans Verkuil
2018-08-02 16:45   ` Rui Miguel Silva [this message]
2018-08-03 11:00     ` Hans Verkuil

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=m3a7q4u38f.fsf@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=hverkuil@xs4all.nl \
    --cc=linux-clk@vger.kernel.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 \
    --cc=shawnguo@kernel.org \
    --cc=slongerbeam@gmail.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).