linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Magnus Damm <damm@opensource.se>,
	"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>
Subject: Re: [PATCH 1/3 v2] V4L: SuperH Video Output Unit (VOU) driver
Date: Thu, 18 Mar 2010 11:25:06 +0000	[thread overview]
Message-ID: <aec7e5c31003180425l5066edffl4eda8804278b42d8@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1003171103030.4354@axis700.grange>

Hey Guennadi,

On Thu, Mar 18, 2010 at 7:28 PM, Guennadi Liakhovetski
<g.liakhovetski@gmx.de> wrote:
> A number of SuperH SoCs, including sh7724, include a Video Output Unit. This
> patch adds a video (V4L2) output driver for it. The driver uses v4l2-subdev and
> mediabus APIs to interface to TV encoders.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> ---

Thanks for your work on this. The VOU block is actually used by the
SH-Mobile series of SoCs. So you may want to throw in a "mobile" there
in you description to avoid future name space collisions.

I'll make sure that people test your V2 patch.

Is both NTSC and PAL known to be ok with v2?

Thanks,

/ magnus

  parent reply	other threads:[~2010-03-18 11:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 10:28 [PATCH 1/3 v2] V4L: SuperH Video Output Unit (VOU) driver Guennadi Liakhovetski
2010-03-18 10:28 ` [PATCH 2/3 v2] V4L: v4l2-subdev driver for AK8813 and AK8814 Guennadi Liakhovetski
2010-03-18 10:28   ` [PATCH 3/3 v2] sh: add Video Output Unit (VOU) and AK8813 TV-encoder Guennadi Liakhovetski
2010-03-26 11:58   ` [PATCH 2/3 v2] V4L: v4l2-subdev driver for AK8813 and AK8814 TV-encoders from AKM Hans Verkuil
2010-03-18 11:25 ` Magnus Damm [this message]
2010-03-23  8:47 ` [PATCH 1/3 v2] V4L: SuperH Video Output Unit (VOU) driver Paul Mundt

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=aec7e5c31003180425l5066edffl4eda8804278b42d8@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --cc=damm@opensource.se \
    --cc=g.liakhovetski@gmx.de \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-sh@vger.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).