From: Raag Jadav <raag.jadav@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>, riana.tauro@intel.com
Cc: rodrigo.vivi@intel.com, intel-xe@lists.freedesktop.org,
heikki.krogerus@linux.intel.com, andi.shyti@linux.intel.com
Subject: Re: [PATCH v3 0/2] Wire up reset/postinstall for I2C IRQ
Date: Tue, 14 Oct 2025 06:52:31 +0200 [thread overview]
Message-ID: <aO3XD6iOuXfXTQRG@black.igk.intel.com> (raw)
In-Reply-To: <176036737835.1701571.11729682859198230623.b4-ty@intel.com>
On Mon, Oct 13, 2025 at 07:57:06AM -0700, Lucas De Marchi wrote:
> On Sat, 11 Oct 2025 18:05:07 +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.
> >
> > v2: Integrate DISABLE_MSI_CAP changes (Heikki)
> > v3: Drop DISABLE_MSI_CAP changes as they are not required for the usecase
> >
> > Raag Jadav (2):
> > drm/xe/i2c: Introduce xe_i2c_irq_present()
> > drm/xe/i2c: Wire up reset/postinstall for I2C IRQ
> >
> > [...]
>
> Merged to drm-xe-next, thanks!
Awesome.
Riana, I noticed we never actually xe_irq_install() in survivability mode
and I'm not sure if I2C controller will work without it.
Anything to worry about there?
Raag
prev parent reply other threads:[~2025-10-14 4:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 12:35 [PATCH v3 0/2] Wire up reset/postinstall for I2C IRQ Raag Jadav
2025-10-11 12:35 ` [PATCH v3 1/2] drm/xe/i2c: Introduce xe_i2c_irq_present() Raag Jadav
2025-10-11 12:35 ` [PATCH v3 2/2] drm/xe/i2c: Wire up reset/postinstall for I2C IRQ Raag Jadav
2025-10-11 13:18 ` ✓ CI.KUnit: success for Wire up reset/postinstall for I2C IRQ (rev3) Patchwork
2025-10-11 13:53 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-11 15:08 ` ✗ Xe.CI.Full: failure " Patchwork
2025-10-13 14:57 ` [PATCH v3 0/2] Wire up reset/postinstall for I2C IRQ Lucas De Marchi
2025-10-14 4:52 ` 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=aO3XD6iOuXfXTQRG@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