From: Marek Vasut <marek.vasut@gmail.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Eric Miao <eric.y.miao@gmail.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mike Rapoport <mike@compulab.co.il>,
Stefan Herbrechtsmeier <hbmeier@hni.uni-paderborn.de>
Subject: Re: [PATCH] Add RGB555X and RGB565X formats to pxa-camera
Date: Mon, 3 Aug 2009 15:59:32 +0200 [thread overview]
Message-ID: <200908031559.32325.marek.vasut@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0908031415370.5310@axis700.grange>
Dne Po 3. srpna 2009 14:31:12 Guennadi Liakhovetski napsal(a):
> On Mon, 3 Aug 2009, Eric Miao wrote:
> > Marek Vasut wrote:
> > > Hi!
> > >
> > > Eric, would you mind applying ?
> > >
> > > From 4dcbff010e996f4c6e5761b3c19f5d863ab51b39 Mon Sep 17 00:00:00 2001
> > > From: Marek Vasut <marek.vasut@gmail.com>
> > > Date: Mon, 3 Aug 2009 10:27:57 +0200
> > > Subject: [PATCH] Add RGB555X and RGB565X formats to pxa-camera
> > >
> > > Those formats are requiered on widely used OmniVision OV96xx cameras.
> > > Those formats are nothing more then endian-swapped RGB555 and RGB565.
> > >
> > > Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
> >
> > Acked-by: Eric Miao <eric.y.miao@gmail.com>
> >
> > Guennadi,
> >
> > Would be better if this gets merged by you, thanks.
>
> Indeed it would, and I do have a couple of questions to this and related
> patches:
>
> 1. Marek, you're saying, you need these formats for the OV96xx camera. Yre
> you using the patch from Stefan Herbrechtsmeier to support ov96xx or some
> other?
Hi!
I'm writing one mostly (I took some bits from Trilok's earlier attempt) from
scratch, as you can see here:
http://marex-hnd.blogspot.com/2009/08/omnivision-ov9640-hacking.html
http://marex-hnd.blogspot.com/2009/08/omnivision-ov9640-hacking-part.html
>
> 2. Mike, while reviewing this patch I came across code in
> pxa_camera_setup_cicr(), introduced by your earlier patch:
>
> case V4L2_PIX_FMT_RGB555:
> cicr1 |= CICR1_RGB_BPP_VAL(1) | CICR1_RGBT_CONV_VAL(2) |
> CICR1_TBIT | CICR1_COLOR_SP_VAL(1);
> break;
>
> Why are you enabling the RGB to RGBT conversion here unconditionally?
> Generally, what are the advantages of configuring CICR1 for a specific RGB
> format compared to using just a raw capture? Do I understand it right,
> that ATM we are not using any of those features?
>
> Thanks
> Guennadi
>
> > > ---
> > > 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;
>
> ---
> Guennadi Liakhovetski
next prev parent reply other threads:[~2009-08-03 13:59 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200908031031.00676.marek.vasut@gmail.com>
[not found] ` <200908031052.59016.marek.vasut@gmail.com>
2009-08-03 9:17 ` [PATCH] Add RGB555X and RGB565X formats to pxa-camera Trilok Soni
2009-08-03 11:35 ` Eric Miao
2009-08-03 11:43 ` Trilok Soni
2009-08-03 12:31 ` Guennadi Liakhovetski
2009-08-03 12:59 ` Mike Rapoport
2009-09-04 19:05 ` Guennadi Liakhovetski
2009-09-04 19:05 ` Guennadi Liakhovetski
2009-09-06 6:03 ` Mike Rapoport
2009-09-06 6:03 ` Mike Rapoport
2009-08-03 13:59 ` Marek Vasut [this message]
2009-09-05 7:26 ` Marek Vasut
2009-09-05 7:26 ` Marek Vasut
2009-09-05 8:55 ` Guennadi Liakhovetski
2009-09-05 8:55 ` Guennadi Liakhovetski
2009-09-05 9:49 ` Marek Vasut
2009-09-05 9:49 ` Marek Vasut
2009-09-05 20:19 ` Guennadi Liakhovetski
2009-09-05 20:19 ` Guennadi Liakhovetski
2009-09-05 21:17 ` Marek Vasut
2009-09-05 21:17 ` Marek Vasut
2009-09-05 22:05 ` Guennadi Liakhovetski
2009-09-05 22:05 ` Guennadi Liakhovetski
2009-09-06 3:50 ` Marek Vasut
2009-09-06 3:50 ` Marek Vasut
2009-09-06 16:52 ` Guennadi Liakhovetski
2009-09-06 16:52 ` Guennadi Liakhovetski
2009-09-06 17:51 ` Marek Vasut
2009-09-06 17:51 ` Marek Vasut
2009-09-06 18:15 ` Guennadi Liakhovetski
2009-09-06 18:15 ` Guennadi Liakhovetski
2009-09-07 4:46 ` Marek Vasut
2009-09-07 4:46 ` Marek Vasut
2009-09-07 6:22 ` Guennadi Liakhovetski
2009-09-07 6:22 ` Guennadi Liakhovetski
2009-09-07 8:50 ` Marek Vasut
2009-09-07 8:50 ` Marek Vasut
2009-09-07 10:21 ` Robert Jarzmik
2009-09-07 10:21 ` Robert Jarzmik
2009-09-07 11:53 ` Marek Vasut
2009-09-07 11:53 ` Marek Vasut
2009-09-07 12:10 ` Guennadi Liakhovetski
2009-09-07 12:10 ` Guennadi Liakhovetski
2009-09-05 15:22 ` Jamie Lokier
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=200908031559.32325.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=hbmeier@hni.uni-paderborn.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-media@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mike@compulab.co.il \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.