Use correct channel for dyndbg JSM message.

Signed-off-by: Jacek Lawrynowicz <jacek.lawrynow...@linux.intel.com>
Reviewed-by: Karol Wachowski <karol.wachow...@intel.com>
---
 drivers/accel/ivpu/ivpu_jsm_msg.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/accel/ivpu/ivpu_jsm_msg.c 
b/drivers/accel/ivpu/ivpu_jsm_msg.c
index ae91ad24d10d8..494ebc2475b19 100644
--- a/drivers/accel/ivpu/ivpu_jsm_msg.c
+++ b/drivers/accel/ivpu/ivpu_jsm_msg.c
@@ -197,7 +197,7 @@ int ivpu_jsm_dyndbg_control(struct ivpu_device *vdev, char 
*command, size_t size
        strscpy(req.payload.dyndbg_control.dyndbg_cmd, command, 
VPU_DYNDBG_CMD_MAX_LEN);
 
        ret = ivpu_ipc_send_receive(vdev, &req, VPU_JSM_MSG_DYNDBG_CONTROL_RSP, 
&resp,
-                                   VPU_IPC_CHAN_ASYNC_CMD, vdev->timeout.jsm);
+                                   VPU_IPC_CHAN_GEN_CMD, vdev->timeout.jsm);
        if (ret)
                ivpu_warn_ratelimited(vdev, "Failed to send command \"%s\": ret 
%d\n",
                                      command, ret);
-- 
2.45.1

Reply via email to