From: Christoph Fritz <chf.fritz@googlemail.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
javier Martin <javier.martin@vista-silicon.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Shawn Guo <shawn.guo@linaro.org>,
"Hans J. Koch" <hjk@hansjkoch.de>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH v2] media: i.MX27 camera: fix picture source width
Date: Tue, 12 Mar 2013 09:25:13 +0100 [thread overview]
Message-ID: <1363076713.3873.21.camel@mars> (raw)
In-Reply-To: <Pine.LNX.4.64.1303120847480.680@axis700.grange>
On Tue, 2013-03-12 at 08:58 +0100, Guennadi Liakhovetski wrote:
> On Thu, 7 Mar 2013, javier Martin wrote:
> > What mbus format are you using? Could you please check if the s_width
> > value that your sensor mt9m001 returns is correct? Remember it should
> > be in pixels, not in bytes.
>
> Thanks for looking at this. But here's my question: for a pass-through
> mode mx2_camera uses a 16-bpp (RGB565) format. But what if it's actually
> an 8-bpp format, don't you then have to adjust line-width register
> settings? If you don't do that, the camera interface would expect a double
> number of bytes per line, so, it could get confused by HSYNC coming after
> half-line?
To emphasize this: I'm using here a mt9m001 (monochrome) camera with an
8-bpp format.
Thanks
-- Christoph
next prev parent reply other threads:[~2013-03-12 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 17:08 [PATCH] media: i.MX27 camera: fix picture source width Christoph Fritz
2013-02-15 17:24 ` Greg KH
2013-02-16 10:19 ` [PATCH v2] " Christoph Fritz
2013-03-05 17:56 ` Guennadi Liakhovetski
2013-03-07 10:11 ` javier Martin
2013-03-12 7:58 ` Guennadi Liakhovetski
2013-03-12 8:25 ` Christoph Fritz [this message]
2013-03-12 8:34 ` javier Martin
2013-03-12 9:39 ` Guennadi Liakhovetski
2013-03-12 10:11 ` javier Martin
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=1363076713.3873.21.camel@mars \
--to=chf.fritz@googlemail.com \
--cc=g.liakhovetski@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=hjk@hansjkoch.de \
--cc=javier.martin@vista-silicon.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=shawn.guo@linaro.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 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.