summaryrefslogtreecommitdiff
path: root/src/soc/intel/broadwell/chip.c
diff options
context:
space:
mode:
authorYouness Alaoui <youness.alaoui@puri.sm>2018-05-04 15:33:54 -0400
committerMartin Roth <martinroth@google.com>2018-05-08 02:58:56 +0000
commit1f64b01bbe0007f0364d23715ff0aef0a1eec336 (patch)
tree994782b1dd1f9e57cae8a4260dea0989f9973c9d /src/soc/intel/broadwell/chip.c
parent55b183f1126e8f9832f83a1dabc5d0b6cb8efd5c (diff)
downloadcoreboot-1f64b01bbe0007f0364d23715ff0aef0a1eec336.tar.xz
intel/broadwell: If L1 Sub state is disabled, do not set capability
I finally found out why disabling the L1 sub state option did not prevent some NVMe drives from locking up in L1 substate. I expect that the disabled L1 substate initialization that coreboot does is negated because Linux might itself configure it if it finds the capability enabled on the PCIe root port. Removing the capability from the PCIe root port when L1 sub states are disabled in the configuration should fix the problem. This was not tested because it's a difficult issue to reproduce and I do not have the problematic hardware that caused it anymore. Change-Id: I293a650db307e77cee024a43fbfc81e1d8c86265 Signed-off-by: Youness Alaoui <youness.alaoui@puri.sm> Reviewed-on: https://review.coreboot.org/25325 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to 'src/soc/intel/broadwell/chip.c')
0 files changed, 0 insertions, 0 deletions