Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: lucas.demarchi@intel.com, rodrigo.vivi@intel.com,
	intel-xe@lists.freedesktop.org, riana.tauro@intel.com
Subject: Re: [PATCH v1 1/2] drm/xe/i2c: Introduce xe_i2c_irq_present()
Date: Wed, 8 Oct 2025 11:08:55 +0300	[thread overview]
Message-ID: <aOYcF8syCKyl9faI@kuha.fi.intel.com> (raw)
In-Reply-To: <20250924200835.3143173-2-raag.jadav@intel.com>

On Thu, Sep 25, 2025 at 01:38:34AM +0530, Raag Jadav wrote:
> In preparation of wider usecases which require checking for I2C IRQ
> presence, introduce xe_i2c_irq_present() helper.
> 
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>

FWIW:

Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>

> ---
>  drivers/gpu/drm/xe/xe_i2c.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_i2c.c b/drivers/gpu/drm/xe/xe_i2c.c
> index 48dfcb41fa08..25c6b8f3c0bb 100644
> --- a/drivers/gpu/drm/xe/xe_i2c.c
> +++ b/drivers/gpu/drm/xe/xe_i2c.c
> @@ -160,6 +160,11 @@ bool xe_i2c_present(struct xe_device *xe)
>  	return xe->i2c && xe->i2c->ep.cookie == XE_I2C_EP_COOKIE_DEVICE;
>  }
>  
> +static bool xe_i2c_irq_present(struct xe_device *xe)
> +{
> +	return xe->i2c && xe->i2c->adapter_irq;
> +}
> +
>  /**
>   * xe_i2c_irq_handler: Handler for I2C interrupts
>   * @xe: xe device instance
> @@ -170,7 +175,7 @@ bool xe_i2c_present(struct xe_device *xe)
>   */
>  void xe_i2c_irq_handler(struct xe_device *xe, u32 master_ctl)
>  {
> -	if (!xe->i2c || !xe->i2c->adapter_irq)
> +	if (!xe_i2c_irq_present(xe))
>  		return;
>  
>  	if (master_ctl & I2C_IRQ)
> -- 
> 2.34.1

-- 
heikki

  parent reply	other threads:[~2025-10-08  8:09 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 [this message]
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
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=aOYcF8syCKyl9faI@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=raag.jadav@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