Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <mripard@kernel.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	 Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	imre.deak@intel.com,  Lyude Paul <lyude@redhat.com>
Subject: Re: [PATCH v3 01/16] drm/mst: remove mgr parameter and debug logging from drm_dp_get_vc_payload_bw()
Date: Tue, 7 Jan 2025 16:14:33 +0100	[thread overview]
Message-ID: <20250107-classy-burrowing-kingfisher-a8a0d1@houat> (raw)
In-Reply-To: <875xmrlzhd.fsf@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]

On Tue, Jan 07, 2025 at 11:55:42AM +0200, Jani Nikula wrote:
> On Fri, 03 Jan 2025, Jani Nikula <jani.nikula@intel.com> wrote:
> > The struct drm_dp_mst_topology_mgr *mgr parameter is only used for debug
> > logging in case the passed in link rate or lane count are zero. There's
> > no further error checking as such, and the function returns 0.
> >
> > There should be no case where the parameters are zero. The returned
> > value is generally used as a divisor, and if we were hitting this, we'd
> > be seeing division by zero.
> >
> > Just remove the debug logging altogether, along with the mgr parameter,
> > so that the function can be used in non-MST contexts without the
> > topology manager.
> >
> > v2: Also remove drm_dp_mst_helper_tests_init as unnecessary (Imre)
> >
> > Cc: Imre Deak <imre.deak@intel.com>
> > Cc: Lyude Paul <lyude@redhat.com>
> > Reviewed-by: Imre Deak <imre.deak@intel.com>
> > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> 
> Maarten, Maxime, Thomas, ack for merging this via drm-intel along with
> the rest of the series?

Ack

Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]

  reply	other threads:[~2025-01-07 15:14 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-03 13:52 [PATCH v3 00/16] drm/i915/dp: 128b/132b uncompressed SST Jani Nikula
2025-01-03 13:52 ` [PATCH v3 01/16] drm/mst: remove mgr parameter and debug logging from drm_dp_get_vc_payload_bw() Jani Nikula
2025-01-07  9:55   ` Jani Nikula
2025-01-07 15:14     ` Maxime Ripard [this message]
2025-01-07 17:05       ` Jani Nikula
2025-01-09 22:06   ` Lyude Paul
2025-01-10  8:54     ` Jani Nikula
2025-01-03 13:52 ` [PATCH v3 02/16] drm/i915/mst: drop connector parameter from intel_dp_mst_bw_overhead() Jani Nikula
2025-01-03 13:52 ` [PATCH v3 03/16] drm/i915/mst: drop connector parameter from intel_dp_mst_compute_m_n() Jani Nikula
2025-01-03 13:52 ` [PATCH v3 04/16] drm/i915/mst: change return value of mst_stream_find_vcpi_slots_for_bpp() Jani Nikula
2025-01-03 13:52 ` [PATCH v3 05/16] drm/i915/mst: remove crtc_state->pbn Jani Nikula
2025-01-03 13:52 ` [PATCH v3 06/16] drm/i915/mst: split out a helper for figuring out the TU Jani Nikula
2025-01-03 13:52 ` [PATCH v3 07/16] drm/i915/mst: adapt intel_dp_mtp_tu_compute_config() for 128b/132b SST Jani Nikula
2025-01-03 13:52 ` [PATCH v3 08/16] drm/i915/ddi: enable 128b/132b TRANS_DDI_FUNC_CTL mode for UHBR SST Jani Nikula
2025-01-03 13:52 ` [PATCH v3 09/16] drm/i915/ddi: 128b/132b SST also needs DP_TP_CTL_MODE_MST Jani Nikula
2025-01-03 13:52 ` [PATCH v3 10/16] drm/i915/ddi: write payload for 128b/132b SST Jani Nikula
2025-01-03 14:23   ` Imre Deak
2025-01-07  9:54   ` [PATCH] " Jani Nikula
2025-01-03 13:52 ` [PATCH v3 11/16] drm/i915/ddi: initialize 128b/132b SST DP2 VFREQ registers Jani Nikula
2025-01-03 14:23   ` Imre Deak
2025-01-03 13:52 ` [PATCH v3 12/16] drm/i915/ddi: enable ACT handling for 128b/132b SST Jani Nikula
2025-01-03 14:39   ` Imre Deak
2025-01-03 13:52 ` [PATCH v3 13/16] drm/i915/ddi: start distinguishing 128b/132b SST and MST at state readout Jani Nikula
2025-01-03 13:52 ` [PATCH v3 14/16] drm/i915/ddi: handle 128b/132b SST in intel_ddi_read_func_ctl() Jani Nikula
2025-01-03 13:52 ` [PATCH v3 15/16] drm/i915/ddi: disable trancoder port select for 128b/132b SST Jani Nikula
2025-01-03 13:52 ` [PATCH v3 16/16] drm/i915/dp: compute config for 128b/132b SST w/o DSC Jani Nikula
2025-01-03 15:25 ` ✓ CI.Patch_applied: success for drm/i915/dp: 128b/132b uncompressed SST (rev4) Patchwork
2025-01-03 15:25 ` ✗ CI.checkpatch: warning " Patchwork
2025-01-03 15:27 ` ✓ CI.KUnit: success " Patchwork
2025-01-03 15:45 ` ✓ CI.Build: " Patchwork
2025-01-03 15:47 ` ✓ CI.Hooks: " Patchwork
2025-01-03 15:49 ` ✗ CI.checksparse: warning " Patchwork
2025-01-03 16:14 ` ✓ Xe.CI.BAT: success " Patchwork
2025-01-03 23:32 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-07 11:07 ` ✓ CI.Patch_applied: success for drm/i915/dp: 128b/132b uncompressed SST (rev5) Patchwork
2025-01-07 11:08 ` ✗ CI.checkpatch: warning " Patchwork
2025-01-07 11:09 ` ✓ CI.KUnit: success " Patchwork
2025-01-07 11:27 ` ✓ CI.Build: " Patchwork
2025-01-07 11:29 ` ✓ CI.Hooks: " Patchwork
2025-01-07 11:31 ` ✗ CI.checksparse: warning " Patchwork
2025-01-07 11:57 ` ✓ Xe.CI.BAT: success " Patchwork
2025-01-07 17:05 ` [PATCH v3 00/16] drm/i915/dp: 128b/132b uncompressed SST Jani Nikula
2025-01-08 15:43 ` ✗ Xe.CI.Full: failure for drm/i915/dp: 128b/132b uncompressed SST (rev5) 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=20250107-classy-burrowing-kingfisher-a8a0d1@houat \
    --to=mripard@kernel.org \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=lyude@redhat.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=tzimmermann@suse.de \
    /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