From: Raag Jadav <raag.jadav@intel.com>
To: "Poosa, Karthik" <karthik.poosa@intel.com>
Cc: igt-dev@lists.freedesktop.org, anshuman.gupta@intel.com,
badal.nilawar@intel.com, riana.tauro@intel.com,
rodrigo.vivi@intel.com, heikki.krogerus@linux.intel.com,
lucas.demarchi@intel.com
Subject: Re: [i-g-t,v3] tests/intel/xe_pm: Introduce i2c subtests
Date: Mon, 28 Jul 2025 19:08:23 +0300 [thread overview]
Message-ID: <aIegd7oC_sNLfaPo@black.fi.intel.com> (raw)
In-Reply-To: <98f03e96-d5ae-4193-a76c-e8dc2d2877da@intel.com>
On Mon, Jul 28, 2025 at 06:34:30PM +0530, Poosa, Karthik wrote:
> On 23-07-2025 17:46, Raag Jadav wrote:
> > Introduce subtests for i2c adapter which is used to control on-board
> > OEM sensors on selected devices. This will test D3hot/D3cold transition
> > before and after i2c adapter access for the devices that support it.
...
> Hi Raag,
>
> 1. This LGTM.
>
> Acked-by: Karthik Poosa <karthik.poosa@intel.com>
Thanks.
> 2. Could you add a new sub-test which runs i2c_test, after the system
> suspend and resume cycle, similar to exec-after test ?
>
> If there is any issue with I2C after system suspend/resume, we would know
> with that.
>
> You can add it as a separate patch if you want.
Yes, I plan to add it along with a few other tests (like mmap) that are
still missing system PM coverage.
Let's get this one through for now so we unblock test coverage for this.
Raag
prev parent reply other threads:[~2025-07-28 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 12:16 [PATCH i-g-t v3] tests/intel/xe_pm: Introduce i2c subtests Raag Jadav
2025-07-23 18:36 ` ✓ i915.CI.BAT: success for tests/intel/xe_pm: Introduce i2c subtests (rev3) Patchwork
2025-07-23 18:44 ` ✓ Xe.CI.BAT: " Patchwork
2025-07-24 2:07 ` ✗ Xe.CI.Full: failure " Patchwork
2025-07-24 9:08 ` ✓ i915.CI.Full: success " Patchwork
2025-07-28 13:04 ` [i-g-t,v3] tests/intel/xe_pm: Introduce i2c subtests Poosa, Karthik
2025-07-28 16:08 ` Raag Jadav [this message]
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=aIegd7oC_sNLfaPo@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@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;
as well as URLs for NNTP newsgroup(s).