From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>,
igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 4/5] tests/intel/kms_pm_dc: Use gem_has_lmem()
Date: Mon, 11 Sep 2023 20:42:51 +0530 [thread overview]
Message-ID: <4368f552-353c-bb7b-32a5-768e9904d9b9@intel.com> (raw)
In-Reply-To: <d8212e26-7b4e-b6d5-1881-8d7c68f8bfea@intel.com>
On 11-Sep-23 8:21 PM, Modem, Bhanuprakash wrote:
> Hi Swati,
>
> On Fri-08-09-2023 11:20 pm, Swati Sharma wrote:
>> Instead of using i915_capabilities debugfs to know if platform
>> is discrete or not, use gem_has_lmem for the same.
>>
>> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
>> ---
>> tests/intel/kms_pm_dc.c | 13 +++----------
>> 1 file changed, 3 insertions(+), 10 deletions(-)
>>
>> diff --git a/tests/intel/kms_pm_dc.c b/tests/intel/kms_pm_dc.c
>> index b5779eaa5..cbb419e12 100644
>> --- a/tests/intel/kms_pm_dc.c
>> +++ b/tests/intel/kms_pm_dc.c
>> @@ -140,15 +140,6 @@ typedef struct {
>> static bool dc_state_wait_entry(int drm_fd, int dc_flag, int
>> prev_dc_count);
>> static void check_dc_counter(data_t *data, int dc_flag, uint32_t
>> prev_dc_count);
>> -static bool is_dgfx(data_t *data)
>> -{
>> - char buf[4096];
>> -
>> - igt_debugfs_simple_read(data->debugfs_fd, "i915_capabilities",
>> - buf, sizeof(buf));
>> - return strstr(buf, "is_dgfx: yes");
>> -}
>> -
>> static void setup_output(data_t *data)
>> {
>> igt_display_t *display = &data->display;
>> @@ -661,6 +652,7 @@ static void kms_poll_state_restore(int sig)
>> igt_main
>> {
>> data_t data = {};
>> + bool is_dgfx;
>> igt_fixture {
>> data.drm_fd = drm_open_driver_master(DRIVER_INTEL);
>> @@ -742,7 +734,8 @@ igt_main
>> igt_describe("This test validates display engine entry to DC9
>> state");
>> igt_subtest("dc9-dpms") {
>> - if (!(is_dgfx(&data)))
>> + is_dgfx = gem_has_lmem(data.drm_fd);
>> + if (!is_dgfx)
>>
>> igt_require_f(igt_pm_pc8_plus_residencies_enabled(data.msr_fd),
>
> Patch LGTM, but looks we don't even need of the variable "is_dgfx",
> instead you can adjust the igt_require_f().
>
> If it's make sense, please fix the above comment.
IMO, this looks okay for readability.
>
> Reviewed-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
>
> - Bhanu
>
>> "PC8+ residencies not supported\n");
>> test_dc9_dpms(&data);
next prev parent reply other threads:[~2023-09-11 15:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 17:50 [igt-dev] [PATCH i-g-t 0/5] Add XE support for display PM tests Swati Sharma
2023-09-08 17:50 ` [igt-dev] [PATCH i-g-t 1/5] tests/intel/kms_pm_backlight: Add XE support Swati Sharma
2023-09-11 14:42 ` Modem, Bhanuprakash
2023-09-08 17:50 ` [igt-dev] [PATCH i-g-t 2/5] tests/intel/kms_pm_lpsp: " Swati Sharma
2023-09-11 14:44 ` Modem, Bhanuprakash
2023-09-11 15:08 ` Sharma, Swati2
2023-09-13 10:42 ` Modem, Bhanuprakash
2023-09-08 17:50 ` [igt-dev] [PATCH i-g-t 3/5] tests/intel/kms_pm_dc: Use linear modifier to set primary plane Swati Sharma
2023-09-11 14:45 ` Modem, Bhanuprakash
2023-09-11 15:10 ` Sharma, Swati2
2023-09-13 10:43 ` Modem, Bhanuprakash
2023-09-08 17:50 ` [igt-dev] [PATCH i-g-t 4/5] tests/intel/kms_pm_dc: Use gem_has_lmem() Swati Sharma
2023-09-11 14:51 ` Modem, Bhanuprakash
2023-09-11 15:12 ` Sharma, Swati2 [this message]
2023-09-08 17:50 ` [igt-dev] [PATCH i-g-t 5/5] tests/intel/kms_pm_dc: Add XE support Swati Sharma
2023-09-11 15:00 ` Modem, Bhanuprakash
2023-09-11 15:13 ` Sharma, Swati2
2023-09-08 19:19 ` [igt-dev] ✗ GitLab.Pipeline: warning for Add XE support for display PM tests Patchwork
2023-09-08 19:56 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-09-08 20:25 ` [igt-dev] ✗ CI.xeBAT: failure " Patchwork
2023-09-09 0:50 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-09-14 14:03 [igt-dev] [PATCH i-g-t 0/5] " Swati Sharma
2023-09-14 14:04 ` [igt-dev] [PATCH i-g-t 4/5] tests/intel/kms_pm_dc: Use gem_has_lmem() Swati Sharma
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=4368f552-353c-bb7b-32a5-768e9904d9b9@intel.com \
--to=swati2.sharma@intel.com \
--cc=bhanuprakash.modem@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