From: Jamin Lin <jamin_lin@aspeedtech.com>
To: "jithu.joseph@oss.qualcomm.com" <jithu.joseph@oss.qualcomm.com>,
"clg@kaod.org" <clg@kaod.org>,
"nabihestefan@google.com" <nabihestefan@google.com>,
"komlodi@google.com" <komlodi@google.com>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Cc: Jamin Lin <jamin_lin@aspeedtech.com>,
Troy Lee <troy_lee@aspeedtech.com>,
Kane Chen <kane_chen@aspeedtech.com>
Subject: [PATCH v1 2/4] hw/i3c/mock-i3c-target: Set num_sent in TX callback to fix trace reporting
Date: Mon, 2 Mar 2026 03:26:31 +0000 [thread overview]
Message-ID: <20260302032626.1974743-3-jamin_lin@aspeedtech.com> (raw)
In-Reply-To: <20260302032626.1974743-1-jamin_lin@aspeedtech.com>
mock_i3c_target_tx() did not update *num_sent before returning.
Although some callers may not directly use this value, i3c_send()
passes num_sent to trace_i3c_send(). If the target TX callback does
not initialize *num_sent, the trace output may report an incorrect
or uninitialized value, leading to confusing debugging information.
For example, the following trace was observed:
mock_i3c_target_tx I3C mock target write 0x12
i3c_send I3C send 0/1 bytes, ack=1 (expected 1/1 bytes)
This happens because *num_sent was never set by the TX callback.
Fix this by setting:
*num_sent = to_write;
so that the actual number of transmitted bytes is correctly
propagated back to i3c_send() and reflected in trace output.
Signed-off-by: Jamin Lin <jamin_lin@aspeedtech.com>
---
hw/i3c/mock-i3c-target.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/i3c/mock-i3c-target.c b/hw/i3c/mock-i3c-target.c
index 875cd7c7d0..5c913ee49b 100644
--- a/hw/i3c/mock-i3c-target.c
+++ b/hw/i3c/mock-i3c-target.c
@@ -86,6 +86,7 @@ static int mock_i3c_target_tx(I3CTarget *i3c, const uint8_t *data,
s->buf[s->p_buf] = data[i];
s->p_buf++;
}
+ *num_sent = to_write;
return ret;
}
--
2.43.0
next prev parent reply other threads:[~2026-03-02 3:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 3:26 [PATCH v1 0/4] hw/i3c: Trace fixes and readability improvements from review feedback Jamin Lin
2026-03-02 3:26 ` [PATCH v1 1/4] hw/i3c/dw-i3c: Use ROUND_UP() for RX buffer allocation alignment Jamin Lin
2026-03-02 21:46 ` Jithu Joseph
2026-03-02 3:26 ` Jamin Lin [this message]
2026-03-02 21:38 ` [PATCH v1 2/4] hw/i3c/mock-i3c-target: Set num_sent in TX callback to fix trace reporting Jithu Joseph
2026-03-03 1:17 ` Jamin Lin
2026-03-02 3:26 ` [PATCH v1 3/4] hw/i3c/core: Initialize num_sent in i3c_send_byte() Jamin Lin
2026-03-02 22:44 ` Jithu Joseph
2026-03-02 3:26 ` [PATCH v1 4/4] hw/i3c/mock-i3c-target: Simplify GETMRL byte extraction logic Jamin Lin
2026-03-03 0:00 ` Jithu Joseph
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=20260302032626.1974743-3-jamin_lin@aspeedtech.com \
--to=jamin_lin@aspeedtech.com \
--cc=clg@kaod.org \
--cc=jithu.joseph@oss.qualcomm.com \
--cc=kane_chen@aspeedtech.com \
--cc=komlodi@google.com \
--cc=nabihestefan@google.com \
--cc=qemu-devel@nongnu.org \
--cc=troy_lee@aspeedtech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.