linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: g.liakhovetski@gmx.de (Guennadi Liakhovetski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Add RGB555X and RGB565X formats to pxa-camera
Date: Fri, 4 Sep 2009 21:05:38 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0909042102200.4501@axis700.grange> (raw)
In-Reply-To: <4A76DF29.1050008@compulab.co.il>

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?

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/

       reply	other threads:[~2009-09-04 19:05 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       ` Guennadi Liakhovetski [this message]
2009-09-06  6:03         ` [PATCH] Add RGB555X and RGB565X formats to pxa-camera 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
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=Pine.LNX.4.64.0909042102200.4501@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --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).