From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Manasi Navare <navaremanasi@chromium.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Return correct err code for bpc < 0
Date: Tue, 11 Apr 2023 20:42:38 +0300 [thread overview]
Message-ID: <ZDWcDhmJyMhQpQBa@intel.com> (raw)
In-Reply-To: <20230411173408.1945921-1-navaremanasi@chromium.org>
On Tue, Apr 11, 2023 at 05:34:08PM +0000, Manasi Navare wrote:
> In the function intel_dp_max_bpp(), currently if bpc < 0 in case of error,
> we return 0 instead of returning an err code of -EINVAL.
> This throws off the logic in the calling function.
What logic? The caller doesn't expect to get an error.
> Fix this by returning
> -EINVAL in case bpc < 0 which would be an error.
>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Cc: Sean Paul <sean@poorly.run>
> Signed-off-by: Manasi Navare <navaremanasi@chromium.org>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index f0bace9d98a1..f6546292e7c6 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -1280,7 +1280,7 @@ static int intel_dp_max_bpp(struct intel_dp *intel_dp,
> max_hdmi_bpc = intel_dp_hdmi_compute_bpc(intel_dp, crtc_state, bpc,
> respect_downstream_limits);
> if (max_hdmi_bpc < 0)
> - return 0;
> + return -EINVAL;
>
> bpc = min(bpc, max_hdmi_bpc);
> }
> --
> 2.40.0.577.gac1e443424-goog
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2023-04-11 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 17:34 [Intel-gfx] [PATCH] drm/i915/display: Return correct err code for bpc < 0 Manasi Navare
2023-04-11 17:42 ` Ville Syrjälä [this message]
2023-04-12 0:07 ` Manasi Navare
2023-04-12 5:22 ` Ville Syrjälä
2023-04-13 15:23 ` Manasi Navare
2023-04-17 22:48 ` Manasi Navare
2023-04-18 12:46 ` Ville Syrjälä
2023-04-18 14:39 ` Nautiyal, Ankit K
2023-04-18 14:54 ` Ville Syrjälä
2023-04-18 22:42 ` Manasi Navare
2023-04-19 4:59 ` Nautiyal, Ankit K
2023-04-19 5:04 ` Nautiyal, Ankit K
2023-04-12 0:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-04-12 13:44 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=ZDWcDhmJyMhQpQBa@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=navaremanasi@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox