From: sashiko-bot@kernel.org
To: "Mika Kahola" <mika.kahola@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 3/4] drm/i915/lt_phy: drop the unused pll argument from intel_lt_phy_pll_enable()
Date: Wed, 14 Oct 2026 10:58:13 +0000 [thread overview]
Message-ID: <sashiko-outbox-171168@kernel.org> (raw)
In-Reply-To: <20261014105306.2761683-4-mika.kahola@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Unnecessary dead argument left in intel_xe3plpd_pll_enable()
--
commit f2396c693af5e8056514c60f30bea8044eae04b7
Author: Mika Kahola <mika.kahola@intel.com>
drm/i915/lt_phy: drop the unused pll argument from intel_lt_phy_pll_enable()
intel_lt_phy_pll_enable() never looks at the pll, it is there only
because intel_xe3plpd_pll_enable() forwards its own arguments. Drop it
so callers that have no pll do not have to pass NULL.
> diff --git a/drivers/gpu/drm/i915/display/intel_lt_phy.c b/drivers/gpu/drm/i915/display/intel_lt_phy.c
> index c626246b71f91..e05fd23b8a651 100644
> --- a/drivers/gpu/drm/i915/display/intel_lt_phy.c
> +++ b/drivers/gpu/drm/i915/display/intel_lt_phy.c
[ ... ]
> @@ -2300,7 +2299,7 @@ void intel_xe3plpd_pll_enable(struct intel_encoder *encoder,
> struct intel_dpll *pll,
> const struct intel_dpll_hw_state *dpll_hw_state)
> {
> - intel_lt_phy_pll_enable(encoder, pll, dpll_hw_state);
> + intel_lt_phy_pll_enable(encoder, dpll_hw_state);
> }
[Severity: Low]
Could we also drop the pll argument from intel_xe3plpd_pll_enable()?
Since the commit message mentions that intel_lt_phy_pll_enable() only had it
because intel_xe3plpd_pll_enable() forwards its own arguments, leaving it in
intel_xe3plpd_pll_enable() means we still have a dead argument here.
Dropping it from intel_xe3plpd_pll_enable() (and its caller in
intel_dpll_mgr.c) would make the API consistent, especially since its
counterpart intel_xe3plpd_pll_disable() takes only an encoder.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261014105306.2761683-1-mika.kahola@intel.com?part=3
next prev parent reply other threads:[~2026-10-14 10:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 10:53 [PATCH v2 0/4] Move the PLL power save W/A to the display W/A framework Mika Kahola
2026-10-14 10:53 ` [PATCH v2 1/4] drm/i915/dpll: move " Mika Kahola
2026-10-14 13:45 ` Mika Kahola
2026-10-14 10:53 ` [PATCH v2 2/4] drm/i915/lt_phy: split out intel_lt_phy_pll_calc_state_from_table() Mika Kahola
2026-10-15 4:10 ` Kandpal, Suraj
2026-10-14 10:53 ` [PATCH v2 3/4] drm/i915/lt_phy: drop the unused pll argument from intel_lt_phy_pll_enable() Mika Kahola
2026-10-14 10:58 ` sashiko-bot [this message]
2026-10-15 4:11 ` Kandpal, Suraj
2026-10-14 10:53 ` [PATCH v2 4/4] drm/i915/lt_phy: apply the PLL power save W/A on LT PHY platforms Mika Kahola
2026-10-14 11:10 ` sashiko-bot
2026-10-14 13:46 ` Mika Kahola
2026-10-15 4:26 ` Kandpal, Suraj
2026-10-14 11:48 ` ✓ i915.CI.BAT: success for Move the PLL power save W/A to the display W/A framework (rev2) Patchwork
2026-10-14 18:34 ` ✗ i915.CI.BAT: failure for Move the PLL power save W/A to the display W/A framework (rev4) Patchwork
2026-10-14 21:43 ` ✗ i915.CI.Full: failure for Move the PLL power save W/A to the display W/A framework (rev2) 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=sashiko-outbox-171168@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=mika.kahola@intel.com \
--cc=sashiko-reviews@lists.linux.dev \
/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