From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>,
linux-kernel@vger.kernel.org
Cc: git@amd.com, Alexandre Belloni <alexandre.belloni@bootlin.com>,
Frank Li <Frank.Li@nxp.com>, Joel Stanley <joel@jms.id.au>,
linux-i3c@lists.infradead.org
Subject: Re: [PATCH v2] i3c: dw-i3c-master: Fix IBI count register selection for versalnet
Date: Wed, 01 Apr 2026 17:14:22 +0800 [thread overview]
Message-ID: <a9b3a99f42bb9d092e95b35290cf4043fc780d3f.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20260401084430.436059-1-shubhrajyoti.datta@amd.com>
Hi Shubhrajyoti,
> On DesignWare I3C controllers where IC_HAS_IBI_DATA=0 (such as versalnet),
> the IBI_STS_CNT field (bits [28:24] of QUEUE_STATUS_LEVEL) is hardwired
> to 0. The IBI status entry count is instead reported via IBI_BUF_BLR
> (bits [23:16] of the same register).
>
> irq_handle_ibis() was unconditionally reading IBI_STS_CNT, causing it to
> always see 0 pending IBIs on versalnet and return early without draining
> the IBI buffer. Since INTR_IBI_THLD_STAT is level-triggered against the
> buffer fill level, this left the interrupt permanently asserted.
>
> Detect IBI data capability at probe time by writing the IBI data threshold
> field in QUEUE_THLD_CTRL and reading it back. Use the result to select the
> correct register field in irq_handle_ibis().
>
> Signed-off-by: Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>
> ---
>
> Changes in v2:
> Remove the fixes tag
The base context looks better now, thanks.
One other question though:
> + /*
> + * Detect IBI data capability (IC_HAS_IBI_DATA): write a non-zero value
> + * to IBI_DATA_THLD and read back. On controllers like Versalnet
> + * the field is hardwired to 0 and the write is ignored. Restore the
> + * original register value after detection.
> + */
> + thld_ctrl = readl(master->regs + QUEUE_THLD_CTRL);
> + ret = thld_ctrl | QUEUE_THLD_CTRL_IBI_DATA(2);
> + writel(ret, master->regs + QUEUE_THLD_CTRL);
> + ret = readl(master->regs + QUEUE_THLD_CTRL);
> + if (ret & QUEUE_THLD_CTRL_IBI_DATA_MASK)
> + master->has_ibi_data = true;
> + writel(thld_ctrl, master->regs + QUEUE_THLD_CTRL);
How are you binding the driver to this device? Are you using a unique
OF compatible string, or something ACPI-based?
... and if that can be specific to this hardware instance, would that be
an effective mechanism to select the IBI read method instead?
Cheers,
Jeremy
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2026-04-01 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 8:44 [PATCH v2] i3c: dw-i3c-master: Fix IBI count register selection for versalnet Shubhrajyoti Datta
2026-04-01 9:14 ` Jeremy Kerr [this message]
2026-04-02 7:39 ` Datta, Shubhrajyoti
2026-04-02 8:32 ` Jeremy Kerr
2026-04-03 16:24 ` Alexandre Belloni
2026-04-08 9:06 ` Datta, Shubhrajyoti
2026-04-08 10:06 ` Jeremy Kerr
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=a9b3a99f42bb9d092e95b35290cf4043fc780d3f.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=git@amd.com \
--cc=joel@jms.id.au \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shubhrajyoti.datta@amd.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