On 9/11/2026 7:41 PM, Ekansh Gupta wrote:
+ /* Map the DMA handle in the invoke call for backward compatibility */
+ FASTRPC_MAP_DMA_HANDLE = 0x20000,
was having a looks again at this, user is never passing this flag,
should we have this in uapi? I think you can move this in kernel as it
is set and used by kernel.> FASTRPC_MAP_MAX,
Agreed, thanks for catching this. FASTRPC_MAP_DMA_HANDLE is only ever
set and consumed internally by the driver to tag DMA handle maps — userspace
never passes it as an input flag — so it doesn't belong in the uapi. I'll move
it to a kernel-internal definition (not exposed via uapi) in the next version,
and drop it from the header.
};
