Hi Sidong,

On 12/11/26 14:11, Sidong Yang wrote:
diff --git a/drivers/accel/rocket/rocket_drv.c b/drivers/accel/rocket/ rocket_drv.c
index 5d7805c41dc3..351be60b1228 100644
--- a/drivers/accel/rocket/rocket_drv.c
+++ b/drivers/accel/rocket/rocket_drv.c
@@ -3,8 +3,10 @@
#include <drm/drm_accel.h>
  #include <drm/drm_drv.h>
+#include <drm/drm_file.h>
  #include <drm/drm_gem.h>
  #include <drm/drm_ioctl.h>
+#include <drm/drm_print.h>
  #include <drm/rocket_accel.h>
  #include <linux/clk.h>
  #include <linux/err.h>
@@ -139,7 +141,23 @@ static const struct drm_ioctl_desc 
rocket_drm_driver_ioctls[] = {
        ROCKET_IOCTL(FINI_BO, fini_bo),
  };
-DEFINE_DRM_ACCEL_FOPS(rocket_accel_driver_fops); +static void rocket_show_fdinfo(struct drm_printer *p, struct drm_file *file)
+{
+ struct rocket_device *rdev = to_rocket_device(file->minor->dev);
+ struct rocket_file_priv *rocket_priv = file->driver_priv;
+
+ drm_printf(p, "drm-engine-npu:\t%llu ns\n",
+ drm_sched_entity_get_runtime(&rocket_priv->sched_entity));
+ drm_printf(p, "drm-engine-capacity-npu:\t%u\n", rdev->max_cores);

Does it make sense to expose the capacity of a core that it's not
actually initialized and in use?

Best regards,
- Maíra

Reply via email to