From: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
linux-i3c@lists.infradead.org
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Guruvendra Punugupati <Guruvendra.Punugupati@amd.com>,
Krishnamoorthi M <krishnamoorthi.m@amd.com>
Subject: Re: [PATCH 0/2] i3c: mipi-i3c-hci: DMA interrupt fixes
Date: Mon, 23 Sep 2024 13:09:58 +0530 [thread overview]
Message-ID: <66ff9903-78d6-4079-8445-6e01d9aa39f0@amd.com> (raw)
In-Reply-To: <20240920144432.62370-1-jarkko.nikula@linux.intel.com>
Hi Jarkko,
On 9/20/2024 20:14, Jarkko Nikula wrote:
> Hi
>
> These are targeted for the v6.13 cycle, i.e for the i3c/next branch
> after v6.12-rc1 is tagged.
>
> Patch 1/2 is stable looking material but I think it gets visible only
> after patch 2/2 on a MIPI I3C HCI v1.0+ compatible HW so in my opinnion
> should go through normal development cycle.
>
> AMD folks: You said you have non-functional DMA mode on your HW. Can the
> patch 2/2 make it functional or are there some other than interrupt
> issues?
>
These are RTL issues within the hardware. I don't believe the patch
will help since the DMA mode never activates (at least with the
current ASIC).
Thanks,
Shyam
> Jarkko Nikula (2):
> i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request
> i3c: mipi-i3c-hci: Handle interrupts according to current
> specifications
>
> drivers/i3c/master/mipi-i3c-hci/core.c | 16 +++-------------
> drivers/i3c/master/mipi-i3c-hci/dma.c | 10 +++-------
> drivers/i3c/master/mipi-i3c-hci/hci.h | 2 +-
> drivers/i3c/master/mipi-i3c-hci/pio.c | 2 +-
> 4 files changed, 8 insertions(+), 22 deletions(-)
>
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2024-09-23 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 14:44 [PATCH 0/2] i3c: mipi-i3c-hci: DMA interrupt fixes Jarkko Nikula
2024-09-20 14:44 ` [PATCH 1/2] i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request Jarkko Nikula
2024-09-20 14:44 ` [PATCH 2/2] i3c: mipi-i3c-hci: Handle interrupts according to current specifications Jarkko Nikula
2024-09-23 7:39 ` Shyam Sundar S K [this message]
2024-10-31 23:06 ` [PATCH 0/2] i3c: mipi-i3c-hci: DMA interrupt fixes 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=66ff9903-78d6-4079-8445-6e01d9aa39f0@amd.com \
--to=shyam-sundar.s-k@amd.com \
--cc=Guruvendra.Punugupati@amd.com \
--cc=alexandre.belloni@bootlin.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=krishnamoorthi.m@amd.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