I think this is in the wrong component, it should be under Components: OS>Kernel>Graphics

#3 thanks. You can also assign this bug to me.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/d4e9f4ed97336568636c7080dc2d15100108e31e

commit d4e9f4ed97336568636c7080dc2d15100108e31e
Author: Jani Nikula <jani.nikula@intel.com>
Date: Mon Feb 26 22:09:28 2018

UPSTREAM: drm/i915/dp: centralize max source rate conditions more

Turn intel_dp_source_supports_hbr2() into a simple helper to query the
pre-filled source rates array, and move the conditions about which
platforms support which rates to the single point of truth in
intel_dp_set_source_rates().

This also reduces the code paths you have to think about in the source
rates initialization in intel_dp_set_source_rates(), making it easier to
grasp.

Cc: Manasi Navare <manasi.d.navare@intel.com>
Reviewed-by: Manasi Navare <manasi.d.navare@intel.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20171009092959.29021-2-jani.nikula@intel.com
(cherry picked from commit fc603ca7f81d729bbec7ced294f25a93113c49f7)

BUG=chromium:811966
TEST=No display regressions on chromeos-4.14.

Change-Id: I9496e8c4a3379ed2c8eda0c0903c6fbf0bfd7321
Signed-off-by: Nathan Ciobanu <nathan.d.ciobanu@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/919385
Tested-by: Casey G Bowman <casey.g.bowman@intel.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/d4e9f4ed97336568636c7080dc2d15100108e31e/drivers/gpu/drm/i915/intel_dp.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/a6ab48e24bcae6bdc4baa45593f9ca1af1d25181

commit a6ab48e24bcae6bdc4baa45593f9ca1af1d25181
Author: Lucas De Marchi <lucas.demarchi@intel.com>
Date: Mon Feb 26 22:09:30 2018

FROMGIT: drm/i915/cnl: apply Display WA #1178 to fix type C dongles

Display WA #1178 is meant to fix Aux channel voltage swing too low with
some type C dongles. Although it is for type C, HW engineers reported
that it can be applied to all external ports even if they are not going
to type C.

For CNL we apply the workaround every time Aux B, C and D are powering
up since they will lose the configuration when powered down.

v2: Use common tag for WA

Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Arthur J Runyan <arthur.j.runyan@intel.com>
Cc: Ville Syrjl <ville.syrjala@linux.intel.com>
Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20171128220553.22435-1-lucas.demarchi@intel.com
(cherry picked from commit ddd39e4b3f8fb9b69c4dd41019cbe30b049af5ed
git://anongit.freedesktop.org/drm-intel drm-intel-next-queued)

BUG=chromium:811966
TEST=No display regressions on chromeos-4.14.

Change-Id: I56b9580b726d4738bed12c9b1037feae2229858a
Signed-off-by: Nathan Ciobanu <nathan.d.ciobanu@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/919386
Tested-by: Casey G Bowman <casey.g.bowman@intel.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/a6ab48e24bcae6bdc4baa45593f9ca1af1d25181/drivers/gpu/drm/i915/i915_reg.h
[modify] https://crrev.com/a6ab48e24bcae6bdc4baa45593f9ca1af1d25181/drivers/gpu/drm/i915/intel_runtime_pm.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/9f8a1e074550322c82a6501e656f75db61ca9c22

commit 9f8a1e074550322c82a6501e656f75db61ca9c22
Author: Jani Nikula <jani.nikula@intel.com>
Date: Mon Feb 26 22:09:33 2018

UPSTREAM: drm/i915/bios: add DP max link rate to VBT child device struct

Update VBT defs to reflect revision 216. While at it, default the
expected child device struct size to sizeof the size rather than a
hardcoded value.

v2: Fix bit order (David)

Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180118153310.32437-1-jani.nikula@intel.com
(cherry picked from commit c4fb60b9aba9f939d3f8575df23fd8d5958ec6ed)
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
(cherry picked from commit 6dd3104e78943685d5183efe883d83a5f2361bf1)

BUG=chromium:811966
TEST=No display regressions on chromeos-4.14.

Change-Id: Ie134522c71913b9b46d9d818356acf4b9f91e535
Signed-off-by: Nathan Ciobanu <nathan.d.ciobanu@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/919387
Tested-by: Casey G Bowman <casey.g.bowman@intel.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/9f8a1e074550322c82a6501e656f75db61ca9c22/drivers/gpu/drm/i915/intel_bios.c
[modify] https://crrev.com/9f8a1e074550322c82a6501e656f75db61ca9c22/drivers/gpu/drm/i915/intel_vbt_defs.h

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/b680d0919cdb01cbbab4c2246c63562222ce0490

commit b680d0919cdb01cbbab4c2246c63562222ce0490
Author: Rodrigo Vivi <rodrigo.vivi@intel.com>
Date: Mon Feb 26 22:09:35 2018

FROMGIT: drm/i915/cnl: Fix aux selection for WA 1178

Current code always select _CNL_AUX_ANAOVRD1_B
register regardless the pw in use.

CNL_DISP_PW_AUX_B = 9
CNL_DISP_PW_AUX_C = 10
CNL_DISP_PW_AUX_D = 11

And for pick we want

B = 0
C = 1
D = 2

Fixes: ddd39e4b3f8f ("drm/i915/cnl: apply Display WA #1178 to fix type C dongles")
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Acked-by: Lucas De Marchi <lucas.demarchi@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180123215245.24026-1-rodrigo.vivi@intel.com
(cherry picked from commit c559c2a071ff01a3b8b9ce38d3b09d3f403cff10
git://anongit.freedesktop.org/drm-intel drm-intel-next-queued)

BUG=chromium:811966
TEST=No display regressions on chromeos-4.14.

Change-Id: I3260683301fe0f0676d5fb57a9c4b8fa4ee24b54
Signed-off-by: Nathan Ciobanu <nathan.d.ciobanu@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/919388
Tested-by: Casey G Bowman <casey.g.bowman@intel.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/b680d0919cdb01cbbab4c2246c63562222ce0490/drivers/gpu/drm/i915/i915_reg.h

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/3035e740d024875615c0b845a284291bb59bae11

commit 3035e740d024875615c0b845a284291bb59bae11
Author: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Date: Mon Feb 26 22:09:37 2018

BACKPORT: Revert "drm/i915: mark all device info struct with __initconst"

This reverts commit 5b54eddd3920e9f6f1a6d972454baf350cbae77e.

 Conflicts:
	drivers/gpu/drm/i915/i915_pci.c

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104805
Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Fixes: 5b54eddd3920 ("drm/i915: mark all device info struct with __initconst")
Link: https://patchwork.freedesktop.org/patch/msgid/20180129083346.29173-1-lionel.g.landwerlin@intel.com
(cherry picked from commit 5db47e37b38755c5e26e6b8fbc1a32ce73495940)

Conflicts:
	Context delta on:
	drivers/gpu/drm/i915/i915_pci.c

BUG=chromium:811966
TEST=No display regressions on chromeos-4.14.

Change-Id: I9513d30d1fd30238a4c7ad21ea8424f85c8a5e5d
Signed-off-by: Nathan Ciobanu <nathan.d.ciobanu@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/919389
Tested-by: Casey G Bowman <casey.g.bowman@intel.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/3035e740d024875615c0b845a284291bb59bae11/drivers/gpu/drm/i915/i915_pci.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/48ff8fd086130699fe0fbfb45b467126888c0670

commit 48ff8fd086130699fe0fbfb45b467126888c0670
Author: Rodrigo Vivi <rodrigo.vivi@intel.com>
Date: Mon Feb 26 22:09:40 2018

BACKPORT: FROMGIT: drm/i915/cnl: Add Cannonlake PCI IDs for another SKU.

The only difference is that this SKUs has the full
Port A/E split named as Port F.

But since SKUs differences don't matter on the platform
definition group and ids, let's merge all off them together.

v2: Really include the PCI IDs to the picidlist[];
v3: Add the PCI Id for another SKU (Anusha).
v4: Update IDs, really include to pciidlists again.
v5: Unify all GT2 IDs.
v6: Unify in a way that we don't break early-quirks.c
v7: Remove GT reference since it doesn't matter here (Paulo)
    Also move IS_CNL_WITH_PORT_F macro to this patch to
    make it easier for review this part and also to get
    used sooner.
v8: Rebased on top of commit 5db47e37b387 ("Revert "drm/i915:
mark all device info struct with __initconst"")

Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Signed-off-by: Anusha Srivatsa <anusha.srivatsa@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180129232223.766-1-rodrigo.vivi@intel.com
(cherry picked from commit 3f43031b169361fefe032c13ebf644d17f3d76d6
git://anongit.freedesktop.org/drm-intel drm-intel-next-queued)

Conflicts:
	Context delta on:
	drivers/gpu/drm/i915/i915_drv.h

BUG=chromium:811966
TEST=No display regressions on chromeos-4.14.

Change-Id: I50c9047f7b4bf1e6e67e82be0fc38b249ec98c4f
Signed-off-by: Nathan Ciobanu <nathan.d.ciobanu@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/919390
Tested-by: Casey G Bowman <casey.g.bowman@intel.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/48ff8fd086130699fe0fbfb45b467126888c0670/include/drm/i915_pciids.h
[modify] https://crrev.com/48ff8fd086130699fe0fbfb45b467126888c0670/drivers/gpu/drm/i915/i915_drv.h
[modify] https://crrev.com/48ff8fd086130699fe0fbfb45b467126888c0670/drivers/gpu/drm/i915/i915_pci.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/b7c4425640264a688e290fa6eab4dff1dc578ee1

commit b7c4425640264a688e290fa6eab4dff1dc578ee1
Author: Rodrigo Vivi <rodrigo.vivi@intel.com>
Date: Mon Feb 26 22:09:42 2018

BACKPORT: FROMGIT: drm/i915/cnl: Fix DP max rate for Cannonlake with port F.

On CNL SKUs that uses port F,  max DP rate is 8.1G for all
ports when we have the elevated voltage (higher than 0.85V).

v2: Make commit message more generic.
v3: Move conditions to a helper to get easier to read. (Ville).
v4: Add a mention to the numerical voltage on commit
    message per Manasi request.
v5: Thanks CI! "error: control reaches end of non-void function"

Cc: Ville Syrjl <ville.syrjala@linux.intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Manasi Navare <manasi.d.navare@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Reviewed-by: Manasi Navare <manasi.d.navare@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180129232223.766-10-rodrigo.vivi@intel.com
(cherry picked from commit 53ddb3cdb063d7be74aa22ed831cad8aa5ee0863)

Conflicts:
	Context delta on:
	drivers/gpu/drm/i915/intel_dp.c

BUG=chromium:811966
TEST=No display regressions on chromeos-4.14.

Change-Id: I91c971fbdbfe7c46956816173cc36a6122ba3c14
Signed-off-by: Nathan Ciobanu <nathan.d.ciobanu@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/919391
Tested-by: Casey G Bowman <casey.g.bowman@intel.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/b7c4425640264a688e290fa6eab4dff1dc578ee1/drivers/gpu/drm/i915/intel_dp.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/32b56df2aeb9cb28d1a4e19b8e26dbf0533165d6

commit 32b56df2aeb9cb28d1a4e19b8e26dbf0533165d6
Author: Jani Nikula <jani.nikula@intel.com>
Date: Mon Feb 26 22:09:45 2018

FROMGIT: drm/i915/dp: abstract rate array length limiting

This will be useful later on. Also move the functions around to not need
forward declarations in subsequent patches. No functional changes.

Cc: Ville Syrjl <ville.syrjala@linux.intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Reviewed-by: Ville Syrjl <ville.syrjala@linux.intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/40f37f08cad33234cd86337d39e823ac6e55805f.1517482774.git.jani.nikula@intel.com
(cherry picked from commit 10ebb736960cd90eeec7239da2c2b3e8c8a24ef6
git://anongit.freedesktop.org/drm-intel drm-intel-next-queued)

BUG=chromium:811966
TEST=No display regressions on chromeos-4.14.

Change-Id: I151059ef52530e10c4ec839b317afe1cc1f291c5
Signed-off-by: Nathan Ciobanu <nathan.d.ciobanu@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/919392
Tested-by: Casey G Bowman <casey.g.bowman@intel.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/32b56df2aeb9cb28d1a4e19b8e26dbf0533165d6/drivers/gpu/drm/i915/intel_dp.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/7a890ce5dc92162de5e51739afb0a6cb69dee02e

commit 7a890ce5dc92162de5e51739afb0a6cb69dee02e
Author: Jani Nikula <jani.nikula@intel.com>
Date: Mon Feb 26 22:09:47 2018

FROMGIT: drm/i915/dp: clean up source rate limiting for cnl

Make the limiting rate based instead of messing with the array size.

Cc: Ville Syrjl <ville.syrjala@linux.intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Reviewed-by: Ville Syrjl <ville.syrjala@linux.intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/cb03b9419191a7d6359bf371aacb2d3725c746de.1517482774.git.jani.nikula@intel.com
(cherry picked from commit 4ba285d4154ab587cc00bf9bd04bb8c7b19b595a
git://anongit.freedesktop.org/drm-intel drm-intel-next-queued)

BUG=chromium:811966
TEST=No display regressions on chromeos-4.14.

Change-Id: Ia2800fd73a0b08ff0472a02eee51b2e611eff8cb
Signed-off-by: Nathan Ciobanu <nathan.d.ciobanu@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/919393
Tested-by: Casey G Bowman <casey.g.bowman@intel.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/7a890ce5dc92162de5e51739afb0a6cb69dee02e/drivers/gpu/drm/i915/intel_dp.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/67d0b98cd468911b7f3c657b273a92ef4ae8512e

commit 67d0b98cd468911b7f3c657b273a92ef4ae8512e
Author: Jani Nikula <jani.nikula@intel.com>
Date: Mon Feb 26 22:09:50 2018

FROMGIT: drm/i915/dp: limit DP link rate based on VBT on CNL+

We have the max DP link rate info available in VBT since BDB version
216, included in child device config since commit c4fb60b9aba9
("drm/i915/bios: add DP max link rate to VBT child device
struct"). Parse it and use it.

Cc: Ville Syrjl <ville.syrjala@linux.intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Reviewed-by: Ville Syrjl <ville.syrjala@linux.intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/a8b1364d1f2394fba3062b6ad11b474744ea4366.1517482774.git.jani.nikula@intel.com
(cherry picked from commit 99b91bda84060bac061d1649fad0e3bddcf67ce6
git://anongit.freedesktop.org/drm-intel drm-intel-next-queued)

BUG=chromium:811966
TEST=No display regressions on chromeos-4.14.

Change-Id: I45ab08c2409385bc2550ce80371e09429a83d740
Signed-off-by: Nathan Ciobanu <nathan.d.ciobanu@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/919394
Tested-by: Casey G Bowman <casey.g.bowman@intel.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/67d0b98cd468911b7f3c657b273a92ef4ae8512e/drivers/gpu/drm/i915/intel_bios.c
[modify] https://crrev.com/67d0b98cd468911b7f3c657b273a92ef4ae8512e/drivers/gpu/drm/i915/i915_drv.h
[modify] https://crrev.com/67d0b98cd468911b7f3c657b273a92ef4ae8512e/drivers/gpu/drm/i915/intel_vbt_defs.h
[modify] https://crrev.com/67d0b98cd468911b7f3c657b273a92ef4ae8512e/drivers/gpu/drm/i915/intel_dp.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/69b080d1d9575d53d6b12557b2694f40e2894c89

commit 69b080d1d9575d53d6b12557b2694f40e2894c89
Author: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Date: Mon Feb 26 22:09:25 2018

UPSTREAM: drm/i915: Use fallback forcewake if primary ack missing

There is a possibility on gen9 hardware to miss the forcewake ack
message. The recommended workaround is to use another free
bit and toggle it until original bit is successfully acknowledged.

Some future gen9 revs might or might not fix the underlying issue but
using fallback forcewake bit dance can be considered as harmless:
without the ack timeout we never reach the fallback bit forcewake.
Thus as of now we adopt a blanket approach for all gen9 and leave
the bypassing the fallback bit approach for future patches if
corresponding hw revisions do appear.

Commit 83e3337204b2 ("drm/i915: Increase maximum polling time to 50ms
for forcewake request/clear ack") did increase the forcewake timeout.
If the issue was a delayed ack, future work could include finding
a suitable timeout value both for primary ack and reserve toggle
to reduce the worst case latency.

v2: use bit 15, naming, comment (Chris), only wait fallback ack
v3: fix return on fallback, backoff after fallback write (Chris)
v4: udelay on first pass, grammar (Chris)
v4: s/reserve/fallback

References: HSDES #1604254524
References: https://bugs.freedesktop.org/show_bug.cgi?id=102051
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Sagar Arun Kamble <sagar.a.kamble@intel.com>
Signed-off-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Link: https://patchwork.freedesktop.org/patch/msgid/20171102094836.2506-1-mika.kuoppala@linux.intel.com
(cherry picked from commit 7130630323c562597191653560963e61c5bd0f57)

BUG=chromium:811966
TEST=No display regressions on chromeos-4.14.

Change-Id: Ic4e303b229a02e12179ba63bf7db141ad03034d3
Signed-off-by: Nathan Ciobanu <nathan.d.ciobanu@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/919686
Tested-by: Casey G Bowman <casey.g.bowman@intel.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/69b080d1d9575d53d6b12557b2694f40e2894c89/drivers/gpu/drm/i915/i915_reg.h
[modify] https://crrev.com/69b080d1d9575d53d6b12557b2694f40e2894c89/drivers/gpu/drm/i915/intel_uncore.c

Working on a fifth patch series tracking upstream CNL developments as well as a series of PSR fixes.