Lines Matching refs:to

9 // Unless required by applicable law or agreed to in writing, software
127 // for conventional HALs, to keep a data structure with one or multiple
147 // similar to TYPE_UNION, but support runtime type check.
183 // To specify an API call to an interface.
189 // HAL driver ID, if set (e.g., >0), use the given driver_id to get the
223 // the HIDL interface ID used to call an API of another nested interface
236 // used to pass the spec of a found HAL_CONVENTIONAL_SUBMODULE to the host.
266 // not a user-provided variable. used by the frameworks to tell the sub
270 // to specify a syscall number.
308 // used for a function pointer to keep its function name.
351 // We use uint64 to represent the address of the hidl_memory pointer,
352 // which allows vtsc to reinterpret the address when caller wants to use
399 // We use uint64 to represent the address of the hidl_handle pointer,
400 // which allows vtsc to reinterpret the address when caller wants to use
465 // when caller wants to use an existing FMQ.
468 // The descriptor can be passed in hidl and be used to create new
469 // FMQ objects. We use uint64 to represent the address of the descriptor,
470 // which allows vtsc to reinterpret the address when callers wants to use
485 // for non HIDL HAL, to use a custom type defined in C/C++.
488 // for non HIDL HAL, to set function pointer(s).
491 // for HIDL HAL, to use a HIDL callback instance.
494 // for HIDL HAL, to specify the HIDL_INTERFACE ID. ID is used between
498 // for HIDL HAL, to specify an HIDL interface's client proxy object's
499 // pointer value. Passed from a DriverBase instance to the VTS HAL driver
501 // case is when this variable is passed to a DriverBase instance from the
552 // To specify a module (which is logically equivalent to a .hal file in case
568 // use two ints to represent major and minor versions separately.
578 // The modules to import (e.g., package_path.component_name).
585 // a list of headers that need to be imported in order to use the component.