linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>Laurent
	Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Tomasz Stanislawski <t.stanislaws@samsung.com>,
	linux-fbdev@vger.kernel.org,
	Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>,
	Pawel Osciak <pawel@osciak.com>,
	Marcus Lorentzon <marcus.lorentzon@linaro.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	dri-devel@lists.freedesktop.org,
	Alexander Deucher <alexander.deucher@amd.com>,
	Rob Clark <rob@ti.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-media@vger.kernel.org
Subject: Re: Kernel Display and Video API Consolidation mini-summit at ELC 2012 - Notes
Date: Sat, 18 Feb 2012 00:56:49 +0000	[thread overview]
Message-ID: <867gzlarhq.fsf@sumi.keithp.com> (raw)
In-Reply-To: <1775349.d0yvHiVdjB@avalon>

<#part sign=pgpmime>
On Fri, 17 Feb 2012 00:25:51 +0100, Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:

> ***  Synchronous pipeline changes ***
> 
>   Goal: Create an API to apply complex changes to a video pipeline atomically.
> 
>   Needed for complex camera use cases. On the DRM/KMS side, the approach is to
>   use one big ioctl to configure the whole pipeline.

This is the only credible approach for most desktop chips -- you must
have the whole configuration available before you can make any
commitment to supporting the requested modes.

>   One solution is a commit ioctl, through the media controller device, that
>   would be dispatched to entities internally with a prepare step and a commit
>   step.

The current plan for the i915 KMS code is to use a single ioctl -- the
application sends a buffer full of configuration commands down to the
kernel which can then figure out whether it can be supported or not.

The kernel will have to store the intermediate data until the commit
arrives anyways, and you still need a central authority in the kernel
controlling the final commit decision.

-- 
keith.packard@intel.com

  parent reply	other threads:[~2012-02-18  0:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201201171126.42675.laurent.pinchart@ideasonboard.com>
     [not found] ` <1654816.MX2JJ87BEo@avalon>
2012-02-16 23:25   ` Kernel Display and Video API Consolidation mini-summit at ELC 2012 - Notes Laurent Pinchart
2012-02-17  9:55     ` Daniel Vetter
2012-02-17 18:46       ` Laurent Pinchart
2012-02-22 16:03         ` James Simmons
2012-02-22 16:24           ` Daniel Vetter
2012-02-22 16:28             ` Rob Clark
2012-02-23  7:34               ` Michel Dänzer
2012-02-22 16:36             ` Chris Wilson
2012-02-22 16:40               ` Clark, Rob
2012-02-22 17:26                 ` James Simmons
2012-02-23  0:15                 ` Alan Cox
2012-02-22 17:00           ` Adam Jackson
2012-02-20 16:09       ` Guennadi Liakhovetski
2012-02-20 16:19         ` David Airlie
2012-05-17  2:46         ` Jun Nie
2012-05-17  7:53           ` Hans Verkuil
2012-02-17 11:19     ` Semwal, Sumit
2012-02-17 18:49       ` Laurent Pinchart
2012-02-17 19:42     ` Adam Jackson
2012-02-18 17:53       ` Clark, Rob
2012-02-18  0:56     ` Keith Packard [this message]
2012-02-20 16:40     ` Guennadi Liakhovetski
2012-03-02 14:23     ` Heiko Stübner

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=867gzlarhq.fsf@sumi.keithp.com \
    --to=keithp@keithp.com \
    --cc=alexander.deucher@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=magnus.damm@gmail.com \
    --cc=marcus.lorentzon@linaro.org \
    --cc=pawel@osciak.com \
    --cc=rob@ti.com \
    --cc=sakari.ailus@maxwell.research.nokia.com \
    --cc=t.stanislaws@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;
as well as URLs for NNTP newsgroup(s).