From: Frank Li <Frank.li@nxp.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: linux-i3c@lists.infradead.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH 2/5] i3c: mipi-i3c-hci: Remove nonexistent ring interrupt
Date: Fri, 12 Sep 2025 10:23:24 -0400 [thread overview]
Message-ID: <aMQs3P9BNOMt/lve@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250827103009.243771-3-jarkko.nikula@linux.intel.com>
On Wed, Aug 27, 2025 at 01:30:06PM +0300, Jarkko Nikula wrote:
> Ring interrupt bit 7, INTR_WARN_INS_STOP_MODE was probably drafted at
> some point but is marked as reserved in the MIPI I3C HCI specification
> versions 1.1 and 1.2 that came out after the initial code and also in
> the earlier specification versions so remove it.
>
> Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
> ---
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> drivers/i3c/master/mipi-i3c-hci/dma.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/drivers/i3c/master/mipi-i3c-hci/dma.c b/drivers/i3c/master/mipi-i3c-hci/dma.c
> index f5f5ab4db172..8bc9de189543 100644
> --- a/drivers/i3c/master/mipi-i3c-hci/dma.c
> +++ b/drivers/i3c/master/mipi-i3c-hci/dma.c
> @@ -77,7 +77,6 @@
> #define INTR_TRANSFER_COMPLETION BIT(11)
> #define INTR_RING_OP BIT(10)
> #define INTR_TRANSFER_ERR BIT(9)
> -#define INTR_WARN_INS_STOP_MODE BIT(7)
> #define INTR_IBI_RING_FULL BIT(6)
> #define INTR_TRANSFER_ABORT BIT(5)
>
> @@ -278,7 +277,6 @@ static int hci_dma_init(struct i3c_hci *hci)
> INTR_TRANSFER_COMPLETION |
> INTR_RING_OP |
> INTR_TRANSFER_ERR |
> - INTR_WARN_INS_STOP_MODE |
> INTR_IBI_RING_FULL |
> INTR_TRANSFER_ABORT);
>
> @@ -795,9 +793,6 @@ static bool hci_dma_irq_handler(struct i3c_hci *hci)
> RING_CTRL_RUN_STOP);
> }
> }
> - if (status & INTR_WARN_INS_STOP_MODE)
> - dev_warn_ratelimited(&hci->master.dev,
> - "ring %d: Inserted Stop on Mode Change\n", i);
> if (status & INTR_IBI_RING_FULL)
> dev_err_ratelimited(&hci->master.dev,
> "ring %d: IBI Ring Full Condition\n", i);
> --
> 2.47.2
>
>
> --
> linux-i3c mailing list
> linux-i3c@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-i3c
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2025-09-12 14:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 10:30 [PATCH 0/5] i3c: mipi-i3c-hci: Convert DBG() prints to dev_dbg() Jarkko Nikula
2025-08-27 10:30 ` [PATCH 1/5] i3c: mipi-i3c-hci: Change interrupt status " Jarkko Nikula
2025-09-12 14:22 ` Frank Li
2025-08-27 10:30 ` [PATCH 2/5] i3c: mipi-i3c-hci: Remove nonexistent ring interrupt Jarkko Nikula
2025-09-12 14:23 ` Frank Li [this message]
2025-08-27 10:30 ` [PATCH 3/5] i3c: mipi-i3c-hci: Uniform ring number printouts Jarkko Nikula
2025-09-12 14:23 ` Frank Li
2025-08-27 10:30 ` [PATCH 4/5] i3c: mipi-i3c-hci: Remove function enter DBG() printouts Jarkko Nikula
2025-09-12 14:27 ` Frank Li
2025-08-27 10:30 ` [PATCH 5/5] i3c: mipi-i3c-hci: Convert remaining DBG() prints to dev_dbg() Jarkko Nikula
2025-09-12 14:31 ` Frank Li
2025-09-15 8:06 ` Jarkko Nikula
2025-09-15 8:14 ` Alexandre Belloni
2025-09-15 8:18 ` Jarkko Nikula
2025-09-12 7:25 ` [PATCH 0/5] i3c: mipi-i3c-hci: Convert " Jarkko Nikula
2025-09-14 20:30 ` Alexandre Belloni
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=aMQs3P9BNOMt/lve@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i3c@lists.infradead.org \
/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