Searched hist:b4eb76d82a0ea92241f5079874a7aea10c5cc4ae (Results 1 – 3 of 3) sorted by relevance
/linux/drivers/gpu/drm/i915/display/ |
H A D | intel_snps_phy.c | diff b4eb76d82a0ea92241f5079874a7aea10c5cc4ae Wed Feb 23 17:54:21 CET 2022 Matt Roper <matthew.d.roper@intel.com> drm/i915/dg2: Skip output init on PHY calibration failure
If one of our PHYs fails to complete calibration, we should skip the general initialization of the corresponding output. Most likely this is going to happen on outputs that don't actually exist on the board; in theory we should have already decided to skip this output based on the VBT, but we can't always rely on the VBT being accurate.
Cc: Lucas De Marchi <lucas.demarchi@intel.com> Signed-off-by: Matt Roper <matthew.d.roper@intel.com> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20220223165421.3949883-1-matthew.d.roper@intel.com
|
H A D | intel_ddi.c | diff b4eb76d82a0ea92241f5079874a7aea10c5cc4ae Wed Feb 23 17:54:21 CET 2022 Matt Roper <matthew.d.roper@intel.com> drm/i915/dg2: Skip output init on PHY calibration failure
If one of our PHYs fails to complete calibration, we should skip the general initialization of the corresponding output. Most likely this is going to happen on outputs that don't actually exist on the board; in theory we should have already decided to skip this output based on the VBT, but we can't always rely on the VBT being accurate.
Cc: Lucas De Marchi <lucas.demarchi@intel.com> Signed-off-by: Matt Roper <matthew.d.roper@intel.com> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20220223165421.3949883-1-matthew.d.roper@intel.com
|
/linux/drivers/gpu/drm/i915/ |
H A D | i915_drv.h | diff b4eb76d82a0ea92241f5079874a7aea10c5cc4ae Wed Feb 23 17:54:21 CET 2022 Matt Roper <matthew.d.roper@intel.com> drm/i915/dg2: Skip output init on PHY calibration failure
If one of our PHYs fails to complete calibration, we should skip the general initialization of the corresponding output. Most likely this is going to happen on outputs that don't actually exist on the board; in theory we should have already decided to skip this output based on the VBT, but we can't always rely on the VBT being accurate.
Cc: Lucas De Marchi <lucas.demarchi@intel.com> Signed-off-by: Matt Roper <matthew.d.roper@intel.com> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20220223165421.3949883-1-matthew.d.roper@intel.com
|