Searched full:deduced (Results 1 – 25 of 40) sorted by relevance
12
13 "unknown": The information is unavailable / cannot be deduced.
96 for which the transfer type cannot be deduced.
72 this information cannot be deduced from the dma-ranges.
138 * looked at. The BSD type field needs to be deduced from linux
60 * smaller period than the one deduced from the nominal CPU in watchdog_update_hrtimer_threshold()
40 * The formula is deduced as follows:
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()
65 and deduced from the APIC IDs of the cores in the package.
230 * Currently, the VP identifiers are deduced from the vCPU id using
134 be deduced from the number of files specified in the “file”
19 # the default values. The "-smp" value is deduced from the contents of
38 * @bpp: bytes per pixel deduced from pixel_format42 * @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.
706 …ead, increment by 1. Note this is connect to Umask 2. No dispatch can be deduced from the UOPS_EXE…716 …s is in DCU and connected to Umask 1. Miss Pending demand load should be deduced by OR-ing increme…736 …n DCU and connected to Umask 1 and 2. Miss Pending demand load should be deduced by OR-ing increme…
806 …s is in DCU and connected to Umask 1. Miss Pending demand load should be deduced by OR-ing increme…816 …ead, increment by 1. Note this is connect to Umask 2. No dispatch can be deduced from the UOPS_EXE…836 …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
260 * Only set @dev_parent if that can't be deduced from @v4l2_dev.
339 considered undefined and the device type should be deduced in the
304 * @view_type: The view type deduced from the view create command.
130 * If so then screen layout can be deduced from the crtc offsets. in vbox_set_up_input_mapping()
341 * suffix is deduced from the first n-period bytes of in irq_timings_next_event_index()
91 /* PF max speed in Mb/s, deduced from line_speed
