From: Jani Nikula <jani.nikula@linux.intel.com>
To: Imre Deak <imre.deak@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/4] drm/i915/dp: Account for channel coding efficiency on UHBR links
Date: Tue, 14 Nov 2023 11:00:49 +0200 [thread overview]
Message-ID: <87v8a4so8u.fsf@intel.com> (raw)
In-Reply-To: <20231113201110.510724-1-imre.deak@intel.com>
On Mon, 13 Nov 2023, Imre Deak <imre.deak@intel.com> wrote:
> Apply the correct BW allocation overhead and channel coding efficiency
> on UHBR link rates, similarly to DP1.4 link rates.
>
> Signed-off-by: Imre Deak <imre.deak@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_display.c | 10 ----------
> 1 file changed, 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> index 3effafcbb411a..24aebdb715e7d 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.c
> +++ b/drivers/gpu/drm/i915/display/intel_display.c
> @@ -2398,16 +2398,6 @@ add_bw_alloc_overhead(int link_clock, int bw_overhead,
> int ch_coding_efficiency =
> drm_dp_bw_channel_coding_efficiency(is_uhbr);
Why do we have this and intel_dp_max_data_rate() separately?
BR,
Jani.
>
> - /*
> - * TODO: adjust for actual UHBR channel coding efficiency and BW
> - * overhead.
> - */
> - if (is_uhbr) {
> - *data_m = pixel_data_rate;
> - *data_n = link_data_rate * 8 / 10;
> - return;
> - }
> -
> *data_m = DIV_ROUND_UP_ULL(mul_u32_u32(pixel_data_rate, bw_overhead),
> 1000000);
> *data_n = DIV_ROUND_DOWN_ULL(mul_u32_u32(link_data_rate, ch_coding_efficiency),
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-11-14 9:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 20:11 [Intel-gfx] [PATCH 1/4] drm/i915/dp: Account for channel coding efficiency on UHBR links Imre Deak
2023-11-13 20:11 ` [Intel-gfx] [PATCH 2/4] drm/i915/dp: Fix UHBR link M/N values Imre Deak
2023-11-14 3:29 ` Murthy, Arun R
2023-11-14 7:43 ` Imre Deak
2023-11-15 13:29 ` Murthy, Arun R
2023-11-13 20:11 ` [Intel-gfx] [PATCH 3/4] drm/i915/dp_mst: Fix PBN / MTP_TU size calculation for UHBR rates Imre Deak
2023-11-15 13:38 ` Imre Deak
2023-11-15 13:41 ` Murthy, Arun R
2023-11-15 14:25 ` Imre Deak
2023-11-16 5:37 ` Murthy, Arun R
2023-11-13 20:11 ` [Intel-gfx] [PATCH 4/4] drm/dp_mst: Fix PBN divider " Imre Deak
2023-11-13 20:11 ` Imre Deak
2023-11-13 22:54 ` [Intel-gfx] " kernel test robot
2023-11-13 22:54 ` kernel test robot
2023-11-13 22:54 ` kernel test robot
2023-11-13 23:05 ` [Intel-gfx] " kernel test robot
2023-11-13 23:05 ` kernel test robot
2023-11-13 23:05 ` kernel test robot
2023-11-13 22:32 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/4] drm/i915/dp: Account for channel coding efficiency on UHBR links Patchwork
2023-11-13 22:50 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-14 2:07 ` [Intel-gfx] [PATCH 1/4] " Murthy, Arun R
2023-11-14 9:00 ` Jani Nikula [this message]
2023-11-14 13:07 ` Imre Deak
2023-11-15 13:42 ` Imre Deak
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=87v8a4so8u.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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.