From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: jani.nikula@intel.com, "Jonathan Woithe" <jwoithe@just42.net>,
"Michał Kępień" <kernel@kempniu.pl>,
"Rainer Koenig" <Rainer.Koenig@ts.fujitsu.com>,
"Jan-Marek Glogowski" <glogow@fbihome.de>
Subject: [PATCH v4 0/2] drm/i915/opregion: proper handling of DIDL and CADL
Date: Wed, 29 Jun 2016 18:36:40 +0300 [thread overview]
Message-ID: <cover.1467214151.git.jani.nikula@intel.com> (raw)
This is v4 of [1]. The first three have already been pushed to
drm-intel-next-queued. The only change here is the atomic commit.
Review and testing would be much appreciated to move this forward. For
testing, I've pushed this to opregion-didl-v4 branch of my repo at [2].
Maarten, please check the hunk touching the atomic code in patch 2.
BR,
Jani.
[1] http://mid.gmane.org/cover.1465810007.git.jani.nikula@intel.com
[2] https://cgit.freedesktop.org/~jani/drm/
Jani Nikula (2):
drm/i915: make i915 the source of acpi device ids for _DOD
drm/i915/opregion: update cadl based on actually active outputs
drivers/gpu/drm/i915/i915_drv.h | 2 +
drivers/gpu/drm/i915/intel_display.c | 4 +
drivers/gpu/drm/i915/intel_drv.h | 3 +
drivers/gpu/drm/i915/intel_opregion.c | 155 +++++++++++++---------------------
4 files changed, 69 insertions(+), 95 deletions(-)
--
2.1.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-06-29 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 15:36 Jani Nikula [this message]
2016-06-29 15:36 ` [PATCH v4 1/2] drm/i915: make i915 the source of acpi device ids for _DOD Jani Nikula
2016-06-29 15:36 ` [PATCH v4 2/2] drm/i915/opregion: update cadl based on actually active outputs Jani Nikula
2016-07-04 5:13 ` Maarten Lankhorst
2016-06-29 16:23 ` ✗ Ro.CI.BAT: failure for drm/i915/opregion: proper handling of DIDL and CADL (rev4) Patchwork
2016-06-29 17:01 ` [PATCH v4 0/2] drm/i915/opregion: proper handling of DIDL and CADL Peter Wu
2016-06-30 9:19 ` Rainer Koenig
2016-07-01 12:12 ` Rainer Koenig
2016-07-01 13:51 ` Jani Nikula
2016-07-12 10:23 ` Maarten Lankhorst
-- strict thread matches above, loose matches on Subject: below --
2016-08-15 11:24 Marcos Paulo de Souza
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=cover.1467214151.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=Rainer.Koenig@ts.fujitsu.com \
--cc=glogow@fbihome.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jwoithe@just42.net \
--cc=kernel@kempniu.pl \
--cc=maarten.lankhorst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox