From: Manasi Navare <manasi.d.navare@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: nidhi1.gupta@intel.com, Animesh Manna <animesh.manna@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v3 8/9] drm/i915/dp: Update the pattern as per request
Date: Fri, 3 Jan 2020 15:51:36 -0800 [thread overview]
Message-ID: <20200103235136.GC2608@intel.com> (raw)
In-Reply-To: <87sgkytdod.fsf@intel.com>
On Thu, Jan 02, 2020 at 11:23:14AM +0200, Jani Nikula wrote:
> On Mon, 30 Dec 2019, Animesh Manna <animesh.manna@intel.com> wrote:
> > As per request from DP phy compliance test few special
> > test pattern need to set by source. Added function
> > to set pattern in DP_COMP_CTL register. It will be
> > called along with other test parameters like vswing,
> > pre-emphasis programming in atomic_commit_tail path.
> >
> > Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_dp.c | 55 +++++++++++++++++++++++++
> > 1 file changed, 55 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> > index cbefda9b6204..7c3f65e5d88b 100644
> > --- a/drivers/gpu/drm/i915/display/intel_dp.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> > @@ -5005,6 +5005,61 @@ static u8 intel_dp_prepare_phytest(struct intel_dp *intel_dp)
> > return DP_TEST_ACK;
> > }
> >
> > +static inline void intel_dp_phy_pattern_update(struct intel_dp *intel_dp)
>
> As a general rule, please only use the inline keyword for static inlines
> in headers. Sometimes, it's useful in small helpers, but usually you
> should just let the compiler decide what gets inlined.
>
> In this case, the inline probably just hides the compiler warning about
> the unused function.
>
> BR,
> Jani.
>
Yes I completely agree with Jani here, please do not use inline
other than some one line helpers in header files.
> > +{
> > + struct drm_i915_private *dev_priv =
> > + to_i915(dp_to_dig_port(intel_dp)->base.base.dev);
> > + struct intel_digital_port *intel_dig_port = dp_to_dig_port(intel_dp);
> > + struct drm_dp_phy_test_params *data =
> > + &intel_dp->compliance.test_data.phytest;
> > + u32 temp;
> > +
> > + switch (data->phy_pattern) {
> > + case DP_PHY_TEST_PATTERN_NONE:
> > + DRM_DEBUG_KMS("Disable Phy Test Pattern\n");
> > + I915_WRITE(DDI_DP_COMP_CTL(intel_dig_port->base.port), 0x0);
> > + break;
> > + case DP_PHY_TEST_PATTERN_D10_2:
> > + DRM_DEBUG_KMS("Set D10.2 Phy Test Pattern\n");
> > + I915_WRITE(DDI_DP_COMP_CTL(intel_dig_port->base.port),
> > + DDI_DP_COMP_CTL_ENABLE | DDI_DP_COMP_CTL_D10_2);
> > + break;
> > + case DP_PHY_TEST_PATTERN_ERROR_COUNT:
> > + DRM_DEBUG_KMS("Set Error Count Phy Test Pattern\n");
> > + I915_WRITE(DDI_DP_COMP_CTL(intel_dig_port->base.port),
> > + DDI_DP_COMP_CTL_ENABLE |
> > + DDI_DP_COMP_CTL_SCRAMBLED_0);
> > + break;
> > + case DP_PHY_TEST_PATTERN_PRBS7:
> > + DRM_DEBUG_KMS("Set PRBS7 Phy Test Pattern\n");
> > + I915_WRITE(DDI_DP_COMP_CTL(intel_dig_port->base.port),
> > + DDI_DP_COMP_CTL_ENABLE | DDI_DP_COMP_CTL_PRBS7);
> > + break;
> > + case DP_PHY_TEST_PATTERN_80BIT_CUSTOM:
> > + DRM_DEBUG_KMS("Set 80Bit Custom Phy Test Pattern\n");
> > + temp = ((data->custom80[0] << 24) | (data->custom80[1] << 16) |
> > + (data->custom80[2] << 8) | (data->custom80[3]));
> > + I915_WRITE(DDI_DP_COMP_PAT(intel_dig_port->base.port, 0), temp);
> > + temp = ((data->custom80[4] << 24) | (data->custom80[5] << 16) |
> > + (data->custom80[6] << 8) | (data->custom80[7]));
> > + I915_WRITE(DDI_DP_COMP_PAT(intel_dig_port->base.port, 1), temp);
> > + temp = ((data->custom80[8] << 8) | data->custom80[9]);
> > + I915_WRITE(DDI_DP_COMP_PAT(intel_dig_port->base.port, 2), temp);
> > + I915_WRITE(DDI_DP_COMP_CTL(intel_dig_port->base.port),
> > + DDI_DP_COMP_CTL_ENABLE | DDI_DP_COMP_CTL_CUSTOM80);
> > + break;
> > + case DP_PHY_TEST_PATTERN_CP2520:
> > + DRM_DEBUG_KMS("Set HBR2 compliance Phy Test Pattern\n");
> > + temp = ((data->hbr2_reset[1] << 8) | data->hbr2_reset[0]);
> > + I915_WRITE(DDI_DP_COMP_CTL(intel_dig_port->base.port),
> > + DDI_DP_COMP_CTL_ENABLE | DDI_DP_COMP_CTL_HBR2 |
> > + temp);
> > + break;
> > + default:
> > + WARN(1, "Invalid Phy Test PAttern\n");
Small nit here, it should be PHY Pattern
Manasi
> > + }
> > +}
> > +
> > static u8 intel_dp_autotest_phy_pattern(struct intel_dp *intel_dp)
> > {
> > u8 test_result = DP_TEST_NAK;
>
> --
> Jani Nikula, Intel Open Source Graphics Center
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Manasi Navare <manasi.d.navare@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: nidhi1.gupta@intel.com, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v3 8/9] drm/i915/dp: Update the pattern as per request
Date: Fri, 3 Jan 2020 15:51:36 -0800 [thread overview]
Message-ID: <20200103235136.GC2608@intel.com> (raw)
In-Reply-To: <87sgkytdod.fsf@intel.com>
On Thu, Jan 02, 2020 at 11:23:14AM +0200, Jani Nikula wrote:
> On Mon, 30 Dec 2019, Animesh Manna <animesh.manna@intel.com> wrote:
> > As per request from DP phy compliance test few special
> > test pattern need to set by source. Added function
> > to set pattern in DP_COMP_CTL register. It will be
> > called along with other test parameters like vswing,
> > pre-emphasis programming in atomic_commit_tail path.
> >
> > Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_dp.c | 55 +++++++++++++++++++++++++
> > 1 file changed, 55 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> > index cbefda9b6204..7c3f65e5d88b 100644
> > --- a/drivers/gpu/drm/i915/display/intel_dp.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> > @@ -5005,6 +5005,61 @@ static u8 intel_dp_prepare_phytest(struct intel_dp *intel_dp)
> > return DP_TEST_ACK;
> > }
> >
> > +static inline void intel_dp_phy_pattern_update(struct intel_dp *intel_dp)
>
> As a general rule, please only use the inline keyword for static inlines
> in headers. Sometimes, it's useful in small helpers, but usually you
> should just let the compiler decide what gets inlined.
>
> In this case, the inline probably just hides the compiler warning about
> the unused function.
>
> BR,
> Jani.
>
Yes I completely agree with Jani here, please do not use inline
other than some one line helpers in header files.
> > +{
> > + struct drm_i915_private *dev_priv =
> > + to_i915(dp_to_dig_port(intel_dp)->base.base.dev);
> > + struct intel_digital_port *intel_dig_port = dp_to_dig_port(intel_dp);
> > + struct drm_dp_phy_test_params *data =
> > + &intel_dp->compliance.test_data.phytest;
> > + u32 temp;
> > +
> > + switch (data->phy_pattern) {
> > + case DP_PHY_TEST_PATTERN_NONE:
> > + DRM_DEBUG_KMS("Disable Phy Test Pattern\n");
> > + I915_WRITE(DDI_DP_COMP_CTL(intel_dig_port->base.port), 0x0);
> > + break;
> > + case DP_PHY_TEST_PATTERN_D10_2:
> > + DRM_DEBUG_KMS("Set D10.2 Phy Test Pattern\n");
> > + I915_WRITE(DDI_DP_COMP_CTL(intel_dig_port->base.port),
> > + DDI_DP_COMP_CTL_ENABLE | DDI_DP_COMP_CTL_D10_2);
> > + break;
> > + case DP_PHY_TEST_PATTERN_ERROR_COUNT:
> > + DRM_DEBUG_KMS("Set Error Count Phy Test Pattern\n");
> > + I915_WRITE(DDI_DP_COMP_CTL(intel_dig_port->base.port),
> > + DDI_DP_COMP_CTL_ENABLE |
> > + DDI_DP_COMP_CTL_SCRAMBLED_0);
> > + break;
> > + case DP_PHY_TEST_PATTERN_PRBS7:
> > + DRM_DEBUG_KMS("Set PRBS7 Phy Test Pattern\n");
> > + I915_WRITE(DDI_DP_COMP_CTL(intel_dig_port->base.port),
> > + DDI_DP_COMP_CTL_ENABLE | DDI_DP_COMP_CTL_PRBS7);
> > + break;
> > + case DP_PHY_TEST_PATTERN_80BIT_CUSTOM:
> > + DRM_DEBUG_KMS("Set 80Bit Custom Phy Test Pattern\n");
> > + temp = ((data->custom80[0] << 24) | (data->custom80[1] << 16) |
> > + (data->custom80[2] << 8) | (data->custom80[3]));
> > + I915_WRITE(DDI_DP_COMP_PAT(intel_dig_port->base.port, 0), temp);
> > + temp = ((data->custom80[4] << 24) | (data->custom80[5] << 16) |
> > + (data->custom80[6] << 8) | (data->custom80[7]));
> > + I915_WRITE(DDI_DP_COMP_PAT(intel_dig_port->base.port, 1), temp);
> > + temp = ((data->custom80[8] << 8) | data->custom80[9]);
> > + I915_WRITE(DDI_DP_COMP_PAT(intel_dig_port->base.port, 2), temp);
> > + I915_WRITE(DDI_DP_COMP_CTL(intel_dig_port->base.port),
> > + DDI_DP_COMP_CTL_ENABLE | DDI_DP_COMP_CTL_CUSTOM80);
> > + break;
> > + case DP_PHY_TEST_PATTERN_CP2520:
> > + DRM_DEBUG_KMS("Set HBR2 compliance Phy Test Pattern\n");
> > + temp = ((data->hbr2_reset[1] << 8) | data->hbr2_reset[0]);
> > + I915_WRITE(DDI_DP_COMP_CTL(intel_dig_port->base.port),
> > + DDI_DP_COMP_CTL_ENABLE | DDI_DP_COMP_CTL_HBR2 |
> > + temp);
> > + break;
> > + default:
> > + WARN(1, "Invalid Phy Test PAttern\n");
Small nit here, it should be PHY Pattern
Manasi
> > + }
> > +}
> > +
> > static u8 intel_dp_autotest_phy_pattern(struct intel_dp *intel_dp)
> > {
> > u8 test_result = DP_TEST_NAK;
>
> --
> Jani Nikula, Intel Open Source Graphics Center
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-01-03 23:50 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 16:15 [PATCH v3 0/9] DP Phy compliance auto test Animesh Manna
2019-12-30 16:15 ` [Intel-gfx] " Animesh Manna
2019-12-30 16:15 ` [PATCH v3 1/9] drm/amd/display: Align macro name as per DP spec Animesh Manna
2019-12-30 16:15 ` [Intel-gfx] " Animesh Manna
2020-01-03 23:54 ` Manasi Navare
2020-01-03 23:54 ` [Intel-gfx] " Manasi Navare
2020-01-06 23:05 ` Alex Deucher
2020-01-06 23:05 ` [Intel-gfx] " Alex Deucher
2019-12-30 16:15 ` [PATCH v3 2/9] drm/dp: get/set phy compliance pattern Animesh Manna
2019-12-30 16:15 ` [Intel-gfx] " Animesh Manna
2019-12-30 16:15 ` [PATCH v3 3/9] drm/i915/dp: Move vswing/pre-emphasis adjustment calculation Animesh Manna
2019-12-30 16:15 ` [Intel-gfx] " Animesh Manna
2020-01-02 9:18 ` Jani Nikula
2020-01-02 9:18 ` [Intel-gfx] " Jani Nikula
2020-01-02 10:26 ` Manna, Animesh
2020-01-02 10:26 ` [Intel-gfx] " Manna, Animesh
2020-01-03 23:48 ` Manasi Navare
2020-01-03 23:48 ` [Intel-gfx] " Manasi Navare
2020-01-06 10:02 ` Manna, Animesh
2020-01-06 10:02 ` [Intel-gfx] " Manna, Animesh
2020-01-15 9:11 ` Jani Nikula
2020-01-15 9:11 ` [Intel-gfx] " Jani Nikula
2019-12-30 16:15 ` [PATCH v3 4/9] drm/i915/dp: Preparation for DP phy compliance auto test Animesh Manna
2019-12-30 16:15 ` [Intel-gfx] " Animesh Manna
2019-12-30 16:15 ` [PATCH v3 5/9] drm/i915/dsb: Send uevent to testapp Animesh Manna
2019-12-30 16:15 ` [Intel-gfx] " Animesh Manna
2019-12-30 16:15 ` [PATCH v3 6/9] drm/i915/dp: Add debugfs entry for DP phy compliance Animesh Manna
2019-12-30 16:15 ` [Intel-gfx] " Animesh Manna
2019-12-30 16:15 ` [PATCH v3 7/9] drm/i915/dp: Register definition for DP compliance register Animesh Manna
2019-12-30 16:15 ` [Intel-gfx] " Animesh Manna
2019-12-30 16:15 ` [PATCH v3 8/9] drm/i915/dp: Update the pattern as per request Animesh Manna
2019-12-30 16:15 ` [Intel-gfx] " Animesh Manna
2020-01-02 9:23 ` Jani Nikula
2020-01-02 9:23 ` Jani Nikula
2020-01-03 23:51 ` Manasi Navare [this message]
2020-01-03 23:51 ` Manasi Navare
2019-12-30 16:15 ` [PATCH v3 9/9] drm/i915/dp: [FIXME] Program vswing, pre-emphasis, test-pattern Animesh Manna
2019-12-30 16:15 ` [Intel-gfx] " Animesh Manna
2019-12-30 16:57 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for DP Phy compliance auto test (rev5) Patchwork
2019-12-30 17:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2019-12-31 7:05 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=20200103235136.GC2608@intel.com \
--to=manasi.d.navare@intel.com \
--cc=animesh.manna@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=nidhi1.gupta@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.