<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/gpu/drm/i915/Makefile, branch linux-5.0.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.0.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.0.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2018-12-04T12:23:19Z</updated>
<entry>
<title>drm/i915/selftests: Add tests for GT and engine workaround verification</title>
<updated>2018-12-04T12:23:19Z</updated>
<author>
<name>Tvrtko Ursulin</name>
</author>
<published>2018-12-03T12:50:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=28d6ccce73bec983d5038f5cee1064957816cf44'/>
<id>urn:sha1:28d6ccce73bec983d5038f5cee1064957816cf44</id>
<content type='text'>
Two simple selftests which test that both GT and engine workarounds are
not lost after either a full GPU reset, or after the per-engine ones.

(Including checks that one engine reset is not affecting workarounds not
belonging to itself.)

v2:
 * Rebase for series refactoring.
 * Add spinner for actual engine reset!
 * Add idle reset test as well. (Chris Wilson)
 * Share existing global_reset_lock. (Chris Wilson)

v3:
 * intel_engine_verify_workarounds can be static.
 * API rename. (Chris Wilson)
 * Move global reset lock out of the loop. (Chris Wilson)

v4:
 * Add missing rpm puts. (Chris Wilson)

Signed-off-by: Tvrtko Ursulin &lt;tvrtko.ursulin@intel.com&gt;
Reviewed-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20181203125014.3219-5-tvrtko.ursulin@linux.intel.com
</content>
</entry>
<entry>
<title>drm/i915/selftests: Extract spinner code</title>
<updated>2018-11-30T15:09:00Z</updated>
<author>
<name>Tvrtko Ursulin</name>
</author>
<published>2018-11-30T08:02:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8d2f6e2f2721097549dded41aa6e1c1a4e8e12ee'/>
<id>urn:sha1:8d2f6e2f2721097549dded41aa6e1c1a4e8e12ee</id>
<content type='text'>
Pull out spinner code to a standalone file to enable it to be shortly used
by other and new test cases.

Plain code movement - no functional changes.

Signed-off-by: Tvrtko Ursulin &lt;tvrtko.ursulin@intel.com&gt;
Reviewed-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20181130080254.15383-1-tvrtko.ursulin@linux.intel.com
</content>
</entry>
<entry>
<title>drm/i915/dsc: Define &amp; Compute VESA DSC params</title>
<updated>2018-11-29T20:22:14Z</updated>
<author>
<name>Gaurav K Singh</name>
</author>
<published>2018-11-29T19:38:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=168243c1801065f7e3a6afb6d5bd49ae5bdf1871'/>
<id>urn:sha1:168243c1801065f7e3a6afb6d5bd49ae5bdf1871</id>
<content type='text'>
This patches does the following:

1. This patch defines all the DSC parameters as per the VESA
DSC specification. These are stored in the encoder and used
to compute the PPS parameters to be sent to the Sink.
2. Compute all the DSC parameters which are derived from DSC
state of intel_crtc_state.
3. Compute all parameters that are VESA DSC specific

This computation happens in the atomic check phase during
compute_config() to validate if display stream compression
can be enabled for the requested mode.

v8 (From Manasi):
* DEBUG_KMS instead of DRM_ERROR for user triggerable
errors (Ville)
v7: (From Manasi)
* Dont use signed int for rc_range_params (Manasi)
* Mask the range_bpg_offset to use only 6 bits
* Add SPDX identifier (Chris Wilson)
v6 (From Manasi):
* Add a check for line_buf_depth return value (Anusha)
* Remove DRM DSC constants to different patch (Manasi)
v5 (From Manasi):
* Add logic to limit the max line buf depth for DSC 1.1 to 13
as per DSC 1.1 spec
* Fix dim checkpatch warnings/checks

v4 (From Gaurav):
* Rebase on latest drm tip
* rename variable name(Manasi)
* Populate linebuf_depth variable(Manasi)

v3 (From Gaurav):
* Rebase my previous patches on top of Manasi's latest patch
series
* Using &gt;&gt;n rather than /2^n (Manasi)
* Change the commit message to explain what the patch is doing(Gaurav)

Fixed review comments from Ville:
* Don't use macro TWOS_COMPLEMENT
* Mention in comment about the source of RC params
* Return directly from case statements
* Using single asssignment for assigning rc_range_params
* Using &lt;&lt;n rather than *2^n and removing the comments
about the fixed point numbers

v2 (From Manasi):
* Update logic for minor version to consider the dpcd value
and what supported by the HW platform
* Use DRM DSC config struct instead of intel_dp struct
* Move the DSC constants to DRM DSC header file
* Use u16, u8 where bigger data types not needed
* * Compute the DSC parameters as part of DSC compute config
since the computation can fail (Manasi)

Cc: Jani Nikula &lt;jani.nikula@linux.intel.com&gt;
Cc: Ville Syrjala &lt;ville.syrjala@linux.intel.com&gt;
Cc: Anusha Srivatsa &lt;anusha.srivatsa@intel.com&gt;
Cc: Gaurav K Singh &lt;gaurav.k.singh@intel.com&gt;
Signed-off-by: Gaurav K Singh &lt;gaurav.k.singh@intel.com&gt;
Signed-off-by: Manasi Navare &lt;manasi.d.navare@intel.com&gt;
Co-developed-by: Manasi Navare &lt;manasi.d.navare@intel.com&gt;
Reviewed-by: Anusha Srivatsa &lt;anusha.srivatsa@intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20181129193827.7914-1-manasi.d.navare@intel.com
</content>
</entry>
<entry>
<title>Merge drm/drm-next into drm-intel-next-queued</title>
<updated>2018-11-20T11:14:08Z</updated>
<author>
<name>Jani Nikula</name>
</author>
<published>2018-11-20T11:14:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2ac5e38ea4203852d6e99edd3cf11f044b0a409f'/>
<id>urn:sha1:2ac5e38ea4203852d6e99edd3cf11f044b0a409f</id>
<content type='text'>
Pull in v4.20-rc3 via drm-next.

Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/i915/cnl+: Move the combo PHY init/uninit code to a new file</title>
<updated>2018-11-08T17:27:00Z</updated>
<author>
<name>Imre Deak</name>
</author>
<published>2018-11-06T16:06:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c45198b163fb5342290144b770a905f0d83821ad'/>
<id>urn:sha1:c45198b163fb5342290144b770a905f0d83821ad</id>
<content type='text'>
Similarly to the GEN9_LP DPIO PHY code keep the CNL+ combo PHY code in a
separate file.

No functional change.

v2:
- Use SPDX license tag instead of boilerplate. (Rodrigo)
v3:
- Use MIT instead of GPL-2.0 license. (Ville)

Suggested-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Cc: Paulo Zanoni &lt;paulo.r.zanoni@intel.com&gt;
Cc: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Cc: José Roberto de Souza &lt;jose.souza@intel.com&gt;
Cc: Rodrigo Vivi &lt;rodrigo.vivi@intel.com&gt;
Signed-off-by: Imre Deak &lt;imre.deak@intel.com&gt;
Reviewed-by: Rodrigo Vivi &lt;rodrigo.vivi@intel.com&gt;
Reviewed-by: José Roberto de Souza &lt;jose.souza@intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20181106160621.23057-3-imre.deak@intel.com
</content>
</entry>
<entry>
<title>drm/i915/dsi: refactor bitrate calculations in intel_dsi_vbt_init()</title>
<updated>2018-10-18T12:15:27Z</updated>
<author>
<name>Jani Nikula</name>
</author>
<published>2018-10-15T14:27:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2bf3f59daeee6cfed79bd0d292aa9b4eded37c42'/>
<id>urn:sha1:2bf3f59daeee6cfed79bd0d292aa9b4eded37c42</id>
<content type='text'>
Abstract bitrate calculation to a newly resurrected intel_dsi.c file
that will contain common code for VLV and ICL DSI.

No functional changes.

Cc: Madhav Chauhan &lt;madhav.chauhan@intel.com&gt;
Cc: Ville Syrjala &lt;ville.syrjala@linux.intel.com&gt;
Reviewed-by: Madhav Chauhan &lt;madhav.chauhan@intel.com&gt;
Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/100e9721dfdec4f3987549ef24291bafc9cb0517.1539613303.git.jani.nikula@intel.com
</content>
</entry>
<entry>
<title>drm/i915: split out display quirks to a new file</title>
<updated>2018-10-17T07:27:44Z</updated>
<author>
<name>Jani Nikula</name>
</author>
<published>2018-10-16T14:42:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=593a21a04f99fd4f5454fca5f1b92a5950c35f80'/>
<id>urn:sha1:593a21a04f99fd4f5454fca5f1b92a5950c35f80</id>
<content type='text'>
Reduce intel_display.c by splitting out intel_quirks.c. No functional
changes.

Reviewed-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20181016144228.18267-1-jani.nikula@intel.com
</content>
</entry>
<entry>
<title>Makefile: Globally enable VLA warning</title>
<updated>2018-10-11T15:17:50Z</updated>
<author>
<name>Kees Cook</name>
</author>
<published>2018-06-25T22:59:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0bb95f80a38f82884693194ea720e9cca5e12ada'/>
<id>urn:sha1:0bb95f80a38f82884693194ea720e9cca5e12ada</id>
<content type='text'>
Now that Variable Length Arrays (VLAs) have been entirely removed[1]
from the kernel, enable the VLA warning globally. The only exceptions
to this are the KASan an UBSan tests which are explicitly checking that
VLAs trigger their respective tests.

[1] https://lkml.kernel.org/r/CA+55aFzCG-zNmZwX4A2FQpadafLfEzK6CC=qPXydAacU1RqZWA@mail.gmail.com

Cc: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;
Cc: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Cc: David Airlie &lt;airlied@linux.ie&gt;
Cc: linux-kbuild@vger.kernel.org
Cc: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
</content>
</entry>
<entry>
<title>drm/i915: rename intel_modes.c to intel_connector.c</title>
<updated>2018-10-10T12:15:10Z</updated>
<author>
<name>Jani Nikula</name>
</author>
<published>2018-10-10T07:52:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=360fa66ae857e8e5ff97a2e0519b2d87baccebfd'/>
<id>urn:sha1:360fa66ae857e8e5ff97a2e0519b2d87baccebfd</id>
<content type='text'>
The common denominator here seems to be connector more than
modes. Prepare for moving more connector functions to the same place. No
functional changes.

Reviewed-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20181010075205.7713-1-jani.nikula@intel.com
</content>
</entry>
<entry>
<title>drm/i915: Pull scheduling under standalone lock</title>
<updated>2018-10-01T19:34:21Z</updated>
<author>
<name>Chris Wilson</name>
</author>
<published>2018-10-01T14:47:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e2f3496e93be3238de2e2e6bfc83b3a83c084ce5'/>
<id>urn:sha1:e2f3496e93be3238de2e2e6bfc83b3a83c084ce5</id>
<content type='text'>
Currently, the backend scheduling code abuses struct_mutex into order to
have a global lock to manipulate a temporary list (without widespread
allocation) and to protect against list modifications. This is an
extraneous coupling to struct_mutex and further can not extend beyond
the local device.

Pull all the code that needs to be under the one true lock into
i915_scheduler.c, and make it so.

Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Reviewed-by: Tvrtko Ursulin &lt;tvrtko.ursulin@intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20181001144755.7978-2-chris@chris-wilson.co.uk
</content>
</entry>
</feed>
