From: Raag Jadav <raag.jadav@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>
Cc: intel-xe@lists.freedesktop.org, saurabhg.gupta@intel.com,
alex.zuo@intel.com
Subject: Re: [PATCH] drm/xe/i2c: Report i2c irq handler issue
Date: Thu, 4 Jun 2026 14:38:50 +0200 [thread overview]
Message-ID: <aiFx2veqtpl9mdSo@black.igk.intel.com> (raw)
In-Reply-To: <20260603201007.3768029-1-jonathan.cavitt@intel.com>
On Thu, Jun 04, 2026 at 04:10:07AM +0800, Jonathan Cavitt wrote:
> xe_i2c_irq_handler calls generic_handle_irq_safe, which can return an
Use '()' for functions.
> error value. In all other cases, this is passed to a
Why the early wrapping? Looks like the next word can fit here.
> .*_err_ratelimited error message helper. Add the missing error handler.
There's no change in the code path so it wasn't "missing".
I'd rephrase this as "Log the error".
> This issue was caught by static analysis.
This is redundant information but I'll leave it to you.
> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> Cc: Raag Jadav <raag.jadav@intel.com>
> ---
> drivers/gpu/drm/xe/xe_i2c.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_i2c.c b/drivers/gpu/drm/xe/xe_i2c.c
> index 706783863d07..acfc171483b2 100644
> --- a/drivers/gpu/drm/xe/xe_i2c.c
> +++ b/drivers/gpu/drm/xe/xe_i2c.c
> @@ -177,12 +177,15 @@ static bool xe_i2c_irq_present(struct xe_device *xe)
> void xe_i2c_irq_handler(struct xe_device *xe, u32 master_ctl)
> {
> struct xe_mmio *mmio = xe_root_tile_mmio(xe);
> + int ret;
>
> if (!(master_ctl & I2C_IRQ) || !xe_i2c_irq_present(xe))
> return;
>
> /* Forward interrupt to I2C adapter */
> - generic_handle_irq_safe(xe->i2c->adapter_irq);
> + ret = generic_handle_irq_safe(xe->i2c->adapter_irq);
> + if (ret)
> + drm_err_ratelimited(&xe->drm, "error handling i2c irq: %d\n", ret);
drm_err_ratelimited() already logs "error" so I'd rephrase this as
"failed to handle i2c irq".
Raag
> /* Deassert after I2C adapter clears the interrupt */
> xe_mmio_rmw32(mmio, I2C_CONFIG_CMD, 0, PCI_COMMAND_INTX_DISABLE);
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-06-04 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 20:10 [PATCH] drm/xe/i2c: Report i2c irq handler issue Jonathan Cavitt
2026-06-03 20:40 ` ✓ CI.KUnit: success for " Patchwork
2026-06-03 21:36 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-06-04 11:30 ` ✓ Xe.CI.FULL: success " Patchwork
2026-06-04 12:38 ` Raag Jadav [this message]
2026-06-04 14:22 ` [PATCH] " Cavitt, Jonathan
2026-06-04 19:04 ` 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=aiFx2veqtpl9mdSo@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=alex.zuo@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=saurabhg.gupta@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