From: Md Shofiqul Islam <shofiqtest@gmail.com>
To: maciej.falkowski@linux.intel.com
Cc: karol.wachowski@linux.intel.com, dri-devel@lists.freedesktop.org
Subject: [PATCH RFC] accel/ivpu: set IPC data_size to per-message payload size
Date: Tue, 19 May 2026 13:47:22 -0700 (PDT) [thread overview]
Message-ID: <6a0ccc5a.1f370a67.11b6d4.de1b@mx.google.com> (raw)
Hi Maciej, Karol,
I noticed the TODO at ivpu_ipc.c:100 regarding setting data_size to the
actual JSM message size rather than sizeof(full union). I'd like to work
on this.
My proposed approach: add a u32 msg_size parameter to ivpu_ipc_send() and
ivpu_ipc_tx_prepare(), passing offsetof(struct vpu_jsm_msg, payload) +
sizeof() of the specific payload from each call site in ivpu_jsm_msg.c.
Before proceeding -- is there a firmware compatibility constraint that
intentionally kept this at sizeof(struct vpu_jsm_msg)? And is this the
right tree (drm/misc/kernel) for this change?
Background: I'm a Linux kernel contributor (IIO/ASoC/SCSI patches
upstream) interested in the accel/NPU subsystem.
Regards,
Md Shofiqul Islam
reply other threads:[~2026-05-20 7:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6a0ccc5a.1f370a67.11b6d4.de1b@mx.google.com \
--to=shofiqtest@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=karol.wachowski@linux.intel.com \
--cc=maciej.falkowski@linux.intel.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