Searched full:deduced (Results 1 – 25 of 45) sorted by relevance
12
14 "unknown" The information is unavailable / cannot be deduced.
96 for which the transfer type cannot be deduced.
74 this information cannot be deduced from the dma-ranges.
137 * looked at. The BSD type field needs to be deduced from linux
40 * The formula is deduced as follows:
60 * smaller period than the one deduced from the nominal CPU in watchdog_update_hrtimer_threshold()
664 * Initialize timings that cannot be deduced from timing mode: in onfi_fill_sdr_interface_config()700 * Initialize timings that cannot be deduced from timing mode: in onfi_fill_nvddr_interface_config()
230 * Currently, the VP identifiers are deduced from the vCPU id using
65 and deduced from the APIC IDs of the cores in the package.
19 # the default values. The "-smp" value is deduced from the contents of
211 In user space, whether the page is present, swapped or none can be deduced with
134 be deduced from the number of files specified in the “file”
39 * @bpp: bytes per pixel deduced from pixel_format43 * @nplanes: number of planes (deduced from pixel_format)
693 semantics is welcomed. One project deduced Kconfig semantics through695 the deduced semantics matches our intended Kconfig design goals.
476 …s is in DCU and connected to Umask 1. Miss Pending demand load should be deduced by OR-ing increme…496 …ead, increment by 1. Note this is connect to Umask 2. No dispatch can be deduced from the UOPS_EXE…506 …n DCU and connected to Umask 1 and 2. Miss Pending demand load should be deduced by OR-ing increme…
486 …s is in DCU and connected to Umask 1. Miss Pending demand load should be deduced by OR-ing increme…506 …ead, increment by 1. Note this is connect to Umask 2. No dispatch can be deduced from the UOPS_EXE…516 …n DCU and connected to Umask 1 and 2. Miss Pending demand load should be deduced by OR-ing increme…
75 of a received message can be deduced from the application protocol header
383 of CPU to queues is automatically deduced from the IRQ affinities
30 * . the various registers semantic as been deduced by observing the register
156 be deduced from purely the line level and the value of the ISPENDR
46 * In the final case, usually for the purposes of type matching, it is deduced
349 considered undefined and the device type should be deduced in the
301 * @view_type: The view type deduced from the view create command.
260 * Only set @dev_parent if that can't be deduced from @v4l2_dev.
132 * If so then screen layout can be deduced from the crtc offsets. in vbox_set_up_input_mapping()
