author | Benoit Parrot <bparrot@ti.com> | |
Fri, 29 May 2015 18:08:42 +0000 (13:08 -0500) | ||
committer | Nikhil Devshatwar <nikhil.nd@ti.com> | |
Thu, 25 Jun 2015 10:51:24 +0000 (16:21 +0530) | ||
commit | 83924b1e8b01fb84b7e93dc9ea5144b1a93e0402 | |
tree | 5e1230ff5bb5d712d98a59d522d817f090715755 | tree | snapshot (tar.xz tar.gz zip) |
parent | 738785d558fbea3fa59d1e64b6bb4212fb97656b | commit | diff |
media: ti-vpe: VIP/VPE/VPDMA: Correction of data type label.
The YUV data type definition below are taken from
both the TRM and i839 Errata information.
Use the correct data type considering byte
reordering of components.
Also since the single use of "C" in the 422 case
to mean "Cr" (i.e. V component). It was decided
to explictly label them CR to remove any confusion.
Bear in mind that the type label refer to the memory
packed order (LSB - MSB).
Change-Id: I2f37b5514f9546b41f09c6bd198534b3482945d0
Signed-off-by: Benoit Parrot <bparrot@ti.com>
Signed-off-by: Jyri Sarha <jsarha@ti.com>
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
The YUV data type definition below are taken from
both the TRM and i839 Errata information.
Use the correct data type considering byte
reordering of components.
Also since the single use of "C" in the 422 case
to mean "Cr" (i.e. V component). It was decided
to explictly label them CR to remove any confusion.
Bear in mind that the type label refer to the memory
packed order (LSB - MSB).
Change-Id: I2f37b5514f9546b41f09c6bd198534b3482945d0
Signed-off-by: Benoit Parrot <bparrot@ti.com>
Signed-off-by: Jyri Sarha <jsarha@ti.com>
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>