From: Robert Jarzmik <robert.jarzmik@free.fr>
To: video4linux-list@redhat.com
Subject: [RFC] soc_camera: endianness between camera and its host
Date: Sat, 02 Aug 2008 12:58:47 +0200 [thread overview]
Message-ID: <87hca34ra0.fsf@free.fr> (raw)
Modern camera chips provide ways to invert their data output, as well in colors
swap as in byte order. To be more precise, the one I know (mt9m111) enables :
- swapping Red and Blue in RGB formats
- swapping first and second byte in RGB formats
- swapping Cb and Cr in YUV formats
- swapping chrominance and luminance in YUV formats
This swap is necessary to adapt the camera chip output to the capture
interface. For example, pxa_camera on pxa27x CPUs expects RGB and YUV formats
in a very specific order. This order is not the default one on mt9m111 chip, so
the mt9m111 driver has to have a way to know how to order its output.
The question I have is where to put such information, so that board specific
code (arch/arm/mach-pxa/xxx.c) can setup this for a dedicated camera chip ?
One easy way would be to put it in soc_camera_link, but is it the right place ?
--
Robert
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next reply other threads:[~2008-08-02 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 10:58 Robert Jarzmik [this message]
2008-08-02 20:09 ` [RFC] soc_camera: endianness between camera and its host Guennadi Liakhovetski
2008-08-02 23:38 ` Robert Jarzmik
2008-08-12 14:59 ` Guennadi Liakhovetski
2008-08-13 8:37 ` robert.jarzmik
2008-08-13 9:10 ` Guennadi Liakhovetski
2008-08-13 10:03 ` robert.jarzmik
2008-08-13 11:35 ` [PATCH] mt9m111: style cleanup Guennadi Liakhovetski
2008-08-13 16:38 ` Robert Jarzmik
2008-08-13 16:47 ` Guennadi Liakhovetski
2008-08-13 16:54 ` Robert Jarzmik
2008-08-13 17:12 ` Guennadi Liakhovetski
2008-08-13 17:20 ` Robert Jarzmik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hca34ra0.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=video4linux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox