From: "Wachowski, Karol" <karol.wachowski@linux.intel.com>
To: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>,
dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, jeff.hugo@oss.qualcomm.com,
andrzej.kacprowski@linux.intel.com, lizhi.hou@amd.com
Subject: Re: [PATCH] accel/ivpu: Document why full JSM message size is always used
Date: Mon, 25 May 2026 10:09:00 +0200 [thread overview]
Message-ID: <d282fa34-218d-4396-85ae-98e040f0f356@linux.intel.com> (raw)
In-Reply-To: <f0a5dbaa-c6bc-484e-8459-eca457c9f617@linux.intel.com>
On 25-May-26 9:44, Dawid Osuchowski wrote:
> On 2026-05-22 11:32 AM, Karol Wachowski wrote:
>> Firmware expects IPC messages to always carry the full fixed
>> sizeof(struct vpu_jsm_msg) size. Sending the full struct also
>> ensures unused fields are zeroed, which maintains compatibility
>> when existing commands are extended with new fields in the future.
>>
>> Replace the misleading TODO comment with an explanation of the
>> actual intent.
>>
>> Signed-off-by: Karol Wachowski <karol.wachowski@linux.intel.com>
>
> Reviewed-by: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
Thanks, applied to drm-misc-next.
>
>> ---
>> drivers/accel/ivpu/ivpu_ipc.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/accel/ivpu/ivpu_ipc.c b/drivers/accel/ivpu/
>> ivpu_ipc.c
>> index f47df092bb0d..9f1ba0c57442 100644
>> --- a/drivers/accel/ivpu/ivpu_ipc.c
>> +++ b/drivers/accel/ivpu/ivpu_ipc.c
>> @@ -97,7 +97,11 @@ ivpu_ipc_tx_prepare(struct ivpu_device *vdev,
>> struct ivpu_ipc_consumer *cons,
>> memset(tx_buf, 0, sizeof(*tx_buf));
>> tx_buf->ipc.data_addr = jsm_vpu_addr;
>> - /* TODO: Set data_size to actual JSM message size, not union of
>> all messages */
>> + /*
>> + * Firmware expects full JSM message size regardless of the
>> payload size.
>> + * Unused fields must be zeroed to allow future extensions of
>> existing
>> + * commands without breaking compatibility.
>> + */
>> tx_buf->ipc.data_size = sizeof(*req);
>> tx_buf->ipc.channel = cons->channel;
>> tx_buf->ipc.src_node = 0;
>
next prev parent reply other threads:[~2026-05-25 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 9:32 [PATCH] accel/ivpu: Document why full JSM message size is always used Karol Wachowski
2026-05-25 7:44 ` Dawid Osuchowski
2026-05-25 8:09 ` Wachowski, Karol [this message]
2026-05-25 9:04 ` Claude review: " Claude Code Review Bot
2026-05-25 9:04 ` Claude Code Review Bot
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=d282fa34-218d-4396-85ae-98e040f0f356@linux.intel.com \
--to=karol.wachowski@linux.intel.com \
--cc=andrzej.kacprowski@linux.intel.com \
--cc=dawid.osuchowski@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=lizhi.hou@amd.com \
--cc=oded.gabbay@gmail.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