All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Plattner <aplattner@nvidia.com>
To: Keith Packard <keithp@keithp.com>,
	Dave Airlie <airlied@gmail.com>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: role of crtcs in modesetting interfaces and possible abstraction away from userspace
Date: Tue, 9 Sep 2014 23:29:52 -0700	[thread overview]
Message-ID: <540FEFE0.6080605@nvidia.com> (raw)
In-Reply-To: <86bnqppadp.fsf@hiro.keithp.com>

On 09/08/2014 11:37 PM, Keith Packard wrote:
> With atomic mode setting in the kernel, I think you're probably right in
> proposing to eliminate explicit CRTC allocation from that. I do think
> you'll want to indicate the number of available CRTCs in the display
> engine, and the number of CRTCs each monitor consumes. Do you know if
> there are some of these monitors that can display lower resolution modes
> with only a single CRTC? Or is the hardware so separate that you end up
> always using multiple CRTCs to drive them?

The one I tried definitely can; indeed it has to because the VBIOS 
doesn't know how to set up MST and drives the port in DP 1.1 mode.  I'm 
sure someone will build a monitor that only turns on half of the display 
if you do that, but I'd be kind of surprised if someone made one that 
just doesn't work if you use a DP 1.1-only GPU.

-- 
Aaron

  reply	other threads:[~2014-09-10  6:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09  0:43 role of crtcs in modesetting interfaces and possible abstraction away from userspace Dave Airlie
2014-09-09  6:37 ` Keith Packard
2014-09-10  6:29   ` Aaron Plattner [this message]
2014-09-09  7:58 ` Dave Airlie
2014-09-09  8:16 ` Ville Syrjälä
2014-09-09 23:22   ` Rob Clark
2014-09-10  8:20     ` Ville Syrjälä
2014-09-10 13:28       ` Rob Clark
2014-09-10 16:27   ` David Herrmann
2014-09-10 17:04 ` Alex Deucher

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=540FEFE0.6080605@nvidia.com \
    --to=aplattner@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=keithp@keithp.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.