From: Sylwester Nawrocki <snjw23@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Sakari Ailus <sakari.ailus@iki.fi>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
"HeungJun Kim/Mobile S/W Platform Lab(DMC)/E3"
<riverful.kim@samsung.com>,
"Seung-Woo Kim/Mobile S/W Platform Lab(DMC)/E4"
<sw0312.kim@samsung.com>, Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [Q] Interleaved formats on the media bus
Date: Sat, 04 Feb 2012 16:38:50 +0100 [thread overview]
Message-ID: <4F2D510A.1040503@gmail.com> (raw)
In-Reply-To: <3142039.4Ht9bV5jFQ@avalon>
Hi Laurent,
On 02/04/2012 12:30 PM, Laurent Pinchart wrote:
>> I'd be much in favour or using a separate channel ID as Guennadi asked;
>> that way you could quite probably save one memory copy as well. But if
>> the hardware already exists and behaves badly there's usually not much
>> you can do about it.
>
> If I'm not mistaken, the sensor doesn't send data in separate channels but
I suspect it might be sending data on separate virtual channels, but the
bridge won't understand that and will just return one data plane in memory.
The sensor might well send the data in one channel, I don't know myself yet.
In either case we end up with a mixed data in memory, that must be parsed,
which is likely best done in the user space.
Also please see my previous answer to Sakari, there is some more details
there.
> interleaves them in a single channel (possibly with headers or fixed-size
> packets - Sylwester, could you comment on that ?). That makes it pretty
> difficult to do anything else than pass-through capture.
I'm not entirely sure the sensor doesn't send the data in separate virtual
channels. Certainly the bridge cannot DMA each channel into separate memory
buffers.
--
Regards,
Sylwester
next prev parent reply other threads:[~2012-02-04 15:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 11:23 [Q] Interleaved formats on the media bus Sylwester Nawrocki
2012-02-01 1:44 ` Guennadi Liakhovetski
2012-02-01 10:44 ` Sylwester Nawrocki
2012-02-01 10:00 ` Sakari Ailus
2012-02-01 11:41 ` Sylwester Nawrocki
2012-02-02 9:55 ` Laurent Pinchart
2012-02-02 11:00 ` Guennadi Liakhovetski
2012-02-04 11:36 ` Laurent Pinchart
2012-02-02 11:14 ` Sylwester Nawrocki
2012-02-04 11:34 ` Laurent Pinchart
2012-02-04 17:00 ` Sylwester Nawrocki
2012-02-05 13:30 ` Laurent Pinchart
2012-02-08 22:48 ` Sylwester Nawrocki
[not found] ` <12779203.vQPWKN8eZf@avalon>
2012-02-10 8:42 ` Guennadi Liakhovetski
2012-02-10 10:19 ` Sylwester Nawrocki
2012-02-10 10:31 ` Sylwester Nawrocki
2012-02-10 10:33 ` Guennadi Liakhovetski
2012-02-10 10:58 ` Sylwester Nawrocki
2012-02-10 11:15 ` Guennadi Liakhovetski
2012-02-10 11:35 ` Sylwester Nawrocki
2012-02-10 11:51 ` Guennadi Liakhovetski
2012-02-04 11:22 ` Sakari Ailus
2012-02-04 11:30 ` Laurent Pinchart
2012-02-04 15:38 ` Sylwester Nawrocki [this message]
2012-02-04 15:26 ` Sylwester Nawrocki
2012-02-04 15:43 ` Sakari Ailus
2012-02-04 18:32 ` Sylwester Nawrocki
2012-02-04 23:44 ` Guennadi Liakhovetski
2012-02-05 0:36 ` Sylwester Nawrocki
2012-02-05 0:04 ` Guennadi Liakhovetski
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=4F2D510A.1040503@gmail.com \
--to=snjw23@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=riverful.kim@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@iki.fi \
--cc=sw0312.kim@samsung.com \
/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