From: Paul Mundt <lethal@linux-sh.org>
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: Tue, 23 Mar 2010 08:47:08 +0000 [thread overview]
Message-ID: <20100323084707.GD30655@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1003171103030.4354@axis700.grange>
On Thu, Mar 18, 2010 at 11:28:28AM +0100, Guennadi Liakhovetski wrote:
> diff --git a/drivers/media/video/Kconfig b/drivers/media/video/Kconfig
> index 64682bf..be6d016 100644
> --- a/drivers/media/video/Kconfig
> +++ b/drivers/media/video/Kconfig
> @@ -511,6 +511,13 @@ config DISPLAY_DAVINCI_DM646X_EVM
> To compile this driver as a module, choose M here: the
> module will be called vpif_display.
>
> +config VIDEO_SH_VOU
> + tristate "SuperH VOU video output driver"
> + depends on VIDEO_DEV && (SUPERH || ARCH_SHMOBILE)
> + select VIDEOBUF_DMA_CONTIG
> + help
> + Support for the Video Output Unit (VOU) on SuperH SoCs.
> +
I assumed the VOU was only on SH-Mobile, in which case you can just
depend on ARCH_SHMOBILE directly, since we set that for all SH-Mobile
CPUs anyways.
After that's done or proven to be an inaccurate assumption:
Acked-by: Paul Mundt <lethal@linux-sh.org>
prev parent reply other threads:[~2010-03-23 8:47 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 ` [PATCH 1/3 v2] V4L: SuperH Video Output Unit (VOU) driver Magnus Damm
2010-03-23 8:47 ` Paul Mundt [this message]
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=20100323084707.GD30655@linux-sh.org \
--to=lethal@linux-sh.org \
--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).