Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Naladala, Ramanaidu" <ramanaidu.naladala@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "B, Jeevan" <jeevan.b@intel.com>
Subject: Re: [PATCH i-g-t v5 0/4] Improvise-the-deep-pkgc
Date: Wed, 28 Aug 2024 12:02:31 +0530	[thread overview]
Message-ID: <0fa19592-b24b-4249-b165-d31aa9aaf233@intel.com> (raw)
In-Reply-To: <SN7PR11MB67503425F71BB85B71A9C562E3952@SN7PR11MB6750.namprd11.prod.outlook.com>



On 8/28/2024 11:18 AM, Kandpal, Suraj wrote:
> 
> 
>> -----Original Message-----
>> From: Naladala, Ramanaidu <ramanaidu.naladala@intel.com>
>> Sent: Tuesday, August 27, 2024 6:10 PM
>> To: igt-dev@lists.freedesktop.org
>> Cc: Kandpal, Suraj <suraj.kandpal@intel.com>; B, Jeevan
>> <jeevan.b@intel.com>; Naladala, Ramanaidu
>> <ramanaidu.naladala@intel.com>
>> Subject: [PATCH i-g-t v5 0/4] Improvise-the-deep-pkgc
> 
> Should be improve deep pkgc I had already commented on this

I think no need to change the cover letter title. It won't be merge into 
git. The Name change will create a new series so we loose previous rev 
history.
>   
> Regards,
> Suraj Kandpal
> 
>>
>> This update improve deep pkgc. Add a check for the eDP connector to ensure
>> proper connector handling. Increase the test duration to 4 seconds. Modify
>> the loop to use igt_wait for better handling of the package C-state counter
>> read.
>>
>> Naladala Ramanaidu (4):
>>    tests/intel/kms_pm_dc: Add time unit macros and update delay
>>      calculation
>>    tests/intel/kms_pm_dc: Update VRR handling and eDP output check
>>    tests/intel/kms_pm_dc: Update test duration to 4 seconds
>>    tests/intel/kms_pm_dc: Add polling for deep-pkgc
>>
>>   tests/intel/kms_pm_dc.c | 51 +++++++++++++++++++++++++++++------------
>>   1 file changed, 36 insertions(+), 15 deletions(-)
>>
>> --
>> 2.43.0
> 

  reply	other threads:[~2024-08-28  6:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27 12:40 [PATCH i-g-t v5 0/4] Improvise-the-deep-pkgc Naladala Ramanaidu
2024-08-27 12:40 ` [PATCH i-g-t v5 1/4] tests/intel/kms_pm_dc: Add time unit macros and update delay calculation Naladala Ramanaidu
2024-08-28  5:53   ` Kandpal, Suraj
2024-08-27 12:40 ` [PATCH i-g-t v5 2/4] tests/intel/kms_pm_dc: Update VRR handling and eDP output check Naladala Ramanaidu
2024-08-28  5:56   ` Kandpal, Suraj
2024-08-27 12:40 ` [PATCH i-g-t v5 3/4] tests/intel/kms_pm_dc: Update test duration to 4 seconds Naladala Ramanaidu
2024-08-27 12:40 ` [PATCH i-g-t v5 4/4] tests/intel/kms_pm_dc: Add polling for deep-pkgc Naladala Ramanaidu
2024-08-28  5:51   ` Kandpal, Suraj
2024-08-27 17:23 ` ✓ CI.xeBAT: success for Improvise-the-deep-pkgc (rev5) Patchwork
2024-08-27 17:35 ` ✓ Fi.CI.BAT: " Patchwork
2024-08-28  2:04 ` ✓ CI.xeFULL: " Patchwork
2024-08-28  5:48 ` [PATCH i-g-t v5 0/4] Improvise-the-deep-pkgc Kandpal, Suraj
2024-08-28  6:32   ` Naladala, Ramanaidu [this message]
2024-08-29  5:07 ` ✓ Fi.CI.IGT: success for Improvise-the-deep-pkgc (rev5) 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=0fa19592-b24b-4249-b165-d31aa9aaf233@intel.com \
    --to=ramanaidu.naladala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jeevan.b@intel.com \
    --cc=suraj.kandpal@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