From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Mohammed Thasleem <mohammed.thasleem@intel.com>,
<igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH v3 2/2] lib/igt_kms: Check for other modes to fit on bw when ENOSPC failure
Date: Tue, 9 May 2023 10:54:09 +0530 [thread overview]
Message-ID: <cba1cf0d-4c4b-d21b-5e58-d992e46bd739@intel.com> (raw)
In-Reply-To: <20230507193943.57877-3-mohammed.thasleem@intel.com>
On Mon-08-05-2023 01:09 am, Mohammed Thasleem wrote:
> It check other then ENOSPC failure and if its ENOSPC then check all
> active outputs modes to fit possible bw and return false if not found
> any suitable bw.
>
> v2: Check for other then ENOSPC failure. (Bhanu)
> v3: Updated commit message.
>
> Signed-off-by: Mohammed Thasleem <mohammed.thasleem@intel.com>
Reviewed-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
> ---
> lib/igt_kms.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/lib/igt_kms.c b/lib/igt_kms.c
> index a6e91f982..5047d4b1b 100644
> --- a/lib/igt_kms.c
> +++ b/lib/igt_kms.c
> @@ -4574,6 +4574,8 @@ bool __override_all_active_output_modes_to_fit_bw(igt_display_t *display,
>
> if (!ret)
> return true;
> + else if (ret != -ENOSPC)
> + return false;
> }
>
> return false;
next prev parent reply other threads:[~2023-05-09 5:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 19:39 [igt-dev] [PATCH v3 0/2] Add negative test for extended display Mohammed Thasleem
2023-05-07 19:39 ` [igt-dev] [PATCH v3 1/2] tests/kms_display_modes: " Mohammed Thasleem
2023-05-12 10:36 ` Kamil Konieczny
2023-06-05 15:08 ` Kamil Konieczny
2023-05-07 19:39 ` [igt-dev] [PATCH v3 2/2] lib/igt_kms: Check for other modes to fit on bw when ENOSPC failure Mohammed Thasleem
2023-05-09 5:24 ` Modem, Bhanuprakash [this message]
2023-05-07 20:20 ` [igt-dev] ✓ Fi.CI.BAT: success for Add negative test for extended display (rev2) Patchwork
2023-05-07 21:55 ` [igt-dev] ✓ 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=cba1cf0d-4c4b-d21b-5e58-d992e46bd739@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=mohammed.thasleem@intel.com \
/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