From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Add RGB555X and RGB565X formats to pxa-camera
Date: Sat, 5 Sep 2009 23:17:23 +0200 [thread overview]
Message-ID: <200909052317.24048.marek.vasut@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0909052219030.4670@axis700.grange>
Dne So 5. z??? 2009 22:19:42 Guennadi Liakhovetski napsal(a):
> On Sat, 5 Sep 2009, Marek Vasut wrote:
> > Dne So 5. z??? 2009 10:55:55 Guennadi Liakhovetski napsal(a):
> > > On Sat, 5 Sep 2009, Marek Vasut wrote:
> > > > > > > drivers/media/video/pxa_camera.c | 4 ++++
> > > > > > > 1 files changed, 4 insertions(+), 0 deletions(-)
> > > > > > >
> > > > > > > diff --git a/drivers/media/video/pxa_camera.c
> > > > > > > b/drivers/media/video/pxa_camera.c
> > > > > > > index 46e0d8a..de0fc8a 100644
> > > > > > > --- a/drivers/media/video/pxa_camera.c
> > > > > > > +++ b/drivers/media/video/pxa_camera.c
> > > > > > > @@ -1222,6 +1222,8 @@ static int required_buswidth(const struct
> > > > > > > soc_camera_data_format *fmt)
> > > > > > > case V4L2_PIX_FMT_YVYU:
> > > > > > > case V4L2_PIX_FMT_RGB565:
> > > > > > > case V4L2_PIX_FMT_RGB555:
> > > > > > > + case V4L2_PIX_FMT_RGB565X:
> > > > > > > + case V4L2_PIX_FMT_RGB555X:
> > > > > > > return 8;
> > > > > > > default:
> > > > > > > return fmt->depth;
> > > > > > > @@ -1260,6 +1262,8 @@ static int pxa_camera_get_formats(struct
> > > > > > > soc_camera_device *icd, int idx,
> > > > > > > case V4L2_PIX_FMT_YVYU:
> > > > > > > case V4L2_PIX_FMT_RGB565:
> > > > > > > case V4L2_PIX_FMT_RGB555:
> > > > > > > + case V4L2_PIX_FMT_RGB565X:
> > > > > > > + case V4L2_PIX_FMT_RGB555X:
> > > > > > > formats++;
> > > > > > > if (xlate) {
> > > > > > > xlate->host_fmt = icd->formats + idx;
> > > >
> > > > What should we do with this patch? Any updates? I spoke to Guennadi
> > > > and he thinks it's not a good idea to apply it (as pxaqci doesnt
> > > > support those formats). But to my understanding, those formats are
> > > > endian-swapped versions of the other ones without X at the end so
> > > > there shouldnt be a problem with it.
> > >
> > > Marek, please, look in PXA270 datasheet. To support a specific pixel
> > > format means, e.g., to be able to process it further, according to this
> > > format's particular colour component ordering. Process further can mean
> > > convert to another format, extract various information from the data
> > > (statistics, etc.)... Now RGB555 looks like (from wikipedia)
> > >
> > > 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
> > > R4 R3 R2 R1 R0 G4 G3 G2 G1 G1 B4 B3 B2 B1 B1 --
> > >
> > > (Actually, I thought bit 15 was unused, but it doesn't matter for this
> > > discussion.) Now, imagine what happens if you swap the two bytes. I
> > > don't think the PXA will still be able to meaningfully process that
> > > format.
> >
> > Not on the pxa side, but on the camera side -- Bs and Rs swapped in the
> > diagram above.
>
> And then? Are you trying to tell me, that the PXA then swaps them back?...
No, the software has to do it then, I'm trying to tell you that it has nothing
to do with PXA (as PXA really doesnt care if the channel is actually blue or
red).
>
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
> http://www.open-technology.de/
next prev parent reply other threads:[~2009-09-05 21:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200908031031.00676.marek.vasut@gmail.com>
[not found] ` <4A76CB7C.10401@gmail.com>
[not found] ` <Pine.LNX.4.64.0908031415370.5310@axis700.grange>
[not found] ` <4A76DF29.1050008@compulab.co.il>
2009-09-04 19:05 ` [PATCH] Add RGB555X and RGB565X formats to pxa-camera Guennadi Liakhovetski
2009-09-06 6:03 ` Mike Rapoport
2009-09-05 7:26 ` Marek Vasut
2009-09-05 8:55 ` Guennadi Liakhovetski
2009-09-05 9:49 ` Marek Vasut
2009-09-05 20:19 ` Guennadi Liakhovetski
2009-09-05 21:17 ` Marek Vasut [this message]
2009-09-05 22:05 ` Guennadi Liakhovetski
2009-09-06 3:50 ` Marek Vasut
2009-09-06 16:52 ` Guennadi Liakhovetski
2009-09-06 17:51 ` Marek Vasut
2009-09-06 18:15 ` Guennadi Liakhovetski
2009-09-07 4:46 ` Marek Vasut
2009-09-07 6:22 ` Guennadi Liakhovetski
2009-09-07 8:50 ` Marek Vasut
2009-09-07 10:21 ` Robert Jarzmik
2009-09-07 11:53 ` Marek Vasut
2009-09-07 12:10 ` Guennadi Liakhovetski
2009-09-05 15:22 ` Jamie Lokier
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=200909052317.24048.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).