diff options
author | Liu Ying <Ying.Liu@freescale.com> | 2014-04-21 14:12:49 +0800 |
---|---|---|
committer | Liu Ying <Ying.Liu@freescale.com> | 2014-04-24 15:02:26 +0800 |
commit | 5c17876222eac2c7c79030d74d813fee97a6bc76 (patch) | |
tree | 4fee4d22c3bfdda1ba268dcb7c37ef42992767f0 /drivers/bus/Kconfig | |
parent | 5f1f2d8a3db3ea7215b717a08cb80385be97f7d3 (diff) |
ENGR00301281 media: mxc vout: set input resolution back after PP check/process
In VDOA PP mode, the input resolution would be changed to be VDOA's output
for PP to use as its input resolution to go on to do resizing or color space
conversion. The input resolution will be different from the original one
when VDOA input cropping is enabled. And, this finally causes a wrong input
resolution being used if the users do rotation by calling the S_CTRL ioctrl
in runtime. In order to fix this issue, this patch sets the original input
resolution back after PP task check and process. The issue can be reproduced
by the following command line(enable VDOA mode in the gst plugin configuration
file first):
gplay AVC_MP30_854x356_23.976_679_AACLC_44.1_96_2_TRON_LEGACY.flv
(Enter 't 90' to change to rotate 90 degrees in runtime.)
In this case, VDOA input cropping(854x356 -> 848x352) is enabled because VDOA
input resolution should align to macro block size.
Signed-off-by: Liu Ying <Ying.Liu@freescale.com>
(cherry picked from commit 4c732ad69265d8e441e6c15a2e87f5aeef234624)
Diffstat (limited to 'drivers/bus/Kconfig')
0 files changed, 0 insertions, 0 deletions