Searched refs:mem_region_info (Results 1 – 3 of 3) sorted by relevance
161 if (resp->mem_region_info[i].size > priv->msa_mem_size || in wlfw_msa_mem_info_send_sync_msg()162 resp->mem_region_info[i].region_addr >= max_mapped_addr || in wlfw_msa_mem_info_send_sync_msg()163 resp->mem_region_info[i].region_addr < priv->msa_pa || in wlfw_msa_mem_info_send_sync_msg()164 resp->mem_region_info[i].size + in wlfw_msa_mem_info_send_sync_msg()165 resp->mem_region_info[i].region_addr > max_mapped_addr) { in wlfw_msa_mem_info_send_sync_msg()167 resp->mem_region_info[i].region_addr, in wlfw_msa_mem_info_send_sync_msg()168 resp->mem_region_info[i].size); in wlfw_msa_mem_info_send_sync_msg()174 resp->mem_region_info[i].region_addr; in wlfw_msa_mem_info_send_sync_msg()176 resp->mem_region_info[i].size; in wlfw_msa_mem_info_send_sync_msg()178 resp->mem_region_info[i].secure_flag; in wlfw_msa_mem_info_send_sync_msg()
878 struct wlfw_memory_region_info_s_v01 mem_region_info[QMI_WLFW_MAX_NUM_MEMORY_REGIONS_V01]; member
3184 mem_region_info),