From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/dp: Update dfp caps only if its a branch device
Date: Mon, 11 Dec 2023 10:54:11 +0200 [thread overview]
Message-ID: <87zfyhxgp8.fsf@intel.com> (raw)
In-Reply-To: <20231211051127.2774407-1-ankit.k.nautiyal@intel.com>
On Mon, 11 Dec 2023, Ankit Nautiyal <ankit.k.nautiyal@intel.com> wrote:
> Avoid checking for Downstream Facing Port capabilities,
> if its not a DP branch device.
Why?
The commit message *always* needs to answer the question why. This
commit message describes what the patch does in English.
BR,
Jani.
>
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 3b2482bf683f..bef797b63000 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -5502,6 +5502,9 @@ intel_dp_update_dfp(struct intel_dp *intel_dp,
> struct drm_i915_private *i915 = dp_to_i915(intel_dp);
> struct intel_connector *connector = intel_dp->attached_connector;
>
> + if (!drm_dp_is_branch(intel_dp->dpcd))
> + return;
> +
> intel_dp->dfp.max_bpc =
> drm_dp_downstream_max_bpc(intel_dp->dpcd,
> intel_dp->downstream_ports, drm_edid);
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-12-11 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 5:11 [PATCH] drm/i915/dp: Update dfp caps only if its a branch device Ankit Nautiyal
2023-12-11 5:56 ` ✓ Fi.CI.BAT: success for " Patchwork
2023-12-11 7:24 ` ✗ Fi.CI.IGT: failure " Patchwork
2023-12-11 8:54 ` Jani Nikula [this message]
2023-12-11 14:14 ` [PATCH] " Nautiyal, Ankit K
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=87zfyhxgp8.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ankit.k.nautiyal@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.