Home
last modified time | relevance | path

Searched full:deduced (Results 1 – 25 of 35) sorted by relevance

12

/linux/Documentation/ABI/testing/
H A Dsysfs-devices-removable14 "unknown" The information is unavailable / cannot be deduced.
/linux/drivers/usb/dwc2/
H A DKconfig96 for which the transfer type cannot be deduced.
/linux/drivers/gpu/drm/imagination/
H A Dpvr_drv.h49 * @_obj_name: The name of the object. Cannot be a typename - this is deduced.
/linux/fs/coda/
H A Dcoda_linux.c140 * looked at. The BSD type field needs to be deduced from linux
/linux/Documentation/devicetree/bindings/pci/
H A Dbrcm,stb-pcie.yaml94 this information cannot be deduced from the dma-ranges.
/linux/drivers/thermal/
H A Dcpuidle_cooling.c41 * The formula is deduced as follows:
/linux/drivers/mtd/nand/raw/
H A Dnand_timings.c664 * 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()
/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A Dpipeline.json432 …s is in DCU and connected to Umask 1. Miss Pending demand load should be deduced by OR-ing increme…
450 …ead, increment by 1. Note this is connect to Umask 2. No dispatch can be deduced from the UOPS_EXE…
459 …n DCU and connected to Umask 1 and 2. Miss Pending demand load should be deduced by OR-ing increme…
/linux/tools/perf/pmu-events/arch/x86/sandybridge/
H A Dpipeline.json441 …s is in DCU and connected to Umask 1. Miss Pending demand load should be deduced by OR-ing increme…
459 …ead, increment by 1. Note this is connect to Umask 2. No dispatch can be deduced from the UOPS_EXE…
468 …n DCU and connected to Umask 1 and 2. Miss Pending demand load should be deduced by OR-ing increme…
/linux/arch/powerpc/kvm/
H A Dbook3s_xive.h230 * Currently, the VP identifiers are deduced from the vCPU id using
/linux/tools/testing/selftests/rcutorture/bin/
H A Dkvm-test-1-run.sh20 # the default values. The "-smp" value is deduced from the contents of
/linux/Documentation/usb/
H A Dmass-storage.rst134 be deduced from the number of files specified in the “file”
/linux/Documentation/networking/
H A Dkcm.rst75 of a received message can be deduced from the application protocol header
H A Dscaling.rst449 of CPU to queues is automatically deduced from the IRQ affinities
/linux/Documentation/admin-guide/mm/
H A Dpagemap.rst204 In user space, whether the page is present, swapped or none can be deduced with
/linux/drivers/gpu/drm/atmel-hlcdc/
H A Datmel_hlcdc_plane.c39 * @bpp: bytes per pixel deduced from pixel_format
43 * @nplanes: number of planes (deduced from pixel_format)
/linux/drivers/platform/surface/
H A Dsurface3_power.c30 * . the various registers semantic as been deduced by observing the register
/linux/Documentation/input/
H A Devent-codes.rst349 considered undefined and the device type should be deduced in the
/linux/drivers/gpu/drm/vmwgfx/
H A Dvmwgfx_so.c303 * @view_type: The view type deduced from the view create command.
/linux/drivers/iio/adc/
H A Dad4130.c849 * The ODR divider is not explicitly specified, but it can be deduced based
857 * mode can be deduced from the same table.
/linux/drivers/gpu/drm/vboxvideo/
H A Dvbox_mode.c132 * If so then screen layout can be deduced from the crtc offsets. in vbox_set_up_input_mapping()
/linux/kernel/irq/
H A Dtimings.c341 * suffix is deduced from the first n-period bytes of in irq_timings_next_event_index()
/linux/include/linux/
H A Dfsnotify_backend.h445 * The type of watched object can be deduced from the iterator type, but not
/linux/fs/resctrl/
H A Dpseudo_lock.c214 * required for pseudo-locking is deduced from this data and &struct
/linux/drivers/i2c/busses/
H A Di2c-at91-master.c765 * deduced from buffer length, so the XDMAC is triggered properly to in at91_twi_configure_dma()

12