From: Mike Rapoport <mike@compulab.co.il>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Eric Miao <eric.y.miao@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Stefan Herbrechtsmeier <hbmeier@hni.uni-paderborn.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Add RGB555X and RGB565X formats to pxa-camera
Date: Sun, 06 Sep 2009 09:03:32 +0300 [thread overview]
Message-ID: <4AA350B4.30204@compulab.co.il> (raw)
In-Reply-To: <Pine.LNX.4.64.0909042102200.4501@axis700.grange>
Hi Guennadi,
Guennadi Liakhovetski wrote:
> On Mon, 3 Aug 2009, Mike Rapoport wrote:
>
>>> 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?
>> As far as I remember I've tried to overlay the captured imagery using pxa
>> overlay1. Most probably it's left here after those tries.
>
> Mike, could you, please, verify that those bits are indeed unneeded and
> provide patch to remove them?
Unfortunately, I don't have the sensor handy at the time :( The one I've used
then is now broken (physically) and there's no replacement for it :(
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
> http://www.open-technology.de/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2009-09-06 6:03 UTC|newest]
Thread overview: 25+ 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-06 6:03 ` Mike Rapoport [this message]
2009-08-03 13:59 ` Marek Vasut
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
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=4AA350B4.30204@compulab.co.il \
--to=mike@compulab.co.il \
--cc=eric.y.miao@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=hbmeier@hni.uni-paderborn.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marek.vasut@gmail.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