From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, Peter Wu <peter@lekensteyn.nl>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: jani.nikula@intel.com
Subject: [PATCH v2 0/5] drm/i915/opregion: proper handling of DIDL and CADL
Date: Mon, 13 Jun 2016 12:30:04 +0300 [thread overview]
Message-ID: <cover.1465810007.git.jani.nikula@intel.com> (raw)
This is v2 of [1].
Peter, sorry it took me so long to get back to this. Please confirm your
reviewed-and-tested-by on the series.
Maarten, I'm not confident patch 5/5 is the best way to do this. Any
suggestions?
BR,
Jani.
[1] http://mid.gmane.org/cover.1458731538.git.jani.nikula@intel.com
Jani Nikula (5):
drm/i915/opregion: add acpi defines from the spec
drm/i915/opregion: abstract acpi display type getter for a connector
drm/i915/opregion: handle missing connector types for acpi display
types
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 | 2 +
drivers/gpu/drm/i915/intel_drv.h | 3 +
drivers/gpu/drm/i915/intel_opregion.c | 235 +++++++++++++++++-----------------
4 files changed, 126 insertions(+), 116 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-13 9:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 9:30 Jani Nikula [this message]
2016-06-13 9:30 ` [PATCH v2 1/5] drm/i915/opregion: add acpi defines from the spec Jani Nikula
2016-06-13 9:30 ` [PATCH v2 2/5] drm/i915/opregion: abstract acpi display type getter for a connector Jani Nikula
2016-06-13 9:30 ` [PATCH v2 3/5] drm/i915/opregion: handle missing connector types for acpi display types Jani Nikula
2016-06-29 14:53 ` Jani Nikula
2016-06-13 9:30 ` [PATCH v2 4/5] drm/i915: make i915 the source of acpi device ids for _DOD Jani Nikula
2016-06-13 9:30 ` [PATCH v2 5/5] drm/i915/opregion: update cadl based on actually active outputs Jani Nikula
2016-06-13 9:57 ` kbuild test robot
2016-06-13 10:00 ` [PATCH v3] " Jani Nikula
2016-06-13 10:21 ` Maarten Lankhorst
2016-06-13 10:25 ` [PATCH v2 5/5] " kbuild test robot
2016-06-13 9:43 ` ✗ Ro.CI.BAT: failure for drm/i915/opregion: proper handling of DIDL and CADL (rev2) Patchwork
2016-06-13 10:29 ` ✗ Ro.CI.BAT: failure for drm/i915/opregion: proper handling of DIDL and CADL (rev3) Patchwork
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.1465810007.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=peter@lekensteyn.nl \
/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