From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Daniel Stone <daniel@fooishbar.org>
Cc: Ander Conselvan de Oliveira
<ander.conselvan.de.oliveira@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Paulo Zanoni <paulo.r.zanoni@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/i915: Enable atomic support by default on supported platforms.
Date: Fri, 3 Feb 2017 09:32:06 +0100 [thread overview]
Message-ID: <e107316b-ae02-42bd-bf66-cc4d722eeda6@linux.intel.com> (raw)
In-Reply-To: <CAPj87rPT3FsY=Fm8-WAQhftcn=R465EZC38PHnNd0NWDvRQfbg@mail.gmail.com>
Hey,
Op 02-02-17 om 17:26 schreef Daniel Stone:
> Hi,
>
> On 2 February 2017 at 07:41, Maarten Lankhorst
> <maarten.lankhorst@linux.intel.com> wrote:
>> i915 is pretty much feature complete. Support for atomic i915-specific
>> connector properties is still missing; those properties can (for now)
>> only be set through the legacy ioctl.
>>
>> ILK style watermarks and gen9+ watermarks are handled atomically,
>> and nonblocking modesets work. FBC has also been made to work with
>> atomic.
>>
>> gen4x- and vlv/chv watermarks still need to be fixed, so disable atomic
>> by default there for now.
>>
>> Flip the switch!!
> Not until we have the multi-CRTC event support please. :\ I don't want
> to have divergent event paths for atomic-but-useless-events.
>
> I've been frantically typing up support for this in Weston (actual
> proper atomic modesetting, which is difficult when you have fiercely
> independent per-output repaint loops, but seems ~mostly done but for
> typing), which I'd hoped to have done a week or two ago but got
> derailed due to being sick. It's coming just as quickly as I can type
> it tho.
>
> Cheers,
> Daniel
Do you mean like ander's https://lists.freedesktop.org/archives/dri-devel/2015-August/088621.html reserved->crtc_id?
I've recreated the same patch locally for exactly that issue before I was aware of its existance. It's easy to hit, and it would be nice if it was merged.
~Maarten
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-02-03 8:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 7:41 [PATCH] drm/i915: Enable atomic support by default on supported platforms Maarten Lankhorst
2017-02-02 8:25 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-02-02 15:20 ` [PATCH] " Lyude Paul
2017-02-02 16:26 ` Daniel Stone
2017-02-03 8:32 ` Maarten Lankhorst [this message]
2017-02-09 12:49 ` Maarten Lankhorst
2017-02-09 13:54 ` Daniel Stone
2017-02-09 15:01 ` Maarten Lankhorst
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=e107316b-ae02-42bd-bf66-cc4d722eeda6@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=ander.conselvan.de.oliveira@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@fooishbar.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=rodrigo.vivi@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.