Searched full:deduced (Results 1 – 25 of 74) sorted by relevance
123
94 for which the transfer type cannot be deduced.
96 for which the transfer type cannot be deduced.
82 this information cannot be deduced from the dma-ranges.
119 * looked at. The BSD type field needs to be deduced from linux
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()
42 * The formula is deduced as follows:
52 and deduced from the APIC IDs of the cores in the package.
308 * Initialize timings that cannot be deduced from timing mode: in onfi_fill_data_interface()
65 and deduced from the APIC IDs of the cores in the package.
128 be deduced from the number of files specified in the “file”
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
372 * Initialize timings that cannot be deduced from timing mode: in onfi_fill_interface_config()
143 be deduced from purely the line level and the value of the ISPENDR
18 # the default values. The "-smp" value is deduced from the contents of
673 semantics is welcomed. One project deduced Kconfig semantics through675 the deduced semantics matches our intended Kconfig design goals.
622 semantics is welcomed. One project deduced Kconfig semantics through624 the deduced semantics matches our intended Kconfig design goals.
37 * @bpp: bytes per pixel deduced from pixel_format41 * @nplanes: number of planes (deduced from pixel_format)
289 * each attribute is of the form below. Total array length is deduced
38 * @bpp: bytes per pixel deduced from pixel_format42 * @nplanes: number of planes (deduced from pixel_format)
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…
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…
709 …ead, increment by 1. Note this is connect to Umask 2. No dispatch can be deduced from the UOPS_EXE…719 …s is in DCU and connected to Umask 1. Miss Pending demand load should be deduced by OR-ing increme…739 …n DCU and connected to Umask 1 and 2. Miss Pending demand load should be deduced by OR-ing increme…