7 Jun
2026
7 Jun
'26
9:17 p.m.
On Thu, Jun 04, 2026 at 10:47:13AM +0530, Ekansh Gupta wrote:
On 20-05-2026 19:30, Dmitry Baryshkov wrote:
On Tue, May 19, 2026 at 11:46:03AM +0530, Ekansh Gupta via B4 Relay wrote:
+/**
- qda_ioctl_init_create() - Create a DSP process
- @dev: DRM device structure
- @data: User-space data (struct drm_qda_init_create)
- @file_priv: DRM file private data
- Return: 0 on success, negative error code on failure
- */
+int qda_ioctl_init_create(struct drm_device *dev, void *data, struct drm_file *file_priv) +{
- return fastrpc_invoke(FASTRPC_RMID_INIT_CREATE, dev, data, file_priv);
Where is INIT_CREATE_ATTR, which you described earlier?
INIT_CREATE_ATTR is used while `sc` creation so the DSP considers the request is coming with some attributes, the ioctl functions are going to be the same in both the cases, so keeping it unchanged and the decision is taken while `sc` is getting created.>
Ack, I missed it earlier.
--
With best wishes
Dmitry