From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Manjunath Hadli <manjunath.hadli@ti.com>
Cc: LMML <linux-media@vger.kernel.org>,
dlos <davinci-linux-open-source@linux.davincidsp.com>
Subject: Re: [PATCH v17 5/6] davinci vpbe: Build infrastructure for VPBE driver
Date: Fri, 20 May 2011 18:32:08 +0400 [thread overview]
Message-ID: <4DD67B68.7070704@mvista.com> (raw)
In-Reply-To: <1305899324-2118-1-git-send-email-manjunath.hadli@ti.com>
Hello.
Manjunath Hadli wrote:
> This patch adds the build infra-structure for Davinci
> VPBE dislay driver.
> Signed-off-by: Manjunath Hadli <manjunath.hadli@ti.com>
> Acked-by: Muralidharan Karicheri <m-karicheri2@ti.com>
> Acked-by: Hans Verkuil <hverkuil@xs4all.nl>
[...]
> diff --git a/drivers/media/video/davinci/Kconfig b/drivers/media/video/davinci/Kconfig
> index 6b19540..a7f11e7 100644
> --- a/drivers/media/video/davinci/Kconfig
> +++ b/drivers/media/video/davinci/Kconfig
> @@ -91,3 +91,25 @@ config VIDEO_ISIF
>
> To compile this driver as a module, choose M here: the
> module will be called vpfe.
> +
> +config VIDEO_DM644X_VPBE
> + tristate "DM644X VPBE HW module"
BTW, as this seems DM644x specific, shouldn't this depend on
CONFIG_ARCH_DAVINCI_DM644x?
> + select VIDEO_VPSS_SYSTEM
> + select VIDEOBUF_DMA_CONTIG
> + help
> + Enables VPBE modules used for display on a DM644x
> + SoC.
> +
> + To compile this driver as a module, choose M here: the
> + module will be called vpbe.
> +
> +
> +config VIDEO_VPBE_DISPLAY
> + tristate "VPBE V4L2 Display driver"
> + select VIDEO_DM644X_VPBE
Or this one, if it selects VIDEO_DM644X_VPBE?
> + default y
Hm, "y" shouldn't be the default.
WBR, Sergei
next prev parent reply other threads:[~2011-05-20 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 13:48 [PATCH v17 5/6] davinci vpbe: Build infrastructure for VPBE driver Manjunath Hadli
2011-05-20 14:32 ` Sergei Shtylyov [this message]
2011-05-23 8:28 ` Nori, Sekhar
2011-05-24 12:59 ` Hadli, Manjunath
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=4DD67B68.7070704@mvista.com \
--to=sshtylyov@mvista.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-media@vger.kernel.org \
--cc=manjunath.hadli@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.