All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
	laurent.pinchart@ideasonboard.com, gjasny@googlemail.com,
	hdegoede@redhat.com, kyungmin.park@samsung.com
Subject: Re: [v4l-utils PATCH/RFC v5 00/14] Add a plugin for Exynos4 camera
Date: Mon, 08 Jun 2015 12:21:02 +0200	[thread overview]
Message-ID: <55756C8E.4020304@samsung.com> (raw)
In-Reply-To: <55756225.30108@xs4all.nl>

On 06/08/2015 11:36 AM, Hans Verkuil wrote:
> On 06/08/2015 11:14 AM, Jacek Anaszewski wrote:
>> Hi Hans,
>>
>> It got stuck on this version. I have some slight improvements locally
>> but haven't sent them as there hasn't been any comment to this so far.
>> AFAIR Sakari had some doubts about handling multiple pipelines within
>> one media controller. In this approach only one pipeline is allowed.
>> There has to be a new IOCTL added for locking pipelines, to handle this
>> IIRC.
>
> Sakari, is this ioctl really needed or something that can be added later?
>
>> Besides there are some v4l-utils build system dependency issues to
>> solve, I mentioned below in the cover letter.
>
> If I remember correctly the libmediactl API may still change, which is
> why it isn't in lib. So statically linking it isn't a bad idea at the
> moment. Laurent, can you confirm this?
>
> Is there anything else that blocks this patch series?

v4l-utils side issues:

I'd have to apply my local bug fixes and submit the next version.

Kernel side issues:

There is a regression in the kernel related to FIMC-LITE
and FIMC-IS-ISP entities. Effectively currently it is only possible
to setup pipelines with S5C73M3 sensor to fimc.0.capture and
fimc.1.capture entities.

I would also have to rebase the patches for exynos4-is driver
for avoiding failure on open when the device being opened
has no connected sensor.

-- 
Best Regards,
Jacek Anaszewski

      reply	other threads:[~2015-06-08 10:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 15:59 [v4l-utils PATCH/RFC v5 00/14] Add a plugin for Exynos4 camera Jacek Anaszewski
2015-02-26 15:59 ` [v4l-utils PATCH/RFC v5 01/14] mediactl: Introduce v4l2_subdev structure Jacek Anaszewski
2015-02-26 15:59 ` [v4l-utils PATCH/RFC v5 02/14] mediactl: Add support for v4l2-ctrl-redir config Jacek Anaszewski
2015-02-26 15:59 ` [v4l-utils PATCH/RFC v5 03/14] mediactl: Separate entity and pad parsing Jacek Anaszewski
2015-02-26 15:59 ` [v4l-utils PATCH/RFC v5 04/14] mediatext: Add library Jacek Anaszewski
2015-02-26 15:59 ` [v4l-utils PATCH/RFC v5 05/14] mediactl: Add media device graph helpers Jacek Anaszewski
2015-02-26 15:59 ` [v4l-utils PATCH/RFC v5 06/14] mediactl: Add media_device creation helpers Jacek Anaszewski
2015-02-26 15:59 ` [v4l-utils PATCH/RFC v5 07/14] mediactl: libv4l2subdev: add VYUY8_2X8 mbus code Jacek Anaszewski
2015-02-26 15:59 ` [v4l-utils PATCH/RFC v5 08/14] mediactl: Add support for media device pipelines Jacek Anaszewski
2015-02-26 15:59 ` [v4l-utils PATCH/RFC v5 09/14] mediactl: libv4l2subdev: add support for comparing mbus formats Jacek Anaszewski
2015-02-26 15:59 ` [v4l-utils PATCH/RFC v5 10/14] mediactl: libv4l2subdev: add support for setting pipeline format Jacek Anaszewski
2015-02-26 15:59 ` [v4l-utils PATCH/RFC v5 11/14] mediactl: libv4l2subdev: add get_pipeline_entity_by_cid function Jacek Anaszewski
2015-02-26 15:59 ` [v4l-utils PATCH/RFC v5 12/14] mediactl: Add media device ioctl API Jacek Anaszewski
2015-02-26 15:59 ` [v4l-utils PATCH/RFC v5 13/14] mediactl: libv4l2subdev: Enable opening/closing pipelines Jacek Anaszewski
2015-02-26 15:59 ` [v4l-utils PATCH/RFC v5 14/14] Add a libv4l plugin for Exynos4 camera Jacek Anaszewski
2015-06-08  8:27 ` [v4l-utils PATCH/RFC v5 00/14] Add a " Hans Verkuil
2015-06-08  9:14   ` Jacek Anaszewski
2015-06-08  9:36     ` Hans Verkuil
2015-06-08 10:21       ` Jacek Anaszewski [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=55756C8E.4020304@samsung.com \
    --to=j.anaszewski@samsung.com \
    --cc=gjasny@googlemail.com \
    --cc=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=kyungmin.park@samsung.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.