diff mbox

[2/2] ARM: imx_v6_v7_defconfig: Add VPU support

Message ID 1359474553-8949-2-git-send-email-fabio.estevam@freescale.com (mailing list archive)
State New, archived
Headers show

Commit Message

Fabio Estevam Jan. 29, 2013, 3:49 p.m. UTC
Let the VPU driver be built by default.

Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
---
 arch/arm/configs/imx_v6_v7_defconfig |    2 ++
 1 file changed, 2 insertions(+)

Comments

Shawn Guo Jan. 30, 2013, 1:04 p.m. UTC | #1
On Tue, Jan 29, 2013 at 01:49:13PM -0200, Fabio Estevam wrote:
> Let the VPU driver be built by default.
> 
Do we have any imx_v6_v7 platform supported by VPU driver today?

Shawn

> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
>  arch/arm/configs/imx_v6_v7_defconfig |    2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/arm/configs/imx_v6_v7_defconfig b/arch/arm/configs/imx_v6_v7_defconfig
> index 6966713..83822d9 100644
> --- a/arch/arm/configs/imx_v6_v7_defconfig
> +++ b/arch/arm/configs/imx_v6_v7_defconfig
> @@ -160,6 +160,8 @@ CONFIG_MEDIA_CAMERA_SUPPORT=y
>  CONFIG_SOC_CAMERA=y
>  CONFIG_SOC_CAMERA_OV2640=y
>  CONFIG_VIDEO_MX3=y
> +CONFIG_V4L_MEM2MEM_DRIVERS=y
> +CONFIG_VIDEO_CODA=y
>  CONFIG_FB=y
>  CONFIG_LCD_PLATFORM=y
>  CONFIG_BACKLIGHT_LCD_SUPPORT=y
> -- 
> 1.7.9.5
> 
>
Sascha Hauer Jan. 31, 2013, 9:54 a.m. UTC | #2
On Wed, Jan 30, 2013 at 09:04:55PM +0800, Shawn Guo wrote:
> On Tue, Jan 29, 2013 at 01:49:13PM -0200, Fabio Estevam wrote:
> > Let the VPU driver be built by default.
> > 
> Do we have any imx_v6_v7 platform supported by VPU driver today?

Does this matter? IMO it's good to keep the driver in a compilable state
even if it ends up being unused for now.

Sascha
Shawn Guo Jan. 31, 2013, 12:28 p.m. UTC | #3
On Thu, Jan 31, 2013 at 10:54:46AM +0100, Sascha Hauer wrote:
> On Wed, Jan 30, 2013 at 09:04:55PM +0800, Shawn Guo wrote:
> > On Tue, Jan 29, 2013 at 01:49:13PM -0200, Fabio Estevam wrote:
> > > Let the VPU driver be built by default.
> > > 
> > Do we have any imx_v6_v7 platform supported by VPU driver today?
> 
> Does this matter? IMO it's good to keep the driver in a compilable state
> even if it ends up being unused for now.
> 
It's not really necessary since we will have imx_v4_v5_defconfig to
cover it.

Shawn
Fabio Estevam Feb. 7, 2013, 11:40 a.m. UTC | #4
On Thu, Jan 31, 2013 at 10:28 AM, Shawn Guo <shawn.guo@linaro.org> wrote:
> On Thu, Jan 31, 2013 at 10:54:46AM +0100, Sascha Hauer wrote:
>> On Wed, Jan 30, 2013 at 09:04:55PM +0800, Shawn Guo wrote:
>> > On Tue, Jan 29, 2013 at 01:49:13PM -0200, Fabio Estevam wrote:
>> > > Let the VPU driver be built by default.
>> > >
>> > Do we have any imx_v6_v7 platform supported by VPU driver today?
>>
>> Does this matter? IMO it's good to keep the driver in a compilable state
>> even if it ends up being unused for now.
>>
> It's not really necessary since we will have imx_v4_v5_defconfig to
> cover it.

Ok, but was the imx_v4_v5_defconfig applied?
Shawn Guo Feb. 7, 2013, 12:59 p.m. UTC | #5
On Thu, Feb 07, 2013 at 09:40:50AM -0200, Fabio Estevam wrote:
> On Thu, Jan 31, 2013 at 10:28 AM, Shawn Guo <shawn.guo@linaro.org> wrote:
> > On Thu, Jan 31, 2013 at 10:54:46AM +0100, Sascha Hauer wrote:
> >> On Wed, Jan 30, 2013 at 09:04:55PM +0800, Shawn Guo wrote:
> >> > On Tue, Jan 29, 2013 at 01:49:13PM -0200, Fabio Estevam wrote:
> >> > > Let the VPU driver be built by default.
> >> > >
> >> > Do we have any imx_v6_v7 platform supported by VPU driver today?
> >>
> >> Does this matter? IMO it's good to keep the driver in a compilable state
> >> even if it ends up being unused for now.
> >>
> > It's not really necessary since we will have imx_v4_v5_defconfig to
> > cover it.
> 
> Ok, but was the imx_v4_v5_defconfig applied?

I already sent my 3.9 material, and assumed that Sascha will pick it
up.

Shawn
Fabio Estevam Feb. 11, 2013, 1:38 p.m. UTC | #6
Sascha,

On Thu, Feb 7, 2013 at 10:59 AM, Shawn Guo <shawn.guo@linaro.org> wrote:

>> Ok, but was the imx_v4_v5_defconfig applied?
>
> I already sent my 3.9 material, and assumed that Sascha will pick it
> up.

Do you plan to pick the imx_v4_v5_defconfig patch, so that we can have
build coverage for the VPU driver?
Sascha Hauer Feb. 12, 2013, 8:10 a.m. UTC | #7
On Mon, Feb 11, 2013 at 11:38:21AM -0200, Fabio Estevam wrote:
> Sascha,
> 
> On Thu, Feb 7, 2013 at 10:59 AM, Shawn Guo <shawn.guo@linaro.org> wrote:
> 
> >> Ok, but was the imx_v4_v5_defconfig applied?
> >
> > I already sent my 3.9 material, and assumed that Sascha will pick it
> > up.
> 
> Do you plan to pick the imx_v4_v5_defconfig patch, so that we can have
> build coverage for the VPU driver?

Just did that.

Thanks
 Sascha
diff mbox

Patch

diff --git a/arch/arm/configs/imx_v6_v7_defconfig b/arch/arm/configs/imx_v6_v7_defconfig
index 6966713..83822d9 100644
--- a/arch/arm/configs/imx_v6_v7_defconfig
+++ b/arch/arm/configs/imx_v6_v7_defconfig
@@ -160,6 +160,8 @@  CONFIG_MEDIA_CAMERA_SUPPORT=y
 CONFIG_SOC_CAMERA=y
 CONFIG_SOC_CAMERA_OV2640=y
 CONFIG_VIDEO_MX3=y
+CONFIG_V4L_MEM2MEM_DRIVERS=y
+CONFIG_VIDEO_CODA=y
 CONFIG_FB=y
 CONFIG_LCD_PLATFORM=y
 CONFIG_BACKLIGHT_LCD_SUPPORT=y