RE: [PATCH 0/2] V4L/DVB: OMAP_VOUT: Allow omap_vout to build without VRFB

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: Taneja, Archit
> Sent: Monday, September 06, 2010 9:31 AM
> To: Hiremath, Vaibhav
> Cc: linux-omap@xxxxxxxxxxxxxxx; linux-media@xxxxxxxxxxxxxxx
> Subject: RE: [PATCH 0/2] V4L/DVB: OMAP_VOUT: Allow omap_vout to build
> without VRFB
> 
> Hi,
> 
> Hiremath, Vaibhav wrote:
> >> -----Original Message-----
> >> From: Taneja, Archit
> >> Sent: Saturday, September 04, 2010 2:12 PM
> >> To: Hiremath, Vaibhav
> >> Cc: linux-omap@xxxxxxxxxxxxxxx;
> > linux-media@xxxxxxxxxxxxxxx; Taneja,
> >> Archit
> >> Subject: [PATCH 0/2] V4L/DVB: OMAP_VOUT: Allow omap_vout to build
> without
> >> VRFB
> >>
> >> This lets omap_vout driver build and run without VRFB. It works along
> >> the lines of the following patch series:
> >> OMAP: DSS2: OMAPFB: Allow FB_OMAP2 to build without VRFB
> >> https://patchwork.kernel.org/patch/105371/
> >>
> >> A variable rotation_type is introduced in omapvideo_info like the way
> >> in omapfb_info to make both vrfb and non vrfb rotation possible.
> >>
> > [Hiremath, Vaibhav] Archit,
> >
> > Currently omap_vout driver only supports VRFB based rotation,
> > it doesn't support SDMA based rotation (unlike OMAPFB) and neither you
> patch
> > adds it.
> 
> [Archit]The above description in the git commit is a mistake from my end.
> The main purpose
> of the patch is to get omap_vout running without VRFB.
> 
> I am not sure if we need to enable SDMA rotation for V4L2 though, we would
> always have
> vrfb and tiler on omap3 and omap4 respectively.
[Hiremath, Vaibhav] No, for me SDMA based rotation doesn't make sense, since SDMA rotation suffers from bandwidth issue. On OMAPFB it has been observed that, DSS throws FIFO underflow error very frequently in SDMA based rotation.


> 
> How do you think things should be handled in the non vrfb case? Should we
> try to get
> rotation running or should the driver return an error if userspace tries
> to enable
> rotation in a non-vrfb mode?
[Hiremath, Vaibhav] We can handle this in 2 ways,

- Driver can return -ERANGE error, in case of OMAP4 (or non-vrfb platform)

- Driver can choose/fall-down 0 degree rotation gracefully

As per V4L2 spec both options are acceptable.

Thanks,
Vaibhav

> 
> Thanks,
> 
> Archit
> 
> >> Since VRFB is tightly coupled with the omap_vout driver, a handful of
> >> vrfb-specific functions have been defined and placed in
> omap_vout_vrfb.c
> >>
> >> This series applies along with the previously submitted patch:
> >> https://patchwork.kernel.org/patch/146401/
> >>
> >> Archit Taneja (2):
> >>   V4L/DVB: OMAP_VOUT: Create a seperate vrfb functions library
> >>   V4L/DVB: OMAP_VOUT: Use rotation_type to choose between vrfb and
> sdram
> >> rotation
> >>
> >>  drivers/media/video/omap/Kconfig          |    1 -
> >>  drivers/media/video/omap/Makefile         |    1 +
> >>  drivers/media/video/omap/omap_vout.c      |  502 ++++++---------------
> ---
> >>  ----- drivers/media/video/omap/omap_vout_vrfb.c |  417
> >>  ++++++++++++++++++++++++ drivers/media/video/omap/omap_vout_vrfb.h |
> 40
> >>  +++ drivers/media/video/omap/omap_voutdef.h   |   26 ++
> >>  6 files changed, 582 insertions(+), 405 deletions(-)  create mode
> >> 100644 drivers/media/video/omap/omap_vout_vrfb.c
> >>  create mode 100644 drivers/media/video/omap/omap_vout_vrfb.h
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux