From: Raag Jadav <raag.jadav@intel.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
lucas.demarchi@intel.com, rodrigo.vivi@intel.com,
intel-xe@lists.freedesktop.org, riana.tauro@intel.com
Subject: Re: [PATCH v1 2/2] drm/xe/i2c: Wire up reset/postinstall for I2C IRQ
Date: Thu, 9 Oct 2025 08:12:38 +0200 [thread overview]
Message-ID: <aOdSVoKhHIClGgKK@black.igk.intel.com> (raw)
In-Reply-To: <aOYaSh5rlCElWurt@kuha.fi.intel.com>
On Wed, Oct 08, 2025 at 11:01:14AM +0300, Heikki Krogerus wrote:
> On Tue, Sep 30, 2025 at 01:22:33PM +0200, Raag Jadav wrote:
> > On Tue, Sep 30, 2025 at 01:13:57PM +0200, Andi Shyti wrote:
> > > Hi Raag,
> > >
> > > On Thu, Sep 25, 2025 at 01:38:35AM +0530, Raag Jadav wrote:
> > > > I2C IRQ needs to be routed to SGUnit or PUnit for the devices that support
> > > > it. Wire up reset/postinstall handles for I2C IRQ to take care of this.
> > > >
> > > > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> > >
> > > Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
> >
> > Awesome, thanks Andi.
> >
> > Heikki, I can integrate your DISABLE_MSI changes which I'm assuming
> > will be in the same path here?
>
> Yes, that would be awesome!
>
> > I know we're in the merge window but let me know how you'd want to
> > proceed.
>
> I think it would make sense to just take care of that DISABLE_MSI (bit
> 29) in this patch. There's not point in adding a separate patch for
> it. So if you can take care of it, that would be great!
>
> P.S.
>
> Espoo site closure is still keeping me busy, so I will be extra slow
> with responses for while longer. I will be completely unreachable next
> week (WW42).
I already miss black :(
Raag
next prev parent reply other threads:[~2025-10-09 6:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 20:08 [PATCH v1 0/2] Wire up reset/postinstall for I2C IRQ Raag Jadav
2025-09-24 20:08 ` [PATCH v1 1/2] drm/xe/i2c: Introduce xe_i2c_irq_present() Raag Jadav
2025-09-30 11:08 ` Andi Shyti
2025-10-08 8:08 ` Heikki Krogerus
2025-09-24 20:08 ` [PATCH v1 2/2] drm/xe/i2c: Wire up reset/postinstall for I2C IRQ Raag Jadav
2025-09-30 11:13 ` Andi Shyti
2025-09-30 11:22 ` Raag Jadav
2025-10-08 8:01 ` Heikki Krogerus
2025-10-08 8:05 ` Heikki Krogerus
2025-10-09 6:14 ` Raag Jadav
2025-10-09 6:12 ` Raag Jadav [this message]
2025-10-08 8:09 ` Heikki Krogerus
2025-09-24 20:16 ` ✓ CI.KUnit: success for " Patchwork
2025-09-24 21:13 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-25 3:42 ` ✗ Xe.CI.Full: failure " 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=aOdSVoKhHIClGgKK@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=andi.shyti@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.