From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: "Dave Airlie" <airlied@gmail.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Daniel Vetter" <daniel@ffwll.ch>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/atomic: Allow for holes in connector state.
Date: Mon, 22 Feb 2016 10:34:48 +0100 [thread overview]
Message-ID: <56CAD638.6060704@linux.intel.com> (raw)
In-Reply-To: <CAPM=9txVNf4khexm-7m=1Hw4sxgj6VhhL46EKr=ZTk1qDTosnQ@mail.gmail.com>
Op 19-02-16 om 04:21 schreef Dave Airlie:
> On 16 February 2016 at 21:37, Ville Syrjälä
> <ville.syrjala@linux.intel.com> wrote:
>> On Mon, Feb 15, 2016 at 02:17:01PM +0100, Maarten Lankhorst wrote:
>>> Because we record connector_mask using 1 << drm_connector_index now
>>> the connector_mask should stay the same even when other connectors
>>> are removed. This was not the case with MST, in that case when removing
>>> a connector all other connectors may change their index.
>>>
>>> This is fixed by waiting until the first get_connector_state to allocate
>>> connector_state, and force reallocation when state is too small.
>>>
>>> As a side effect connector arrays no longer have to be preallocated,
>>> and can be allocated on first use which means a less allocations in
>>> the page flip only path.
> Daniel you said something on irc about v2 of this for -fixes? Did I miss v2?
>
> Dave.
"[PATCH v2] drm/atomic: Allow for holes in connector state, v2."
It wasn't sent in this thread to give CI a chance to run.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-02-22 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 13:17 [PATCH] drm/atomic: Allow for holes in connector state Maarten Lankhorst
2016-02-15 14:30 ` kbuild test robot
2016-02-16 11:02 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-02-16 11:37 ` [PATCH] " Ville Syrjälä
2016-02-19 3:21 ` [Intel-gfx] " Dave Airlie
2016-02-22 9:34 ` Maarten Lankhorst [this message]
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=56CAD638.6060704@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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.