From: Yu Dai <yu.dai@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v4] drm/i915: add support for Z-order of planes for VLV.
Date: Tue, 04 Mar 2014 17:37:39 -0800 [thread overview]
Message-ID: <53167FE3.20800@intel.com> (raw)
In-Reply-To: <20140304082021.GE17720@nuc-i3427.alporthouse.com>
[-- Attachment #1.1: Type: text/plain, Size: 1346 bytes --]
Chris,
This looks like a hw specific value which is difficult to understand.
However, the definition of these values are just a list of available
options of z-order. On Intel VLV, there is only 6 options for the three
planes Primary, Sprite A and Sprite B. Cursor is always on top. For
example, "P1S1S2C1" means z-order (from bottom to top) of Primary ->
Sprite A -> Sprite B -> Cursor.
#define P1S1S2C1 0
#define P1S2S1C1 8
#define S2P1S1C1 1
#define S2S1P1C1 9
#define S1P1S2C1 4
#define S1S2P1C1 6
In theory, if hw supports, each CRTC may have their own plane z-order if
user intentionally wants that happens. The pipe info (0 or 1) is packed
into z-order value with extra bit (bit 31).
Thanks,
Alex
On 14-03-04 12:20 AM, Chris Wilson wrote:
> On Mon, Mar 03, 2014 at 02:12:28PM -0800, yu.dai@intel.com wrote:
>> From: "Yu(Alex) Dai" <yu.dai@intel.com>
>>
>> Add "zorder" property to crtc to control Z-order of sprite and
>> primary planes. The alpha channel of the planes can be enabled or
>> disabled during Z-order change.
>
> Can I just say that is an abonimal user interface. You expect the
> client to encode a hw specific value into a CRTC property that
> affects global state. and given the two properties on the two CRTCs,
> which should userspace believe? -Chris
>
[-- Attachment #1.2: Type: text/html, Size: 2347 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-03-05 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 22:12 [PATCH v4] drm/i915: add support for Z-order of planes for VLV yu.dai
2014-03-04 8:20 ` Chris Wilson
2014-03-05 1:37 ` Yu Dai [this message]
2014-03-10 20:59 ` Matt Roper
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=53167FE3.20800@intel.com \
--to=yu.dai@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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