All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: David Herrmann <dh.herrmann@googlemail.com>,
	Daniel Vetter <daniel.vetter@ffwll.com>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v2] mode: Retrieve only the current information for a Connector
Date: Wed, 4 Mar 2015 12:34:35 +0000	[thread overview]
Message-ID: <20150304123435.GH26004@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <CAKMK7uEM0POLOv57Lmzpc6s3hMjBXhpCFw1Jm18L5eVpjm79Fg@mail.gmail.com>

On Wed, Mar 04, 2015 at 01:31:46PM +0100, Daniel Vetter wrote:
> On Wed, Mar 4, 2015 at 12:29 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > On Wed, Mar 04, 2015 at 12:08:42PM +0100, Daniel Vetter wrote:
> >> On Wed, Mar 04, 2015 at 10:38:08AM +0000, Chris Wilson wrote:
> >> > +   if (conn.encoder_id) {
> >> > +           r->count_encoders = 1;
> >>
> >> This only works for i915 where we only ever have 1 encoder. Other drivers
> >> reassign encoders depending upon output type (e.g. dvi-i vs dvi-d). Imo
> >> it'd be cleaner to do something like the below:
> >
> > Not quite. This value is the currently active encoder_id for the
> > connector; there can only be one. As opposed to the array of associated
> > encoders that we normally supply on ouptut. Even i915 has multiple
> > encoders on connectors nowadays!
> 
> DRM_MAX_ENCODER in the kernel is 3. And i915 has multipled connectors
> for the same encoder, but not the other way round. Having multiple
> encoders is the reason for the best_encoders callback in the crtc
> helpers, which we've ditched for i915 (we always pick the single
> intel_connector->encoder statically assigned at load time).

We have multiple encoders on the same connector, since 3.17.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-03-04 12:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 10:30 [PATCH] mode: Retrieve only the current information for a Connector Chris Wilson
2015-03-04 10:38 ` [PATCH v2] " Chris Wilson
2015-03-04 11:08   ` Daniel Vetter
2015-03-04 11:10     ` Daniel Stone
2015-03-04 11:29     ` Chris Wilson
2015-03-04 12:31       ` Daniel Vetter
2015-03-04 12:34         ` Chris Wilson [this message]
2015-03-04 12:53           ` Daniel Vetter
2015-03-04 13:01             ` [PATCH v3] " Chris Wilson
2015-03-04 13:16               ` [PATCH v4] " Chris Wilson
2015-03-04 18:00                 ` Daniel Vetter

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=20150304123435.GH26004@nuc-i3427.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.com \
    --cc=daniel@ffwll.ch \
    --cc=dh.herrmann@googlemail.com \
    --cc=dri-devel@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 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.