From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Cc: Ulrich Hecht <ulrich.hecht@gmail.com>,
mchehab@osg.samsung.com, linux-media@vger.kernel.org,
hans.verkuil@cisco.com, linux-renesas-soc@vger.kernel.org
Subject: Re: [RFC/PATCH] [media] rcar-vin: add Renesas R-Car VIN IP core
Date: Mon, 22 Feb 2016 17:17:19 +0200 [thread overview]
Message-ID: <4002725.0WTZZGiC9K@avalon> (raw)
In-Reply-To: <20160222143616.GD3442@bigcity.dyn.berto.se>
Hi Niklas,
On Monday 22 February 2016 15:36:16 Niklas Söderlund wrote:
> On 2016-02-22 14:31:29 +0100, Ulrich Hecht wrote:
> > On Sun, Feb 14, 2016 at 5:55 PM, Niklas Söderlund
> >
> > <niklas.soderlund+renesas@ragnatech.se> wrote:
> > > Also I
> > > could only get frames if the video signal on the composite IN was NTSC,
> > > but this also applied to the soc_camera driver, it might be my test
> > > setup.
> >
> > I think it is. For me, PAL works just as well as NTSC.
>
> Yes it must have been my setup, I'm now using a PAL SNES as my video
> source and it works fine. I'm about ready to send out a v2 of this patch
> with all of Hans comments fixed. I only need to look at
> vidioc_[gs]_selection.
I think we need an SNES screenshot as a proof ;-)
> It took some extra time since I found some bugs in how I handled DMA and
> that I had been to libera in porting the format code from soc-camera.
> It's all fixed and all v4l2-compliance tests I tried works.
>
> One concern I have is that I can't get some of the formats to display
> properly in qv4l2 (V4L2_PIX_FMT_NV16, V4L2_PIX_FMT_RGB555X,
> V4L2_PIX_FMT_RGB32) but I get the same 'errors' in the feed as I do with
> the soc-camera driver so I'm not spending so much time on the issue right
> now.
What errors do you get ?
> Unfortunate the rework I have done clashes with your HDMI series Ulrich.
> If you wish I can rework the parts of your series that touches rcar-vin
> and post them as a separate series after v2? Let me know what you think.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2016-02-22 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 16:55 [RFC/PATCH] [media] rcar-vin: add Renesas R-Car VIN IP core Niklas Söderlund
2016-02-15 9:28 ` Hans Verkuil
2016-02-15 10:48 ` Hans Verkuil
2016-02-18 0:13 ` Niklas Söderlund
2016-02-18 6:36 ` Hans Verkuil
2016-02-15 11:40 ` Ulrich Hecht
2016-02-18 1:51 ` Niklas Söderlund
2016-02-22 13:31 ` Ulrich Hecht
2016-02-22 14:36 ` Niklas Söderlund
2016-02-22 15:17 ` Laurent Pinchart [this message]
2016-02-23 10:45 ` Ulrich Hecht
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=4002725.0WTZZGiC9K@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=hans.verkuil@cisco.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=niklas.soderlund@ragnatech.se \
--cc=ulrich.hecht@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