From: Manasi Navare <manasi.d.navare@intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: igt-dev@lists.freedesktop.org,
Anusha Srivatsa <anusha.srivatsa@intel.com>,
Petri Latvala <petri.latvala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_dp_dsc: Force a full modeset when we force dsc enable
Date: Fri, 5 Apr 2019 11:28:36 -0700 [thread overview]
Message-ID: <20190405182835.GK17236@intel.com> (raw)
In-Reply-To: <20190405100646.GB13716@ideak-desk.fi.intel.com>
On Fri, Apr 05, 2019 at 01:06:46PM +0300, Imre Deak wrote:
> On Thu, Apr 04, 2019 at 04:44:35PM -0700, Manasi Navare wrote:
> > [...]
> > So just call igt_install_exit_handler() without pasisng any function pointer to do
> > just the default cleanups?
>
> You need to pass it a pointer to a new function you add. The new
> function should write the original value to the debugfs file.
Ok, I had added the restore_value() function to the test_cleanup that I call after update_display()
but yes adding that to the exit handler function would be a good idea.
the test cleanup function that I have now does:
if (data->output) {
igt_plane_set_fb(primary, NULL);
igt_display_commit(&data->display);
igt_remove_fb(data->drm_fd, &data->fb_test_pattern);
}
Hmm, I can still keep this after each test as is correct?
Manasi
>
> --Imre
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-04-05 18:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 19:31 [igt-dev] [PATCH i-g-t] tests/kms_dp_dsc: Force a full modeset when we force dsc enable Manasi Navare
2019-04-02 20:10 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-04-03 7:46 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-04-03 10:06 ` [igt-dev] [PATCH i-g-t] " Petri Latvala
2019-04-03 13:25 ` Imre Deak
2019-04-03 18:20 ` Manasi Navare
2019-04-03 19:33 ` Imre Deak
2019-04-03 20:17 ` Manasi Navare
2019-04-03 20:34 ` Imre Deak
2019-04-03 20:49 ` Manasi Navare
2019-04-03 21:42 ` Imre Deak
2019-04-03 22:48 ` Manasi Navare
2019-04-03 23:02 ` Imre Deak
2019-04-03 23:11 ` Manasi Navare
2019-04-03 23:15 ` Imre Deak
2019-04-04 23:44 ` Manasi Navare
2019-04-05 10:06 ` Imre Deak
2019-04-05 18:28 ` Manasi Navare [this message]
2019-04-03 17:38 ` Srivatsa, Anusha
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=20190405182835.GK17236@intel.com \
--to=manasi.d.navare@intel.com \
--cc=anusha.srivatsa@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=petri.latvala@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 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.