From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
Cc: "Saarinen, Jani" <jani.saarinen@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Syrjala, Ville" <ville.syrjala@intel.com>
Subject: Re: [PATCH v10 5/6] drm/i915/display: handle systems with duplicate psf gv points
Date: Mon, 8 Apr 2024 10:18:31 +0000 [thread overview]
Message-ID: <3358ebd7e8b14f8992c37188e53125cb2da66e95.camel@intel.com> (raw)
In-Reply-To: <ZhOrBzpTWJ0xKysl@intel.com>
On Mon, 2024-04-08 at 11:29 +0300, Lisovskiy, Stanislav wrote:
> On Fri, Apr 05, 2024 at 02:35:32PM +0300, Vinod Govindapillai wrote:
> > From: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> >
> > There could be multiple qgv and psf gv points with similar values.
> > Apparently pcode's handling og psf and qgv points are different. For
> > qgv case, pcode sets whatever is asked by the driver. But in case
> > of psf gv points, it compares the bw from points before setting the
> > mask. This can cause problems in scenarios where we have to disable
> > sagv by setting the highest bw point and there could be multiple
> > points with highest bw. So to set the maximum psf gv point, find
> > out all the points with the highest bw and set all together.
> >
> > v1: - use the same treatment to qgv points as well (Vinod)
> >
> > v2: - pcode confirms that for qgv points, it sets whatever the
> > driver sets (Vinod)
> >
> > Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> > Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_bw.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_bw.c b/drivers/gpu/drm/i915/display/intel_bw.c
> > index 5f4f93524bef..6fb228a1a28f 100644
> > --- a/drivers/gpu/drm/i915/display/intel_bw.c
> > +++ b/drivers/gpu/drm/i915/display/intel_bw.c
> > @@ -874,6 +874,8 @@ static unsigned int icl_max_bw_psf_gv_point_mask(struct drm_i915_private
> > *i915)
> > if (max_data_rate > max_bw) {
> > max_bw_point_mask = BIT(i);
> > max_bw = max_data_rate;
> > + } else if (max_data_rate == max_bw) {
> > + max_bw_point_mask |= BIT(i);
>
> So we just came back to where we started. Wondering still, why it even bothers to expose
> two equal PSF GV points. Not only having duplicate points doesn't make much sense for
> the driver(since the BW they provide is the same), but also requires some additional
> logic on top to handle those.
Yes. Unfortunately this is what pcode expects for psf gv points. (Please have a look at the email
thread with the pcode team/Art etc.)
For qgv, it sets whatever the driver sets!
BR
Vinod
>
> Stan
>
> > }
> > }
> >
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2024-04-08 10:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 11:35 [PATCH v10 0/6] QGV/SAGV related fixes Vinod Govindapillai
2024-04-05 11:35 ` [PATCH v10 1/6] drm/i915/display: Add meaningful traces for QGV point info error handling Vinod Govindapillai
2024-04-19 17:11 ` Ville Syrjälä
2024-04-05 11:35 ` [PATCH v10 2/6] drm/i915/display: Extract code required to calculate max qgv/psf gv point Vinod Govindapillai
2024-04-08 8:32 ` Lisovskiy, Stanislav
2024-04-08 10:25 ` Govindapillai, Vinod
2024-04-05 11:35 ` [PATCH v10 3/6] drm/i915/display: extract code to prepare qgv points mask Vinod Govindapillai
2024-04-05 11:35 ` [PATCH v10 4/6] drm/i915/display: Disable SAGV on bw init, to force QGV point recalculation Vinod Govindapillai
2024-04-05 11:35 ` [PATCH v10 5/6] drm/i915/display: handle systems with duplicate psf gv points Vinod Govindapillai
2024-04-08 8:29 ` Lisovskiy, Stanislav
2024-04-08 10:18 ` Govindapillai, Vinod [this message]
2024-04-05 11:35 ` [PATCH v10 6/6] drm/i915/display: force qgv check after the hw state readout Vinod Govindapillai
2024-04-19 17:19 ` Ville Syrjälä
2024-04-23 7:40 ` Govindapillai, Vinod
2024-04-23 7:46 ` Govindapillai, Vinod
2024-04-22 7:54 ` Lisovskiy, Stanislav
2024-04-05 12:24 ` ✗ Fi.CI.SPARSE: warning for QGV/SAGV related fixes (rev10) Patchwork
2024-04-05 12:40 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-04-06 5:02 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-06 7:38 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-19 8:42 ` [PATCH v10 0/6] QGV/SAGV related fixes Hogander, Jouni
2024-04-19 13:32 ` Govindapillai, Vinod
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=3358ebd7e8b14f8992c37188e53125cb2da66e95.camel@intel.com \
--to=vinod.govindapillai@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=stanislav.lisovskiy@intel.com \
--cc=ville.syrjala@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