From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: Shuzhen Wang <shuzhenw@codeaurora.org>
Cc: "'Laurent Pinchart'" <laurent.pinchart@ideasonboard.com>,
"'Mauro Carvalho Chehab'" <mchehab@redhat.com>,
"'Hans Verkuil'" <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org, hzhong@codeaurora.org, "Yan,
Yupeng" <yyan@quicinc.com>
Subject: Re: RFC: V4L2 driver for Qualcomm MSM camera.
Date: Tue, 04 Jan 2011 13:30:28 +0200 [thread overview]
Message-ID: <4D2304D4.6070806@maxwell.research.nokia.com> (raw)
In-Reply-To: <000001cbabb8$49892d10$dc9b8730$@org>
Hello,
Shuzhen Wang wrote:
>> -----Original Message-----
>> From: Laurent Pinchart [mailto:laurent.pinchart@ideasonboard.com]
>> Sent: Tuesday, December 28, 2010 12:24 PM
>> To: Shuzhen Wang
>> Cc: 'Mauro Carvalho Chehab'; 'Hans Verkuil'; linux-
>> media@vger.kernel.org; hzhong@codeaurora.org; Yan, Yupeng
>> Subject: Re: RFC: V4L2 driver for Qualcomm MSM camera.
>>
>> I will strongly NAK any implementation that requires a daemon.
>>
>
> We understand the motivation behind making the daemon optional.
> However there are restrictions from legal perspective, which we
> don't know how to get around.
>
> A simplest video streaming data flow with MSM ISP is like this:
>
> Sensor -> ISP Hardware pipeline -> videobuf
>
> The procedure to set up ISP pipeline is proprietary and cannot
> be open sourced. Without proper pipeline configuration, streaming
> won't work. And That's why we require the daemon.
Why not? In my opinion the pipeline configuration is quite basic
functionality present also in the OMAP3 ISP, for example. This should be
available through the Media controller interface.
In general, the driver should expose APIs best suited for configuring
the ISP hardware. Existing APIs should be used as much as possible.
There should be no untyped blob passing in its API.
Regards,
--
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com
prev parent reply other threads:[~2011-01-04 11:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 19:38 RFC: V4L2 driver for Qualcomm MSM camera Shuzhen Wang
2010-12-24 11:19 ` Hans Verkuil
2010-12-27 6:45 ` Shuzhen Wang
2010-12-27 12:11 ` Mauro Carvalho Chehab
2010-12-28 18:35 ` Shuzhen Wang
2010-12-28 20:23 ` Laurent Pinchart
2011-01-04 2:37 ` Shuzhen Wang
2011-01-04 6:14 ` Haibo Zhong
2011-01-04 8:46 ` Laurent Pinchart
2011-01-04 10:40 ` Hans Verkuil
2011-01-04 14:29 ` Mauro Carvalho Chehab
2011-01-04 18:08 ` Markus Rechberger
2011-01-04 19:37 ` Yan, Yupeng
2011-01-05 0:15 ` Laurent Pinchart
2011-01-07 0:03 ` Yupeng Yan
2011-01-07 14:37 ` Laurent Pinchart
2011-01-04 8:35 ` Laurent Pinchart
2011-01-04 11:30 ` Sakari Ailus [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=4D2304D4.6070806@maxwell.research.nokia.com \
--to=sakari.ailus@maxwell.research.nokia.com \
--cc=hverkuil@xs4all.nl \
--cc=hzhong@codeaurora.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=shuzhenw@codeaurora.org \
--cc=yyan@quicinc.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