From: Jani Nikula <jani.nikula@intel.com>
To: Khaled Almahallawy <khaled.almahallawy@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 1/2] drm/i915/dp: Use LINK_QUAL_PATTERN_* Phy test pattern names
Date: Tue, 05 Dec 2023 15:21:25 +0200 [thread overview]
Message-ID: <87y1e823ai.fsf@intel.com> (raw)
In-Reply-To: <20231130213103.214915-1-khaled.almahallawy@intel.com>
On Thu, 30 Nov 2023, Khaled Almahallawy <khaled.almahallawy@intel.com> wrote:
> Starting from DP2.0 specs, DPCD 248h is renamed
> LINK_QUAL_PATTERN_SELECT and it has the same values of registers
> DPCD 10Bh-10Eh.
> Use the PHY pattern names defined for DPCD 10Bh-10Eh in order to add
> CP2520 Pattern 3 (TPS4) phy pattern support in the next
> patch of this series and DP2.1 PHY patterns for future series.
>
> v2: rebase
>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Imre Deak <imre.deak@intel.com>
> Cc: Lee Shawn C <shawn.c.lee@intel.com>
> Signed-off-by: Khaled Almahallawy <khaled.almahallawy@intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 3b2482bf683f..a1e63ab5761b 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -4683,27 +4683,27 @@ static void intel_dp_phy_pattern_update(struct intel_dp *intel_dp,
> u32 pattern_val;
>
> switch (data->phy_pattern) {
> - case DP_PHY_TEST_PATTERN_NONE:
> + case DP_LINK_QUAL_PATTERN_DISABLE:
> drm_dbg_kms(&dev_priv->drm, "Disable Phy Test Pattern\n");
> intel_de_write(dev_priv, DDI_DP_COMP_CTL(pipe), 0x0);
> break;
> - case DP_PHY_TEST_PATTERN_D10_2:
> + case DP_LINK_QUAL_PATTERN_D10_2:
> drm_dbg_kms(&dev_priv->drm, "Set D10.2 Phy Test Pattern\n");
> intel_de_write(dev_priv, DDI_DP_COMP_CTL(pipe),
> DDI_DP_COMP_CTL_ENABLE | DDI_DP_COMP_CTL_D10_2);
> break;
> - case DP_PHY_TEST_PATTERN_ERROR_COUNT:
> + case DP_LINK_QUAL_PATTERN_ERROR_RATE:
> drm_dbg_kms(&dev_priv->drm, "Set Error Count Phy Test Pattern\n");
> intel_de_write(dev_priv, DDI_DP_COMP_CTL(pipe),
> DDI_DP_COMP_CTL_ENABLE |
> DDI_DP_COMP_CTL_SCRAMBLED_0);
> break;
> - case DP_PHY_TEST_PATTERN_PRBS7:
> + case DP_LINK_QUAL_PATTERN_PRBS7:
> drm_dbg_kms(&dev_priv->drm, "Set PRBS7 Phy Test Pattern\n");
> intel_de_write(dev_priv, DDI_DP_COMP_CTL(pipe),
> DDI_DP_COMP_CTL_ENABLE | DDI_DP_COMP_CTL_PRBS7);
> break;
> - case DP_PHY_TEST_PATTERN_80BIT_CUSTOM:
> + case DP_LINK_QUAL_PATTERN_80BIT_CUSTOM:
> /*
> * FIXME: Ideally pattern should come from DPCD 0x250. As
> * current firmware of DPR-100 could not set it, so hardcoding
> @@ -4721,7 +4721,7 @@ static void intel_dp_phy_pattern_update(struct intel_dp *intel_dp,
> DDI_DP_COMP_CTL_ENABLE |
> DDI_DP_COMP_CTL_CUSTOM80);
> break;
> - case DP_PHY_TEST_PATTERN_CP2520:
> + case DP_LINK_QUAL_PATTERN_CP2520_PAT_1:
> /*
> * FIXME: Ideally pattern should come from DPCD 0x24A. As
> * current firmware of DPR-100 could not set it, so hardcoding
--
Jani Nikula, Intel
prev parent reply other threads:[~2023-12-05 13:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 21:31 [Intel-gfx] [PATCH v2 1/2] drm/i915/dp: Use LINK_QUAL_PATTERN_* Phy test pattern names Khaled Almahallawy
2023-11-30 21:31 ` [Intel-gfx] [PATCH v2 2/2] drm/i915/dp: Add TPS4 PHY test pattern support Khaled Almahallawy
2023-12-05 13:37 ` Jani Nikula
2023-12-01 2:37 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/2] drm/i915/dp: Use LINK_QUAL_PATTERN_* Phy test pattern names Patchwork
2023-12-01 2:53 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-12-01 19:47 ` Almahallawy, Khaled
2023-12-04 9:06 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-12-04 12:06 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-12-05 13:21 ` Jani Nikula [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1e823ai.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=khaled.almahallawy@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).