From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/dp: Define each HBR link rate
Date: Tue, 3 Dec 2019 15:11:54 +0200 [thread overview]
Message-ID: <20191203131154.GP1208@intel.com> (raw)
In-Reply-To: <87a789kc7v.fsf@intel.com>
On Tue, Dec 03, 2019 at 11:08:52AM +0200, Jani Nikula wrote:
> On Mon, 02 Dec 2019, José Roberto de Souza <jose.souza@intel.com> wrote:
> > This is better than keep those values in the code that you always
> > need to check the DP spec to know what level of HBR it is.
> >
> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_ddi.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_ddi.c b/drivers/gpu/drm/i915/display/intel_ddi.c
> > index a976606d21c7..914f0cc4d237 100644
> > --- a/drivers/gpu/drm/i915/display/intel_ddi.c
> > +++ b/drivers/gpu/drm/i915/display/intel_ddi.c
> > @@ -49,6 +49,10 @@
> > #include "intel_tc.h"
> > #include "intel_vdsc.h"
> >
> > +#define HBR_RATE 270000
> > +#define HBR2_RATE 540000
> > +#define HBR3_RATE 810000
> > +
> > struct ddi_buf_trans {
> > u32 trans1; /* balance leg enable, de-emph level */
> > u32 trans2; /* vref sel, vswing */
> > @@ -888,7 +892,7 @@ icl_get_combo_buf_trans(struct drm_i915_private *dev_priv, int type, int rate,
> > if (type == INTEL_OUTPUT_HDMI) {
> > *n_entries = ARRAY_SIZE(icl_combo_phy_ddi_translations_hdmi);
> > return icl_combo_phy_ddi_translations_hdmi;
> > - } else if (rate > 540000 && type == INTEL_OUTPUT_EDP) {
> > + } else if (rate > HBR2_RATE && type == INTEL_OUTPUT_EDP) {
>
> I don't want a patch switching some random place to using a
> macro. Either we stick to numbers or switch all.
>
> And if switch all, add the rates to drm core, not locally to
> intel_ddi.c. (And then wonder what to do with the intermediate rates in
> intel_dp_set_source_rates()...)
Yeah, we'll still end up with a mix of defines and raw numbers.
>
> Personally, HBR<N> is less useful to me in code, it's the actual rate
> that helps me.
>
> But I'll trust Ville's judgement on this one.
I tend to prefer raw numbers for this sort of stuff. If we didn't have
the intermediate rates I might have a different opinion. The only thing
I really worry about with raw numbers is the potential for typos.
The original problem of bspec talking about hbr2 in the bug trans
tables we could probably solve with a comment.
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-12-03 13:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 2:31 [PATCH 1/2] drm/i915/dp: Define each HBR link rate José Roberto de Souza
2019-12-03 2:31 ` [Intel-gfx] " José Roberto de Souza
2019-12-03 2:31 ` [PATCH 2/2] drm/i915/dp/tgl+: Update combo phy vswing tables José Roberto de Souza
2019-12-03 2:31 ` [Intel-gfx] " José Roberto de Souza
2019-12-03 13:18 ` Ville Syrjälä
2019-12-03 16:35 ` Matt Roper
2019-12-03 3:09 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/dp: Define each HBR link rate Patchwork
2019-12-03 3:09 ` [Intel-gfx] " Patchwork
2019-12-03 9:08 ` [Intel-gfx] [PATCH 1/2] " Jani Nikula
2019-12-03 13:11 ` Ville Syrjälä [this message]
2019-12-03 21:48 ` Souza, Jose
2019-12-03 22:01 ` Manasi Navare
2019-12-03 9:21 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] " Patchwork
2019-12-03 16:17 ` [Intel-gfx] [PATCH 1/2] " Matt Roper
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=20191203131154.GP1208@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.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