{"push_id":2664602770,"size":35,"distinct_size":35,"ref":"refs/heads/mirror/master","head":"1cfea546b10c8fec218973c3f3c39ff797a3e50c","before":"27db64f65f1be2f2ee741a1bf20d8d13d62c167f","commits":[{"sha":"069035c5db3459b9b5f12caf3bffed9a863fa5c4","author":{"name":"Oleksandr Andrushchenko","email":"816c9fea1b19d153023198fc1cd1053f97fb2e05@epam.com"},"message":"drm: Fix possible race conditions while unplugging DRM device\n\nWhen unplugging a hotpluggable DRM device we first unregister it\nwith drm_dev_unregister and then set drm_device.unplugged flag which\nis used to mark device critical sections with drm_dev_enter()/\ndrm_dev_exit() preventing access to device resources that are not\navailable after the device is gone.\nBut drm_dev_unregister may lead to hotplug uevent(s) fired to\nuser-space on card and/or connector removal, thus making it possible\nfor user-space to try accessing a disconnected device.\n\nFix this by first making sure device is properly marked as\ndisconnected and only then unregister it.\n\nFixes: bee330f3d672 (\"drm: Use srcu to protect drm_device.unplugged\")\n\nSigned-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>\nReported-by: Andrii Chepurnyi <andrii_chepurnyi@epam.com>\nCc: \"Noralf Trønnes\" <noralf@tronnes.org>\nReviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nLink: https://patchwork.freedesktop.org/patch/msgid/20180522141304.18646-1-andr2000@gmail.com","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/069035c5db3459b9b5f12caf3bffed9a863fa5c4"},{"sha":"889ad63d41eea20184b0483e7e585e5b20fb6cfe","author":{"name":"Jeremy Cline","email":"f648af476d5297108517aa3643c2c45a04900eaa@redhat.com"},"message":"drm/qxl: Call qxl_bo_unref outside atomic context\n\n\"qxl_bo_unref\" may sleep, but calling \"qxl_release_map\" causes\n\"preempt_disable()\" to be called and \"preempt_enable()\" isn't called\nuntil \"qxl_release_unmap\" is used. Move the call to \"qxl_bo_unref\" out\nfrom in between the two to avoid sleeping from an atomic context.\n\nThis issue can be demonstrated on a kernel with CONFIG_LOCKDEP=y by\ncreating a VM using QXL, using a desktop environment using Xorg, then\nmoving the cursor on or off a window.\n\nBugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1571128\nFixes: 9428088c90b6 (\"drm/qxl: reapply cursor after resetting primary\")\nCc: stable@vger.kernel.org\nSigned-off-by: Jeremy Cline <jcline@redhat.com>\nLink: http://patchwork.freedesktop.org/patch/msgid/20180601200532.13619-1-jcline@redhat.com\nSigned-off-by: Gerd Hoffmann <kraxel@redhat.com>","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/889ad63d41eea20184b0483e7e585e5b20fb6cfe"},{"sha":"8efaac07d7e6694f39521f9fb8a5c848b712ecee","author":{"name":"Andrzej Hajda","email":"dcc2b772defa18622a340d324a717fd6b8ee2807@samsung.com"},"message":"drm/bridge/sii8620: simplify hardware reset procedure\n\nThere is no need to flip reset pin twice. Also delays can be changed to\nvalues present in vendor's code.\n\nSigned-off-by: Andrzej Hajda <a.hajda@samsung.com>\nTested-by: Marek Szyprowski <m.szyprowski@samsung.com>\nReviewed-by: Maciej Purski <m.purski@samsung.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/20180608060457.18357-1-a.hajda@samsung.com","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/8efaac07d7e6694f39521f9fb8a5c848b712ecee"},{"sha":"8e627a1b1ce8feb3e1da4428b71b9b4905f04888","author":{"name":"Andrzej Hajda","email":"dcc2b772defa18622a340d324a717fd6b8ee2807@samsung.com"},"message":"drm/bridge/sii8620: fix loops in EDID fetch logic\n\nFunction should constantly check if cable is connected and finish\nin finite time.\n\nSigned-off-by: Andrzej Hajda <a.hajda@samsung.com>\nTested-by: Marek Szyprowski <m.szyprowski@samsung.com>\nReviewed-by: Maciej Purski <m.purski@samsung.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/20180115173357.31067-4-a.hajda@samsung.com","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/8e627a1b1ce8feb3e1da4428b71b9b4905f04888"},{"sha":"ecba7cfa3afbe489288f2c819158b7402afd7ee9","author":{"name":"Maciej Purski","email":"a73d4b26f107cccd724583fa21e5e9b592a8597e@samsung.com"},"message":"drm/bridge/sii8620: fix display modes validation\n\nCurrent implementation of mode_valid() and mode_fixup() callbacks\nhandle packed pixel modes improperly.\n\nFix it by using proper maximum clock values from the documentation.\n\nSigned-off-by: Maciej Purski <m.purski@samsung.com>\nSigned-off-by: Andrzej Hajda <a.hajda@samsung.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/1517568865-25219-1-git-send-email-m.purski@samsung.com","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/ecba7cfa3afbe489288f2c819158b7402afd7ee9"},{"sha":"9378cecb1ce5d618b8aff4d65113ddcf72fc1011","author":{"name":"Maciej Purski","email":"a73d4b26f107cccd724583fa21e5e9b592a8597e@samsung.com"},"message":"drm/bridge/sii8620: fix potential buffer overflow\n\nBuffer overflow error should not occur, as mode_fixup() callback\nfilters pixel clock value and it should never exceed 600000. However,\ncurrent implementation is not obviously safe and relies on\nimplementation of mode_fixup().\n\nMake 'i' variable never reach unsafe value in order to avoid buffer\noverflow error.\n\nReported-by: Dan Carpenter <dan.carpenter@oracle.com>\nFixes: bf1722ca (\"drm/bridge/sii8620: rewrite hdmi start sequence\")\nSigned-off-by: Maciej Purski <m.purski@samsung.com>\nSigned-off-by: Andrzej Hajda <a.hajda@samsung.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/1511341718-6974-1-git-send-email-m.purski@samsung.com","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/9378cecb1ce5d618b8aff4d65113ddcf72fc1011"},{"sha":"bbc05e172fad9affa388be35b78b9e5e5da76648","author":{"name":"Maciej Purski","email":"a73d4b26f107cccd724583fa21e5e9b592a8597e@samsung.com"},"message":"drm/bridge/sii8620: start MHL transmission after HDMI signal detection\n\nThe vendor code waits for infoframe to detect video mode set by source.\nWe do not need to follow this pattern, because video mode information is\nprovided by drm core. As a result most of the infoframe handling\ncode can be removed.\n\nStart transmission immediately after detecting stream on HDMI lines\nin irq_scdt() function without waiting for infoframe interrupt.\n\nSigned-off-by: Maciej Purski <m.purski@samsung.com>\nSigned-off-by: Andrzej Hajda <a.hajda@samsung.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/1511956130-24482-1-git-send-email-m.purski@samsung.com","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/bbc05e172fad9affa388be35b78b9e5e5da76648"},{"sha":"95e8522588c81fdef1b10777a874c4a1fe14bf88","author":{"name":"Maciej Purski","email":"a73d4b26f107cccd724583fa21e5e9b592a8597e@samsung.com"},"message":"drm/bridge/sii8620: remove HSIC initialization\n\nHSIC initialization was taken from the vendor code. HSIC in MHL circuit\nis not connected, so it is not possible to test it. Tests prove that\nwithout HSIC the device works well. Therefore it can be removed.\n\nSigned-off-by: Maciej Purski <m.purski@samsung.com>\nSigned-off-by: Andrzej Hajda <a.hajda@samsung.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/1511968368-30884-1-git-send-email-m.purski@samsung.com","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/95e8522588c81fdef1b10777a874c4a1fe14bf88"},{"sha":"c7d6d511eb56495f065600c90336da0f0fe1b174","author":{"name":"Maciej Purski","email":"a73d4b26f107cccd724583fa21e5e9b592a8597e@samsung.com"},"message":"drm/bridge/sii8620: fix HDMI cable connection to dongle\n\nMHL bridge is usually connected to TV via MHL dongle. Currently plugging\nHDMI cable to dongle is handled improperly.\n\nFix it by splitting connecting of a dongle and a HDMI cable. The driver\nshould now handle unplugging a sink from a dongle and plugging a\ndifferent sink with new edid.\n\nTested on MHL1, MHL2 and MHL3 using various vendors' dongles both in\nDVI and HDMI mode.\n\nSigned-off-by: Maciej Purski <m.purski@samsung.com>\nSigned-off-by: Andrzej Hajda <a.hajda@samsung.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/1516705996-8928-1-git-send-email-m.purski@samsung.com","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/c7d6d511eb56495f065600c90336da0f0fe1b174"},{"sha":"9fcf2b3c1c0276650fea537c71b513d27d929b05","author":{"name":"Stefan Agner","email":"eb0877843acc39f8ef6f7269937dee931c372d23@agner.ch"},"message":"drm/atmel-hlcdc: check stride values in the first plane\n\nThe statement always evaluates to true since the struct fields\nare arrays. This has shown up as a warning when compiling with\nclang:\n  warning: address of array 'desc->layout.xstride' will always\n      evaluate to 'true' [-Wpointer-bool-conversion]\n\nCheck for values in the first plane instead.\n\nFixes: 1a396789f65a (\"drm: add Atmel HLCDC Display Controller support\")\nCc: <stable@vger.kernel.org>\nSigned-off-by: Stefan Agner <stefan@agner.ch>\nSigned-off-by: Boris Brezillon <boris.brezillon@bootlin.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/20180617084826.31885-1-stefan@agner.ch","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/9fcf2b3c1c0276650fea537c71b513d27d929b05"},{"sha":"58b3d02f066e5b1480d80bd308c545526eea3250","author":{"name":"Paul Kocialkowski","email":"9016e9b42ab7c99df1a95addd0a70ded9a86418d@bootlin.com"},"message":"Revert \"drm/sun4i: Handle DRM_BUS_FLAG_PIXDATA_*EDGE\"\n\nThis reverts commit 2c17a4368aad2b88b68e4390c819e226cf320f70.\n\nThe offending commit triggers a run-time fault when accessing the panel\nelement of the sun4i_tcon structure when no such panel is attached.\n\nIt was apparently assumed in said commit that a panel is always used with\nthe TCON. Although it is often the case, this is not always true.\nFor instance a bridge might be used instead of a panel.\n\nThis issue was discovered using an A13-OLinuXino, that uses the TCON\nin RGB mode for a simple DAC-based VGA bridge.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Paul Kocialkowski <paul.kocialkowski@bootlin.com>\nSigned-off-by: Maxime Ripard <maxime.ripard@bootlin.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/20180613081647.31183-1-paul.kocialkowski@bootlin.com","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/58b3d02f066e5b1480d80bd308c545526eea3250"},{"sha":"1264f8325e9b8c004f36f1ae7bacd2a46a7ed771","author":{"name":"Ben Skeggs","email":"d9f27fb07c1e9f131223ad827fa5179f3846c30b@redhat.com"},"message":"drm/nouveau/kms/nv50-: cursors always use core channel vram ctxdma\n\nCtxdmas for cursors from all heads are setup in the core channel, and due\nto us tracking allocated handles per-window, we were failing with -EEXIST\non multiple-head setups trying to allocate duplicate handles.\n\nThe cursor code is hardcoded to use the core channel vram ctxdma already,\nso just skip ctxdma allocation for cursor fbs to fix the issue.\n\nFixes: 5bca1621c07 (\"drm/nouveau/kms/nv50-: move fb ctxdma tracking into windows\")\nReported-by: Adam Borowski <kilobyte@angband.pl>\nSigned-off-by: Ben Skeggs <bskeggs@redhat.com>","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/1264f8325e9b8c004f36f1ae7bacd2a46a7ed771"},{"sha":"7ba33e1c9d1e03f442b161c701d1f811ea13c75e","author":{"name":"Chris Wilson","email":"711c73f64afdce07b7e38039a96d2224209e9a6c@chris-wilson.co.uk"},"message":"drm/i915: Apply batch location restrictions before pinning\n\nWe special case the position of the batch within the GTT to prevent\nnegative self-relocation deltas from underflowing. However, that\nrestriction is being applied after a trial pin of the batch in its\ncurrent position. Thus we are not rejecting an invalid location if the\nbatch has been used before, leading to an assertion if we happen to need\nto rearrange the entire payload. In the worst case, this may cause a GPU\nhang on gen7 or perhaps missing state.\n\nReferences: https://bugs.freedesktop.org/show_bug.cgi?id=105720\nFixes: 2889caa92321 (\"drm/i915: Eliminate lots of iterations over the execobjects array\")\nSigned-off-by: Chris Wilson <chris@chris-wilson.co.uk>\nCc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>\nCc: Martin Peres <martin.peres@linux.intel.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/20180610194325.13467-2-chris@chris-wilson.co.uk\nReviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>\n(cherry picked from commit 746c8f143afad7aaa66c484485fc39888d437a3f)\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/7ba33e1c9d1e03f442b161c701d1f811ea13c75e"},{"sha":"a5bfcdf0e16b33c1690ded31f863466136480ddc","author":{"name":"Chris Wilson","email":"711c73f64afdce07b7e38039a96d2224209e9a6c@chris-wilson.co.uk"},"message":"drm/i915/execlists: Avoid putting the error pointer\n\nOn allocation error, do not jump to the unwind handler that tries to\nfree the error pointer.\n\nReported-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>\nFixes: a89d1f921c15 (\"drm/i915: Split i915_gem_timeline into individual timelines\")\nSigned-off-by: Chris Wilson <chris@chris-wilson.co.uk>\nCc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>\nCc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>\nReviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/20180611153332.14824-1-chris@chris-wilson.co.uk\n(cherry picked from commit 467d35789e5a4f47428b65ef711b30fdabbb0fd4)\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/a5bfcdf0e16b33c1690ded31f863466136480ddc"},{"sha":"541ab84d2b6ea79021d5df0b54d81600334fa2a4","author":{"name":"Ville Syrjälä","email":"cd6e8d405ca90be3a03d5427c5b24fbd2d68dcc4@linux.intel.com"},"message":"drm/i915: Allow DBLSCAN user modes with eDP/LVDS/DSI\n\nWhen encountering a connector with the scaling mode property both\nintel and modesetting ddxs sometimes add tons of DBLSCAN modes\nto the output's mode list. The idea presumably being that since the\noutput will be going through the panel fitter anyway we can pretend\nto use any kind of mode.\n\nSadly that means we can't reject user modes with the DBLSCAN flag\nuntil we know whether we're going to be using the panel's native\nmode or the user mode directly. Doing otherwise means X clients using\nxf86vidmode/xrandr will get a protocol error (and often self\nterminate as a result) when the kernel refuses to use the requested\nmode with the DBLSCAN flag.\n\nTo undo the regression we'll move the DBLSCAN checks into the\nconnector->mode_valid() and encoder->compute_config() hooks.\n\nCc: stable@vger.kernel.org\nCc: Vito Caputo <vcaputo@pengaru.com>\nReported-by: Vito Caputo <vcaputo@pengaru.com>\nFixes: e995ca0b8139 (\"drm/i915: Provide a device level .mode_valid() hook\")\nReferences: https://lkml.org/lkml/2018/5/21/715\nSigned-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/20180524125403.23445-1-ville.syrjala@linux.intel.com\nReviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>\nBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=106804\nTested-by: Arkadiusz Miskiewicz <arekm@maven.pl>\n(cherry picked from commit e4dd27aadd205417a2e9ea9902b698a0252ec3a0)\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/541ab84d2b6ea79021d5df0b54d81600334fa2a4"},{"sha":"4dc055c9cc8b3dac966b54d3cd5cf463a988299b","author":{"name":"Ville Syrjälä","email":"cd6e8d405ca90be3a03d5427c5b24fbd2d68dcc4@linux.intel.com"},"message":"drm/i915: Fix PIPESTAT irq ack on i965/g4x\n\nOn i965/g4x IIR is edge triggered. So in order for IIR to notice that\nthere is still a pending interrupt we have to force and edge in ISR.\nFor the ISR/IIR pipe event bits we can do that by temporarily\nclearing all the PIPESTAT enable bits when we ack the status bits.\nThis will force the ISR pipe event bit low, and it can then go back\nhigh when we restore the PIPESTAT enable bits.\n\nThis avoids the following race:\n1. stat = read(PIPESTAT)\n2. an enabled PIPESTAT status bit goes high\n3. write(PIPESTAT, enable|stat);\n4. write(IIR, PIPE_EVENT)\n\nThe end result is IIR==0 and ISR!=0. This can lead to nasty\nvblank wait/flip_done timeouts if another interrupt source\ndoesn't trick us into looking at the PIPESTAT status bits despite\nthe IIR PIPE_EVENT bit being low.\n\nBefore i965 IIR was level triggered so this problem can't actually\nhappen there. And curiously VLV/CHV went back to the level triggered\nscheme as well. But for simplicity we'll use the same i965/g4x\ncompatible code for all platforms.\n\nCc: stable@vger.kernel.org\nBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=106033\nBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105225\nBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=106030\nSigned-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/20180611200258.27121-1-ville.syrjala@linux.intel.com\nReviewed-by: Chris Wilson <chris@chris-wilson.co.uk>\n(cherry picked from commit 132c27c97cb958f637dc05adc35a61b47779bcd8)\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/4dc055c9cc8b3dac966b54d3cd5cf463a988299b"},{"sha":"1e34f1d36804be1a446212a33ca5397bf0e5acdd","author":{"name":"Ville Syrjälä","email":"cd6e8d405ca90be3a03d5427c5b24fbd2d68dcc4@linux.intel.com"},"message":"drm/i915: Disallow interlaced modes on g4x DP outputs\n\nLooks like interlaced DP output doesn't work on g4x either. Not all\nthat surprising considering we already established that interlaced\nDP output is busted on VLV/CHV.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>\nReviewed-by: Jani Nikula <jani.nikula@intel.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/20180613160553.11664-1-ville.syrjala@linux.intel.com\n(cherry picked from commit 929168c5f3df5d9ea0ef426c33e971157d045eab)\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/1e34f1d36804be1a446212a33ca5397bf0e5acdd"},{"sha":"4dccc4d517481282e84335c7acbfd7a1481004b8","author":{"name":"Ville Syrjälä","email":"cd6e8d405ca90be3a03d5427c5b24fbd2d68dcc4@linux.intel.com"},"message":"drm/i915: Turn off g4x DP port in .post_disable()\n\nWhile Bspec doesn't list a specific sequence for turning off the DP port\non g4x we are getting an underrun if the port is disabled in the\n.disable() hook. Looks like the pipe stops when the port stops, and by\nthat time the plane disable may not have completed yet. Also the plane(s)\nseem to end up in some wonky state when this happens as they also signal\nanother underrun immediately after we turn them back on during the next\nenable sequence.\n\nWe could add a vblank wait in .disable() to avoid wedging the planes,\nbut I assume we're still tripping up the pipe in some way. So it seems\nbetter to me to just follow the ILK+ sequence and turn off the DP port\nin .post_disable() instead. This sequence doesn't seem to suffer from\nthis problem. Could be it was always the intended sequence for DP and\nthe gen4 bspec was just never updated to include it.\n\nOriginally we used the bad sequence even on ilk+, but I changed that\nin commit 08aff3fe26ae (\"drm/i915: Move DP port disable to post_disable\nfor pch platforms\") as it was causing issues on those platforms as well.\nI left out g4x then only because I didn't have the hardware to test it.\nNow that I do it's fairly clear that the ilk+ sequence is also the\nright choice for g4x.\n\nv2: Fix whitespace fail (Jani)\n    Mention the ilk+ commit (Jani)\n\nCc: stable@vger.kernel.org\nSigned-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>\nLink: https://patchwork.freedesktop.org/patch/msgid/20180613160553.11664-2-ville.syrjala@linux.intel.com\nReviewed-by: Jani Nikula <jani.nikula@intel.com>\n(cherry picked from commit 51a9f6dfc00d35f927ecfaf6f0ae8ebaba39b3fe)\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/4dccc4d517481282e84335c7acbfd7a1481004b8"},{"sha":"bc64e05408cafe3668e7460834935ea3f1764f31","author":{"name":"Mika Kuoppala","email":"cd221c71e765d1ce593d15b204fee351fb09fd98@linux.intel.com"},"message":"drm/i915: Fix context ban and hang accounting for client\n\nIf client is smart or lucky enough to create a new context\nafter each hang, our context banning mechanism will never\ncatch up, and as a result of that it will be saved from\nclient banning. This can result in a never ending streak of\ngpu hangs caused by bad or malicious client, preventing\naccess from other legit gpu clients.\n\nFix this by always incrementing per client ban score if\nit hangs in short successions regardless of context ban\nscoring. The exception are non bannable contexts. They remain\ndetached from client ban scoring mechanism.\n\nv2: xchg timestamp, tidyup (Chris)\nv3: comment, bannable & banned together (Chris)\n\nFixes: b083a0870c79 (\"drm/i915: Add per client max context ban limit\")\nCc: Chris Wilson <chris@chris-wilson.co.uk>\nSigned-off-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>\nReviewed-by: Chris Wilson <chris@chris-wilson.co.uk>\nLink: https://patchwork.freedesktop.org/patch/msgid/20180615104429.31477-1-mika.kuoppala@linux.intel.com\n(cherry picked from commit 14921f3cef85b0167a9145e5f29b9dfc3b2a84dc)\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/bc64e05408cafe3668e7460834935ea3f1764f31"},{"sha":"7a3727f385dc64773db1c144f6b15c1e9d4735bb","author":{"name":"Kenneth Graunke","email":"bd2562f754ec92342f93f61c25d731e290a2ffa8@whitecape.org"},"message":"drm/i915: Enable provoking vertex fix on Gen9 systems.\n\nThe SF and clipper units mishandle the provoking vertex in some cases,\nwhich can cause misrendering with shaders that use flat shaded inputs.\n\nThere are chicken bits in 3D_CHICKEN3 (for SF) and FF_SLICE_CHICKEN\n(for the clipper) that work around the issue.  These registers are\nunfortunately not part of the logical context (even the power context),\nand so we must reload them every time we start executing in a context.\n\nBugzilla: https://bugs.freedesktop.org/103047\nSigned-off-by: Kenneth Graunke <kenneth@whitecape.org>\nSigned-off-by: Chris Wilson <chris@chris-wilson.co.uk>\nLink: https://patchwork.freedesktop.org/patch/msgid/20180615190605.16238-1-chris@chris-wilson.co.uk\nReviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>\nCc: stable@vger.kernel.org\n(cherry picked from commit b77422f80337d363eed60c8c48db9cb6e33085c9)\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/linux-sunxi/linux-sunxi/commits/7a3727f385dc64773db1c144f6b15c1e9d4735bb"}]}
{"actor":{"display_login":"amery"}}