search for: rm_control

...r (struct nvfw_gsp_rpc), which maintains the info > + * of the RPC. E.g., the RPC function number. > + * > + * - The payload, where the RPC message stays. E.g. the params of a > + * specific RPC function. Some RPC functions also have their headers > + * in the payload. E.g. rm_alloc, rm_control. > + * > + * The memory layout of a GSP message element can be illustrated below: > + * > + * +------------------------+ > + * | Message Element Header | > + * | (r535_gsp_msg) | > + * | | > + * | (r535_gsp_msg.data) | > + * | |...

Hi folks: Here is the leftover of the previous spin of NVKM GSP RPC fixes, which is handling the return of large GSP message. PATCH 1 and 2 in the previous spin were merged [1], and this spin is based on top of PATCH 1 and PATCH 2 in the previous spin. Besides the support of the large GSP message, kernel doc and many cleanups are introduced according to the comments in the previous spin [2].