Searched refs:expert (Results 1 – 9 of 9) sorted by relevance
449 struct vpu_enc_expert_mode_param *expert; member539 return hcs->ctrls[instance].expert; in get_expert_param()612 hcs->ctrls[i].expert = rpc->virt + offset; in vpu_windsor_init_rpc()858 struct vpu_enc_expert_mode_param *expert; in vpu_windsor_config_stream_buffer() local861 expert = get_expert_param(shared, instance); in vpu_windsor_config_stream_buffer()868 expert->calib_param.mem_chunk_phys_addr = 0; in vpu_windsor_config_stream_buffer()869 expert->calib_param.mem_chunk_virt_addr = 0; in vpu_windsor_config_stream_buffer()870 expert->calib_param.mem_chunk_size = 0; in vpu_windsor_config_stream_buffer()871 expert->calib_param.cb_base = buf->phys; in vpu_windsor_config_stream_buffer()872 expert->calib_param.cb_size = buf->length; in vpu_windsor_config_stream_buffer()[all …]
163 - If an expert who is required to handle an issue is employed by a listed165 request the disclosure of that expert from that entity. This ensures166 that the expert is also part of the entity's response team.203 If an expert is employed by or a member of an entity on the disclosure list215 After the incident team acknowledges or resolves an objection, the expert
5 to expert both in kernel hacking and in understanding LKMM.
267 Sadly these things happen, but luckily not very often; if they occur, expert
1546 bool "Configure standard kernel features (expert users)"1877 # end of the "standard kernel features (expert users)" menu
193 :Debugging information: written to syslog (expert only)
213 :Debugging information: written to syslog (expert only)
27 refactorings already and are an expert in the specific area
944 # Mark as expert because too many people got it wrong.