From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Florian Neuhaus <florian.neuhaus@reberinformatik.ch>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: media: i2c: mt9p031: HFLIP/VFLIP changes format
Date: Sat, 22 Jun 2013 01:32:44 +0200 [thread overview]
Message-ID: <2959002.SlIJC0ILYx@avalon> (raw)
In-Reply-To: <6EE9CD707FBED24483D4CB0162E8546745F4218E@AMSPRD0711MB532.eurprd07.prod.outlook.com>
Hi Florian,
On Friday 21 June 2013 15:48:25 Florian Neuhaus wrote:
> Hi Laurent
>
> In the mt9p031 driver, the picture can be flipped either horizontally or
> vertically by using the according V4L2 controls. This can be done at
> runtime.
> I have noticed, that flipping the picture will change the bayer-pattern.
> So if I flip horizontally and vertically to get a 180 degree rotation
> the bayer pattern changes from
> V4L2_MBUS_FMT_SGRBG12_1X12
> to
> V4L2_MBUS_FMT_SGBRG12_1X12
> I'm not sure how the patch should look like...
> The format code could be adapted accordingly to the flipping, but
> how does the userspace notices this change? The user could issue
> another get_format. But what about the omap3isp-pipe?
> Concrete:
> What should I do to configure a streaming pipe with a flipped image?
> Flip the image on the v4l-subdev and then build the pipe?
> Is there a chance to propagate the format change through the pipe
> during streaming?
There are two ways to handle this situation. You could modify the output
format, which would then bring format propagation issues, or you could offset
the sensor crop rectangle by one pixel. The second option is probably easier
to implement as it's local to the sensor, without any need to propagate format
changes.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2013-06-21 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 15:48 media: i2c: mt9p031: HFLIP/VFLIP changes format Florian Neuhaus
2013-06-21 23:32 ` Laurent Pinchart [this message]
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=2959002.SlIJC0ILYx@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=florian.neuhaus@reberinformatik.ch \
--cc=linux-media@vger.kernel.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