From: Michael Jones <michael.jones@matrix-vision.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [RFC] ISP lane shifter support
Date: Mon, 24 Jan 2011 15:16:28 +0100 [thread overview]
Message-ID: <4D3D89BC.8070305@matrix-vision.de> (raw)
In-Reply-To: <201101241457.44866.laurent.pinchart@ideasonboard.com>
Hi Laurent,
On 01/24/2011 02:57 PM, Laurent Pinchart wrote:
<snip>
>>>
>>> As the lane shifter is located at the CCDC input, it might be easier to
>>> implement support for this using the CCDC input format. ispvideo.c would
>>> need to validate the pipeline when the output of the entity connected to
>>> the CCDC input (parallel sensor, CCP2 or CSI2) is configured with a
>>> format that can be shifted to the format at the CCDC input.
>>
>> This crossed my mind, but it seems illogical to have a link with a
>> different format at each of its ends.
>
> I agree in theory, but it might be problematic for the CCDC. Right now the
> CCDC can write to memory or send the data to the preview engine, but not both
> at the same time. That's something that I'd like to change in the future. What
> happens if the user then sets different widths on the output pads ?
>
Shouldn't we prohibit the user from doing this in ccdc_[try/set]_format
in the first place? By "prohibit", I mean shouldn't we be sure that the
pixel format on pad 1 is always the same as on pad 2? Downside: this
suggests that set_fmt on pad 2 could change the fmt on pad 1, which may
be unexpected. But that does at least reflect the reality of the
hardware, right?
<snip>
Michael
MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner
next prev parent reply other threads:[~2011-01-24 14:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 8:40 [RFC] ISP lane shifter support Michael Jones
2011-01-24 0:10 ` Laurent Pinchart
2011-01-24 13:47 ` Michael Jones
2011-01-24 13:57 ` Laurent Pinchart
2011-01-24 14:16 ` Michael Jones [this message]
2011-01-24 19:45 ` Laurent Pinchart
2011-01-25 9:10 ` Michael Jones
2011-01-25 9:20 ` Laurent Pinchart
2011-01-26 23:46 ` Guennadi Liakhovetski
2011-02-02 10:36 ` Michael Jones
2011-02-11 12:07 ` Michael Jones
2011-02-11 13:06 ` Laurent Pinchart
2011-02-22 12:36 ` Michael Jones
2011-02-24 11:57 ` Hans Verkuil
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=4D3D89BC.8070305@matrix-vision.de \
--to=michael.jones@matrix-vision.de \
--cc=laurent.pinchart@ideasonboard.com \
--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