From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
IGT development <igt-dev@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 5/5] lib/kms: warn if we commit without outputs
Date: Fri, 2 Nov 2018 13:11:30 +0100 [thread overview]
Message-ID: <caf99587-a1ec-e9f2-79e4-3c5052654ddd@linux.intel.com> (raw)
In-Reply-To: <20181102095726.9052-5-daniel.vetter@ffwll.ch>
Op 02-11-18 om 10:57 schreef Daniel Vetter:
> With the high-level helpers requiring outputs there's not point
> in silently ignoring issues anymore. Complain about that if it
> ever happens.
>
> This reverts
>
> commit 212b71372bfbb73663d872df31118d6b396ada4f
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date: Fri Sep 14 21:03:38 2018 +0100
>
> lib/kms: Skip no-op display updates
>
> which created an in my opinion serious API issue by silently dropping
> possible errors on the floor. Instead of silently second guess what
> the test might have wanted to do in the absence of display outputs
> it's much better to be explicit, and enforce that.
>
> v2: Improve commit message.
>
> Cc: Antonio Argenziano <antonio.argenziano@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
> lib/igt_kms.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/igt_kms.c b/lib/igt_kms.c
> index 7214101e2696..5a35f6bbc177 100644
> --- a/lib/igt_kms.c
> +++ b/lib/igt_kms.c
> @@ -3292,7 +3292,7 @@ static int do_display_commit(igt_display_t *display,
> enum pipe pipe;
> LOG_INDENT(display, "commit");
>
> - if (!display->n_pipes || !display->n_outputs)
> + if (igt_warn_on(!display->n_pipes || !display->n_outputs))
> return 0; /* nothing to do */
>
> igt_display_refresh(display);
> @@ -3345,7 +3345,7 @@ int igt_display_try_commit_atomic(igt_display_t *display, uint32_t flags, void *
> {
> int ret;
>
> - if (!display->n_pipes || !display->n_outputs)
> + if (igt_warn_on(!display->n_pipes || !display->n_outputs))
> return 0; /* nothing to do */
>
> LOG_INDENT(display, "commit");
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-11-02 12:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 9:57 [igt-dev] [PATCH i-g-t 1/5] tests/sw_sync: use igt_fork_helper Daniel Vetter
2018-11-02 9:57 ` [igt-dev] [PATCH i-g-t 2/5] tests/debugfs: use igt_display_require Daniel Vetter
2018-11-02 11:16 ` Chris Wilson
2018-11-06 17:18 ` Antonio Argenziano
2018-11-06 22:05 ` Daniel Vetter
2018-11-06 22:09 ` [igt-dev] [PATCH i-g-t] " Daniel Vetter
2018-11-02 9:57 ` [igt-dev] [PATCH i-g-t 3/5] tests: Use igt_display_require Daniel Vetter
2018-11-06 22:09 ` [igt-dev] [PATCH i-g-t] " Daniel Vetter
2018-11-02 9:57 ` [igt-dev] [PATCH i-g-t 4/5] lib/kms: Drop igt_display_init Daniel Vetter
2018-11-02 9:57 ` [igt-dev] [PATCH i-g-t 5/5] lib/kms: warn if we commit without outputs Daniel Vetter
2018-11-02 12:11 ` Maarten Lankhorst [this message]
2018-11-20 10:21 ` Daniel Vetter
2018-11-20 11:09 ` Maarten Lankhorst
2018-11-21 12:23 ` [igt-dev] [PATCH i-g-t] " Daniel Vetter
2018-11-02 10:36 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/5] tests/sw_sync: use igt_fork_helper Patchwork
2018-11-02 12:07 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-11-02 12:26 ` [igt-dev] [PATCH i-g-t 1/5] " Robert Foss
2018-11-07 19:41 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/5] tests/sw_sync: use igt_fork_helper (rev3) Patchwork
2018-11-08 7:23 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-11-21 15:01 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/5] tests/sw_sync: use igt_fork_helper (rev4) 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=caf99587-a1ec-e9f2-79e4-3c5052654ddd@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=igt-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox