From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/8] drm/i915/dsi: i2c/gpio
Date: Thu, 4 Feb 2016 12:50:48 +0200 [thread overview]
Message-ID: <cover.1454582914.git.jani.nikula@intel.com> (raw)
Sme fixes to i2c/gpio elements in dsi. I think patches 1-4 are needed
for bxt at this time. The remaining patches don't really help, since the
sideband code is vlv/chv specific anyway.
BR,
Jani.
Deepak M (2):
drm/i915: Extend gpio read/write to other cores
drm/i915/dsi: Added the generic gpio sequence support and gpio table
Jani Nikula (5):
drm/i915/dsi: defend gpio table against out of bounds access
drm/i915/dsi: don't pass arbitrary data to sideband
drm/i915/dsi: skip gpio element execution when not supported
drm/i915: put the IOSF port defines in numerical order
drm/i915/vlv: drop unused vlv_gps_core_read/write functions
vkorjani (1):
drm/i915: Adding the parsing logic for the i2c element
drivers/gpu/drm/i915/i915_drv.h | 6 +-
drivers/gpu/drm/i915/i915_reg.h | 13 +-
drivers/gpu/drm/i915/intel_dsi_panel_vbt.c | 669 +++++++++++++++++++++++++++--
drivers/gpu/drm/i915/intel_sideband.c | 23 +-
4 files changed, 641 insertions(+), 70 deletions(-)
--
2.1.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-02-04 10:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 10:50 Jani Nikula [this message]
2016-02-04 10:50 ` [PATCH 1/8] drm/i915/dsi: defend gpio table against out of bounds access Jani Nikula
2016-02-04 15:40 ` Ville Syrjälä
2016-02-04 10:50 ` [PATCH 2/8] drm/i915/dsi: don't pass arbitrary data to sideband Jani Nikula
2016-02-04 15:41 ` Ville Syrjälä
2016-02-04 16:56 ` Jani Nikula
2016-02-04 10:50 ` [PATCH 3/8] drm/i915: Adding the parsing logic for the i2c element Jani Nikula
2016-02-04 15:28 ` Ville Syrjälä
2016-02-04 16:21 ` Jani Nikula
2016-02-04 16:36 ` Ville Syrjälä
2016-02-15 16:48 ` Daniel Vetter
2016-02-04 10:50 ` [PATCH 4/8] drm/i915/dsi: skip gpio element execution when not supported Jani Nikula
2016-02-04 15:36 ` Ville Syrjälä
2016-02-04 16:52 ` [PATCH v2] " Jani Nikula
2016-02-04 17:05 ` Ville Syrjälä
2016-02-04 17:10 ` Jani Nikula
2016-02-04 17:12 ` Jani Nikula
2016-02-04 17:18 ` Ville Syrjälä
2016-02-04 17:22 ` Jani Nikula
2016-02-04 17:48 ` Ville Syrjälä
2016-02-04 17:49 ` Ville Syrjälä
2016-02-04 18:39 ` Jani Nikula
2016-02-04 10:50 ` [PATCH 5/8] drm/i915: put the IOSF port defines in numerical order Jani Nikula
2016-02-04 16:05 ` Ville Syrjälä
2016-02-04 10:50 ` [PATCH 6/8] drm/i915/vlv: drop unused vlv_gps_core_read/write functions Jani Nikula
2016-02-04 16:12 ` Ville Syrjälä
2016-02-04 16:57 ` Jani Nikula
2016-02-04 10:50 ` [PATCH 7/8] drm/i915: Extend gpio read/write to other cores Jani Nikula
2016-02-04 15:39 ` Ville Syrjälä
2016-02-04 16:55 ` [PATCH v5] " Jani Nikula
2016-02-04 17:03 ` Ville Syrjälä
2016-02-04 17:14 ` Jani Nikula
2016-02-04 10:50 ` [PATCH 8/8] drm/i915/dsi: Added the generic gpio sequence support and gpio table Jani Nikula
2016-02-04 17:51 ` Ville Syrjälä
2016-02-04 12:46 ` ✓ Fi.CI.BAT: success for drm/i915/dsi: i2c/gpio Patchwork
2016-02-05 7:31 ` ✗ Fi.CI.BAT: failure for drm/i915/dsi: i2c/gpio (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.1454582914.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).