All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Rob Clark <robdclark@gmail.com>
Cc: "linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	Erik Gilling <konkers@google.com>
Subject: Re: [RFC 0/4] Atomic Display Framework
Date: Fri, 30 Aug 2013 17:11:47 +0300	[thread overview]
Message-ID: <20130830141147.GK11428@intel.com> (raw)
In-Reply-To: <CAF6AEGuUELs=yyg6CyrHczYAo_VYYj-16eb-hXK=8oxjnjqYTA@mail.gmail.com>

On Fri, Aug 30, 2013 at 10:00:28AM -0400, Rob Clark wrote:
> On Thu, Aug 29, 2013 at 7:34 PM, Greg Hackmann <ghackmann@google.com> wrote:
> > On Thu, Aug 29, 2013 at 5:54 AM, Rob Clark <robdclark@gmail.com> wrote:
> >>
> >> I guess if you have multiple encoders + multiple connectors for the
> >> "ganging" case, then it probably just looks like 2x displays, and
> >> nothing more really needed?
> >>
> >> I'm a bit fuzzy on what the hw looks like in this "ganging" scenario,
> >> so I'm not completely sure what the best approach is.  But if we do
> >> have hw like this, then it makes sense to support it *somehow* in KMS.
> >
> >
> > I don't have the hardware anymore so this is all working from memory, it
> > didn't look like two independent displays.  You had to explicitly set up
> > connections between the two mixers to deal with things like scaled overlays
> > that spanned both mixers (there was some in-hardware magic to make sure
> > there wasn't a visible seam where the two mixers met).
> 
> Ok, sounds like mixer == crtc (ie. the thing the combines one or more
> planes)?  So it sounds maybe a bit like:
> 
>  plane0_0 -\
>     ...    +---> CRTC -\
>  plane0_n -/           |
>                        +--> encoder -> connector
>  plane1_0 -\           |
>     ...    +---> CRTC -/
>  plane1_n -/

So I wonder if we should just add the x,y,w,h output parameters to crtc.
That could also be used to specify borders in the normal one crtc per
encoder case. Although the border color is then a bit a question mark.
Supposedly the crtc can have its own background color, but i guess the
border color need not match that necessarily. So maybe add an encoder
bg color property too (or maybe just slap it to the connector since we
don't currently have encoder properties).

Another related thing I really want to expose is the crtc input size
(ie. the coordinate space that the planes' output coordinates live in).
That way the user will get explicit control over the scaler in the crtc
(panel fitter in i915 lingo).

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2013-08-30 14:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29  1:51 [RFC 0/4] Atomic Display Framework Greg Hackmann
2013-08-29  1:51 ` [RFC 1/4] video: Add generic display entity core Greg Hackmann
2013-08-29  1:51 ` [RFC 2/4] video: add atomic display framework Greg Hackmann
2013-08-29  1:51 ` [RFC 3/4] video: adf: add display core helper Greg Hackmann
2013-08-29  1:51 ` [RFC 4/4] video: adf: add memblock helper Greg Hackmann
2013-08-29  3:51 ` [RFC 0/4] Atomic Display Framework Rob Clark
2013-08-29  7:01   ` [Linaro-mm-sig] " Daniel Vetter
2013-08-29  7:58     ` Ville Syrjälä
2013-08-29  8:52       ` Damien Lespiau
2013-08-29 12:59       ` Rob Clark
2013-08-29 12:25     ` Rob Clark
2013-08-29  7:36   ` Ville Syrjälä
2013-08-29 12:54     ` Rob Clark
2013-08-29 23:34       ` Greg Hackmann
2013-08-30 14:00         ` Rob Clark
2013-08-30 14:11           ` Ville Syrjälä [this message]
2013-09-02  7:39           ` Daniel Vetter
2013-09-02 13:19             ` Rob Clark
2013-09-02 15:26               ` Alex Deucher
2013-08-29 23:26     ` Greg Hackmann
2013-08-30 13:55       ` Rob Clark
2013-08-30 14:01       ` Ville Syrjälä

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=20130830141147.GK11428@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=konkers@google.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=robdclark@gmail.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.