Home
last modified time | relevance | path

Searched full:supposed (Results 1 – 25 of 657) sorted by relevance

12345678910>>...27

/Linux-v5.4/sound/hda/
Dhdac_component.c27 * This function is supposed to be used only by a HD-audio controller
115 * This function is supposed to be used only by a HD-audio controller
150 * This function is supposed to be used only by a HD-audio controller
244 * This function is supposed to be used only by a HD-audio controller
268 * This function is supposed to be used only by a HD-audio controller
322 * This function is supposed to be used only by a HD-audio controller
/Linux-v5.4/drivers/usb/core/
Dotg_whitelist.h22 /* FIXME actually, printers are NOT supposed to use device classes;
23 * they're supposed to use interface classes...
/Linux-v5.4/drivers/of/
Dof_net.c77 * checked first, because that is supposed to contain to "most recent" MAC
84 * Note that the 'address' property is supposed to contain a virtual address of
/Linux-v5.4/include/linux/mailbox/
Dzynqmp-ipi-message.h13 * Client is supposed to be aware of this.
/Linux-v5.4/drivers/i3c/
DKconfig9 It's supposed to be backward compatible with I2C while providing
/Linux-v5.4/arch/powerpc/platforms/52xx/
Dlite5200.c49 * Firmware is supposed to be responsible for this. If you are creating a
83 * Firmware is supposed to be responsible for this. If you are creating a
/Linux-v5.4/drivers/staging/sm750fb/
DTODO7 are supposed to be sample code which is given here if someone wants to
/Linux-v5.4/include/linux/soc/ti/
Dti-msgmgr.h28 * on SoC. Client is supposed to be aware of this.
/Linux-v5.4/arch/arm/mach-pxa/
Dmioa701_bootresume.S26 orr r0, r0, #0x00200000 @ even if it's supposed to
/Linux-v5.4/drivers/misc/mic/common/
Dmic_dev.h46 * These values are supposed to be in the config_change field of the
/Linux-v5.4/include/uapi/linux/
Dkcov.h17 * was supposed to be 0 in such a call. So, for reasons of backward
/Linux-v5.4/Documentation/input/
Dgamepad.rst12 document defines how gamepads are supposed to report their data.
79 All new gamepads are supposed to comply with this mapping. Please report any
/Linux-v5.4/include/linux/usb/
Diowarrior.h18 /* vendor id : supposed to be USB_VENDOR_ID_CODEMERCS in all cases */
/Linux-v5.4/drivers/pci/
Dpci-pf-stub.c15 * This table provides the list of IDs this driver is supposed to bind
/Linux-v5.4/Documentation/devicetree/bindings/hsi/
Dclient-devices.txt1 Each HSI port is supposed to have one child node, which
/Linux-v5.4/fs/sysv/
Dballoc.c53 * free list). As AFS is supposed to be read-only no one in sysv_free_block()
171 * free list). As AFS is supposed to be read-only we just in sysv_count_free_blocks()
/Linux-v5.4/arch/s390/include/asm/
Dvdso.h17 * structure is supposed to be known only to the function in the vdso
/Linux-v5.4/tools/testing/selftests/kvm/
Dkvm_create_max_vcpus.c52 * Userspace is supposed to use KVM_CAP_MAX_VCPUS as the maximum ID in main()
/Linux-v5.4/include/linux/
Ddrbd_genl_api.h18 * to know which volume number within the resource this is supposed to be.
/Linux-v5.4/arch/arm/boot/dts/
Dsun5i-gr8-evb.dts310 * pin supposed to control VBUS, an ID pin, a VBUS detect pin,
313 * Except that the pin supposed to control VBUS is not
/Linux-v5.4/arch/ia64/lib/
Dclear_user.S47 // tail is to stay semantically correct. This routine is not supposed
78 // the various counters compared to how long the loop is supposed
/Linux-v5.4/Documentation/devicetree/bindings/net/
Dmarvell-armada-370-neta.txt30 Obligatory, when the port is supposed to use hardware
/Linux-v5.4/Documentation/firmware-guide/acpi/
Dgpio-properties.rst131 available to the driver can be used to identify the device and that is supposed
134 the driver is supposed to know what to use the GpioIo()/GpioInt() resources for
/Linux-v5.4/drivers/block/drbd/
DKconfig25 On the node with the primary device the application is supposed to
/Linux-v5.4/arch/powerpc/include/asm/
Ddelay.h23 * is supposed to take 1ms, the hypervisor could sleep our partition for

12345678910>>...27