Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Kunal Joshi <kunal1.joshi@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 0/2] Add test for hotplug validation in simulation
Date: Tue, 3 Oct 2023 14:42:43 +0530	[thread overview]
Message-ID: <17bd5bee-d5ff-9351-ed9b-e917b780d491@intel.com> (raw)
In-Reply-To: <20231001103006.431894-1-kunal1.joshi@intel.com>

Hi Kunal,

On Sun-01-10-2023 04:00 pm, Kunal Joshi wrote:
> Test to validate hotplug in simulation environment we
> have scratch pad register 0x4f080 from which we can
> trigger uevents such as HPD, VBLANK..etc, Idea is to
> have port mapping placed in igtrcthrough which test
> can write to 0x4f080 and check if we get hotplug

In first glance, do we really need to upstream this test? I am pretty 
sure, no one (including Intel) is going to use this test from upstream 
repo (We don't have any simulation environment in public CI).

So, we can't merge this.

+ Kamil, thoughts?

- Bhanu

> 
> Cc: Karthik B S <karthik.b.s@intel.com>
> Cc: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
> Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com>
> 
> Kunal Joshi (2):
>    tests/kms_simulation_hpd: New test for hotplug validation
>    tests/meson: added test to meson.build
> 
>   tests/intel/kms_simulation_hpd.c | 534 +++++++++++++++++++++++++++++++
>   tests/meson.build                |   1 +
>   2 files changed, 535 insertions(+)
>   create mode 100644 tests/intel/kms_simulation_hpd.c
> 

  parent reply	other threads:[~2023-10-03  9:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-01 10:30 [igt-dev] [PATCH i-g-t 0/2] Add test for hotplug validation in simulation Kunal Joshi
2023-10-01 10:30 ` [igt-dev] [PATCH i-g-t 1/2] tests/kms_simulation_hpd: New test for hotplug validation Kunal Joshi
2023-10-01 10:30 ` [igt-dev] [PATCH i-g-t 2/2] tests/meson: added test to meson.build Kunal Joshi
2023-10-01 10:50 ` [igt-dev] ✗ Fi.CI.BUILD: failure for Add test for hotplug validation in simulation Patchwork
2023-10-01 10:54 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2023-10-03  9:12 ` Modem, Bhanuprakash [this message]
2023-10-04  5:48   ` [igt-dev] [PATCH i-g-t 0/2] " Modem, Bhanuprakash
2023-10-04  8:15     ` Juha-Pekka Heikkila
2023-10-04 10:36       ` Kamil Konieczny
2023-10-26  6:38         ` Joshi, Kunal1
2023-10-26  7:31           ` Modem, Bhanuprakash
2023-10-04 13:28       ` Modem, Bhanuprakash

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=17bd5bee-d5ff-9351-ed9b-e917b780d491@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kunal1.joshi@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