Re: [PATCH RFC 0/4] V4L2: Vendor specific media bus formats/ frame size control

[Nicolas THERY <nicolas.thery@st.com>]

Hello,

Thanks for your reply.  It's good to know your proposal is simply on the
back-burner.

Best regards,
Nicolas

On 2012-08-29 20:41, sakari.ailus@iki.fi wrote:
> Hi Nicolas,
>
> On Mon, Aug 27, 2012 at 05:48:43PM +0200, Nicolas THERY wrote:
>> Hello,
>>
>> On 2012-08-23 11:51, Sylwester Nawrocki wrote:
>>> This patch series introduces new image source class control - V4L2_CID_FRAMESIZE
>>> and vendor or device specific media bus format section.
>>>
>>> There was already a discussion WRT handling interleaved image data [1].
>>> I'm not terribly happy with those vendor specific media bus formats but I
>>> couldn't find better solution that would comply with the V4L2 API concepts
>>> and would work reliably.
>> What about Sakari's "Frame format descriptors" RFC[1] that would allow to
>> describe arbitrary pixel code combinations and provide required information
>> (virtual channel and data type) to the CSI receiver driver for configuring the
>> hardware?
> I we'll need to continue that work as well, unfortunately I've had higher
> priority things to do. Still, getting that right is complex and will take
> time. The V4L2 pixel format for this sensor will likely be a
> hardware-specific one for quite a while: this sensor in question sends
> several frames in different formats of a single image at once which doesn't
> match to V4L2's pixel format configuration that assumes a single format.
>
> Kind regards,
>