From: Raag Jadav <raag.jadav@intel.com>
To: lucas.demarchi@intel.com, rodrigo.vivi@intel.com
Cc: intel-xe@lists.freedesktop.org, riana.tauro@intel.com,
heikki.krogerus@linux.intel.com, andi.shyti@linux.intel.com
Subject: Re: [PATCH v2 0/2] Wire up reset/postinstall for I2C IRQ
Date: Thu, 9 Oct 2025 15:42:45 +0200 [thread overview]
Message-ID: <aOe71Yj-o6QFFXaU@black.igk.intel.com> (raw)
In-Reply-To: <20251009070304.3210101-1-raag.jadav@intel.com>
On Thu, Oct 09, 2025 at 12:33:02PM +0530, Raag Jadav wrote:
> This series wires up reset/postinstall handles for I2C IRQ so that it
> can be routed to SGunit or PUnit when needed.
Please hold on to this series while I resolve a few queries with the
architecture.
Raag
> v2: Integrate DISABLE_MSI_CAP changes (Heikki)
>
> Raag Jadav (2):
> drm/xe/i2c: Introduce xe_i2c_irq_present()
> drm/xe/i2c: Wire up reset/postinstall for I2C IRQ
>
> drivers/gpu/drm/xe/regs/xe_i2c_regs.h | 4 ++++
> drivers/gpu/drm/xe/xe_i2c.c | 28 ++++++++++++++++++++++++++-
> drivers/gpu/drm/xe/xe_i2c.h | 4 ++++
> drivers/gpu/drm/xe/xe_irq.c | 2 ++
> 4 files changed, 37 insertions(+), 1 deletion(-)
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-10-09 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 7:03 [PATCH v2 0/2] Wire up reset/postinstall for I2C IRQ Raag Jadav
2025-10-09 7:03 ` [PATCH v2 1/2] drm/xe/i2c: Introduce xe_i2c_irq_present() Raag Jadav
2025-10-09 7:03 ` [PATCH v2 2/2] drm/xe/i2c: Wire up reset/postinstall for I2C IRQ Raag Jadav
2025-10-09 7:11 ` ✓ CI.KUnit: success for Wire up reset/postinstall for I2C IRQ (rev2) Patchwork
2025-10-09 7:53 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-09 10:08 ` ✗ Xe.CI.Full: failure " Patchwork
2025-10-09 13:42 ` Raag Jadav [this message]
2025-10-09 14:15 ` [PATCH v2 0/2] Wire up reset/postinstall for I2C IRQ Lucas De Marchi
2025-10-09 14:26 ` Rodrigo Vivi
2025-10-09 17:31 ` Raag Jadav
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=aOe71Yj-o6QFFXaU@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--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