media: mx2_camera: Add YUYV output format.

  While YUYV format can be handled using generic pass-through mode,
in order to allow resizing the eMMa-PrP has to know exactly
what format it is dealing with to process data accordingly.

Signed-off-by: Javier Martin <javier.martin@vista-silicon.com>
---
 drivers/media/video/mx2_camera.c |   26 ++++++++++++++++++++++++++
 1 files changed, 26 insertions(+), 0 deletions(-)
  

Hi,

On 5 June 2012 16:09, Fabio Estevam <festevam@gmail.com> wrote:
> Hi Javier,
>
> Just curious: have you managed to get VPU driver working in mainline
> running on mx27?

No, I'm still working on it in my spare time. Progress is rather slow.

Regards.
  

On Tue, Jun 5, 2012 at 11:14 AM, javier Martin
<javier.martin@vista-silicon.com> wrote:

> No, I'm still working on it in my spare time. Progress is rather slow.

Ok, great. If you want to collaborate on this task, I will be glad to help.

Let me know if you have a git tree with your work in progress.

Saludos,

Fabio Estevam
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
  

Hi Fabio,

On 5 June 2012 16:17, Fabio Estevam <festevam@gmail.com> wrote:
> On Tue, Jun 5, 2012 at 11:14 AM, javier Martin
> <javier.martin@vista-silicon.com> wrote:
>
>> No, I'm still working on it in my spare time. Progress is rather slow.
>
> Ok, great. If you want to collaborate on this task, I will be glad to help.
>
> Let me know if you have a git tree with your work in progress.

As i stated, the driver is still in an early development stage, it
doesn't do anything useful yet. But this is the public git repository
if you want to take a look:

git repo: https://github.com/jmartinc/video_visstrim.git
branch:  mx27-codadx6

FYI we are only interested on adding support for the encoding path of
the VPU, but we are trying our best to make it modular (as it is done
in Samsung's [1]), so that anyone can add decoding support later.

By the way, you work for Freescale, don't you?

We have a couple of issues with the i.MX27 VPU:

1- Firmware for the VPU is provided as a table of binary values inside
a source file which is licensed as GPL, however software is packaged
in a .tar.gz file that is marked as NDA. Do we have the right to
distribute this firmware with our products?
2- There is a BUG in the firmware that marks P frames as IDR when it
should only be done to I frames. Would it be possible to have access
to the source code of the firmware in order to fix that problem?

Regards.

[1] http://lxr.linux.no/#linux+v3.4.1/drivers/media/video/s5p-mfc/
  

Hi Javier,

On Thu, Jun 7, 2012 at 5:30 AM, javier Martin
<javier.martin@vista-silicon.com> wrote:

> As i stated, the driver is still in an early development stage, it
> doesn't do anything useful yet. But this is the public git repository
> if you want to take a look:
>
> git repo: https://github.com/jmartinc/video_visstrim.git
> branch:  mx27-codadx6

Thanks, I will take a look at your tree when I am back to the office next week.

I also see that Linaro's tree has support for VPU for mx5/mx6:
http://git.linaro.org/gitweb?p=landing-teams/working/freescale/kernel.git;a=summary

,so we should probably think in unifying it with mx27 support there too.

>
> FYI we are only interested on adding support for the encoding path of
> the VPU, but we are trying our best to make it modular (as it is done
> in Samsung's [1]), so that anyone can add decoding support later.

Ok, sounds good.

> By the way, you work for Freescale, don't you?

Yes, correct.

> We have a couple of issues with the i.MX27 VPU:
>
> 1- Firmware for the VPU is provided as a table of binary values inside
> a source file which is licensed as GPL, however software is packaged
> in a .tar.gz file that is marked as NDA. Do we have the right to
> distribute this firmware with our products?
> 2- There is a BUG in the firmware that marks P frames as IDR when it
> should only be done to I frames. Would it be possible to have access
> to the source code of the firmware in order to fix that problem?

I will need to check this next week when I am back to the office.

Thanks,

Fabio Estevam
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
  

Hi Fabio,

On 7 June 2012 19:35, Fabio Estevam <festevam@gmail.com> wrote:
> Hi Javier,
>
> On Thu, Jun 7, 2012 at 5:30 AM, javier Martin
> <javier.martin@vista-silicon.com> wrote:
>
>> As i stated, the driver is still in an early development stage, it
>> doesn't do anything useful yet. But this is the public git repository
>> if you want to take a look:
>>
>> git repo: https://github.com/jmartinc/video_visstrim.git
>> branch:  mx27-codadx6
>
> Thanks, I will take a look at your tree when I am back to the office next week.
>
> I also see that Linaro's tree has support for VPU for mx5/mx6:
> http://git.linaro.org/gitweb?p=landing-teams/working/freescale/kernel.git;a=summary
>
> ,so we should probably think in unifying it with mx27 support there too.
>
>>
>> FYI we are only interested on adding support for the encoding path of
>> the VPU, but we are trying our best to make it modular (as it is done
>> in Samsung's [1]), so that anyone can add decoding support later.
>
> Ok, sounds good.
>
>> By the way, you work for Freescale, don't you?
>
> Yes, correct.
>
>> We have a couple of issues with the i.MX27 VPU:
>>
>> 1- Firmware for the VPU is provided as a table of binary values inside
>> a source file which is licensed as GPL, however software is packaged
>> in a .tar.gz file that is marked as NDA. Do we have the right to
>> distribute this firmware with our products?

To address this issue it would be great if you, as a Freescale
employee, could send VPU firmware binary file to linux-firmware with a
LICENSE.xxxx file as well:

http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree

>> 2- There is a BUG in the firmware that marks P frames as IDR when it
>> should only be done to I frames. Would it be possible to have access
>> to the source code of the firmware in order to fix that problem?
>
> I will need to check this next week when I am back to the office.


Regards.