From: Badal Nilawar <badal.nilawar@intel.com>
To: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Cc: anshuman.gupta@intel.com, rodrigo.vivi@intel.com,
alexander.usyskin@intel.com, gregkh@linuxfoundation.org,
daniele.ceraolospurio@intel.com, mika.westerberg@linux.intel.com,
lucas.demarchi@intel.com, karthik.poosa@intel.com
Subject: [PATCH v9 1/9] mei: bus: add mei_cldev_mtu interface
Date: Fri, 5 Sep 2025 21:19:45 +0530 [thread overview]
Message-ID: <20250905154953.3974335-2-badal.nilawar@intel.com> (raw)
In-Reply-To: <20250905154953.3974335-1-badal.nilawar@intel.com>
From: Alexander Usyskin <alexander.usyskin@intel.com>
Add a new helper function that allows MEI client drivers
to query the maximum transmission unit (MTU) for a connected
MEI client.
This is useful for clients that need to transmit large payloads,
such as firmware blobs, allowing them to determine the maximum
message size that can be safely sent before starting transmission and
size of the buffer to allocate when receiving data.
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>
Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
---
drivers/misc/mei/bus.c | 13 +++++++++++++
include/linux/mei_cl_bus.h | 1 +
2 files changed, 14 insertions(+)
diff --git a/drivers/misc/mei/bus.c b/drivers/misc/mei/bus.c
index 5cc3ad07d5be..09aae8f9d225 100644
--- a/drivers/misc/mei/bus.c
+++ b/drivers/misc/mei/bus.c
@@ -614,6 +614,19 @@ u8 mei_cldev_ver(const struct mei_cl_device *cldev)
}
EXPORT_SYMBOL_GPL(mei_cldev_ver);
+/**
+ * mei_cldev_mtu - max message that client can send and receive
+ *
+ * @cldev: mei client device
+ *
+ * Return: mtu or 0 if client is not connected
+ */
+size_t mei_cldev_mtu(const struct mei_cl_device *cldev)
+{
+ return mei_cl_mtu(cldev->cl);
+}
+EXPORT_SYMBOL_GPL(mei_cldev_mtu);
+
/**
* mei_cldev_enabled - check whether the device is enabled
*
diff --git a/include/linux/mei_cl_bus.h b/include/linux/mei_cl_bus.h
index 725fd7727422..a82755e1fc40 100644
--- a/include/linux/mei_cl_bus.h
+++ b/include/linux/mei_cl_bus.h
@@ -113,6 +113,7 @@ int mei_cldev_register_notif_cb(struct mei_cl_device *cldev,
mei_cldev_cb_t notif_cb);
u8 mei_cldev_ver(const struct mei_cl_device *cldev);
+size_t mei_cldev_mtu(const struct mei_cl_device *cldev);
void *mei_cldev_get_drvdata(const struct mei_cl_device *cldev);
void mei_cldev_set_drvdata(struct mei_cl_device *cldev, void *data);
--
2.34.1
next prev parent reply other threads:[~2025-09-05 15:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 15:49 [PATCH v9 0/9] Introducing firmware late binding Badal Nilawar
2025-09-05 15:49 ` Badal Nilawar [this message]
2025-09-05 15:49 ` [PATCH v9 2/9] mei: late_bind: add late binding component driver Badal Nilawar
2025-09-08 16:25 ` Lucas De Marchi
2025-09-09 4:50 ` Usyskin, Alexander
2025-09-09 14:43 ` Lucas De Marchi
2025-09-12 5:19 ` Lucas De Marchi
2025-09-18 15:41 ` Rodrigo Vivi
2025-09-18 16:27 ` gregkh
2025-09-05 15:49 ` [PATCH v9 3/9] drm/xe/xe_late_bind_fw: Introduce xe_late_bind_fw Badal Nilawar
2025-09-05 15:49 ` [PATCH v9 4/9] drm/xe/xe_late_bind_fw: Initialize late binding firmware Badal Nilawar
2025-09-05 15:49 ` [PATCH v9 5/9] drm/xe/xe_late_bind_fw: Load " Badal Nilawar
2025-09-05 15:49 ` [PATCH v9 6/9] drm/xe/xe_late_bind_fw: Reload late binding fw in rpm resume Badal Nilawar
2025-09-05 15:49 ` [PATCH v9 7/9] drm/xe/xe_late_bind_fw: Reload late binding fw during system resume Badal Nilawar
2025-09-05 15:49 ` [PATCH v9 8/9] drm/xe/xe_late_bind_fw: Introduce debug fs node to disable late binding Badal Nilawar
2025-09-05 15:49 ` [PATCH v9 9/9] drm/xe/xe_late_bind_fw: Extract and print version info Badal Nilawar
2025-09-24 20:44 ` Kees Bakker
2025-09-25 12:09 ` Nilawar, Badal
2025-09-05 16:08 ` ✗ CI.checkpatch: warning for Introducing firmware late binding Patchwork
2025-09-05 16:09 ` ✓ CI.KUnit: success " Patchwork
2025-09-05 16:24 ` ✗ CI.checksparse: warning " Patchwork
2025-09-05 16:51 ` ✓ Xe.CI.BAT: success " Patchwork
2025-09-06 2:54 ` ✓ Xe.CI.Full: " Patchwork
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=20250905154953.3974335-2-badal.nilawar@intel.com \
--to=badal.nilawar@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rodrigo.vivi@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