Searched full:supposed (Results 1 – 25 of 1389) sorted by relevance
12345678910>>...56
| /kernel/linux/linux-6.6/sound/hda/ |
| D | hdac_component.c | 27 * 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
246 * This function is supposed to be used only by a HD-audio controller
271 * This function is supposed to be used only by a HD-audio controller
326 * This function is supposed to be used only by a HD-audio controller
|
| /kernel/linux/linux-5.10/sound/hda/ |
| D | hdac_component.c | 27 * 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
246 * This function is supposed to be used only by a HD-audio controller
271 * This function is supposed to be used only by a HD-audio controller
326 * This function is supposed to be used only by a HD-audio controller
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pci/ |
| D | snps,dw-pcie.yaml | 125 signal is supposed to be specified for the host controller.
182 supposed to be unmasked in the Root Control register).
191 Status register (the event is supposed to be unmasked in the
196 Status register (the event is supposed to be unmasked in the
|
| D | baikal,bt1-pcie.yaml | 17 control module, so the proper interface initialization is supposed to be
67 clock signal is supposed to be attached to the corresponding Ref-pad
81 A comprehensive controller reset logic is supposed to be implemented
|
| D | snps,dw-pcie-common.yaml | 136 are supposed to reset. Note the platforms may have some of these signals
185 PHYs are supposed to be able to work in the PCIe mode with a speed
224 up link is supposed to be preserved.
|
| /kernel/linux/linux-5.10/drivers/usb/core/ |
| D | otg_productlist.h | 18 /* FIXME actually, printers are NOT supposed to use device classes;
19 * they're supposed to use interface classes...
|
| /kernel/linux/linux-6.6/drivers/usb/core/ |
| D | otg_productlist.h | 18 /* FIXME actually, printers are NOT supposed to use device classes;
19 * they're supposed to use interface classes...
|
| /kernel/linux/linux-5.10/drivers/of/ |
| D | of_net.c | 83 * checked first, because that is supposed to contain to "most recent" MAC
90 * Note that the 'address' property is supposed to contain a virtual address of
|
| /kernel/linux/linux-5.10/drivers/mtd/maps/ |
| D | physmap-bt1-rom.c | 108 /* It's supposed to be read-only MTD. */ in of_flash_probe_bt1_rom()
120 dev_warn(dev, "Bank width is supposed to be 32 bits wide\n"); in of_flash_probe_bt1_rom()
|
| /kernel/linux/linux-6.6/drivers/mtd/maps/ |
| D | physmap-bt1-rom.c | 107 /* It's supposed to be read-only MTD. */ in of_flash_probe_bt1_rom()
119 dev_warn(dev, "Bank width is supposed to be 32 bits wide\n"); in of_flash_probe_bt1_rom()
|
| /kernel/linux/linux-6.6/net/core/ |
| D | of_net.c | 106 * checked first, because that is supposed to contain to "most recent" MAC
113 * Note that the 'address' property is supposed to contain a virtual address of
|
| /kernel/linux/linux-6.6/Documentation/driver-api/tty/ |
| D | tty_driver.rst | 62 put is supposed to free the tty_port including the device's private struct.
65 TTY driver is supposed to register every device discovered in the system
|
| /kernel/linux/linux-5.10/include/linux/mailbox/ |
| D | zynqmp-ipi-message.h | 13 * Client is supposed to be aware of this.
|
| /kernel/linux/linux-6.6/include/linux/mailbox/ |
| D | zynqmp-ipi-message.h | 13 * Client is supposed to be aware of this.
|
| /kernel/linux/linux-5.10/drivers/i3c/ |
| D | Kconfig | 9 It's supposed to be backward compatible with I2C while providing
|
| /kernel/linux/linux-6.6/drivers/i3c/ |
| D | Kconfig | 9 It's supposed to be backward compatible with I2C while providing
|
| /kernel/linux/linux-5.10/arch/powerpc/platforms/52xx/ |
| D | lite5200.c | 49 * 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
|
| /kernel/linux/linux-6.6/arch/powerpc/platforms/52xx/ |
| D | lite5200.c | 48 * Firmware is supposed to be responsible for this. If you are creating a
82 * Firmware is supposed to be responsible for this. If you are creating a
|
| /kernel/linux/linux-5.10/drivers/staging/sm750fb/ |
| D | TODO | 7 are supposed to be sample code which is given here if someone wants to
|
| /kernel/linux/linux-6.6/drivers/staging/sm750fb/ |
| D | TODO | 7 are supposed to be sample code which is given here if someone wants to
|
| /kernel/linux/linux-6.6/include/linux/input/ |
| D | vivaldi-fmap.h | 16 * This structure is supposed to be used by ChromeOS keyboards using
|
| /kernel/linux/linux-5.10/arch/s390/include/asm/ |
| D | vdso.h | 19 * structure is supposed to be known only to the function in the vdso
|
| /kernel/linux/linux-6.6/include/linux/soc/ti/ |
| D | ti-msgmgr.h | 24 * on SoC. Client is supposed to be aware of this.
|
| /kernel/linux/linux-6.6/Documentation/dev-tools/kunit/ |
| D | faq.rst | 12 A `unit test <https://martinfowler.com/bliki/UnitTest.html>`_ is supposed to
49 - A unit test is supposed to test a single unit of code in isolation. A unit
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/kunit/ |
| D | faq.rst | 12 A `unit test <https://martinfowler.com/bliki/UnitTest.html>`_ is supposed to
47 - A unit test is supposed to test a single unit of code in isolation, hence the
|
12345678910>>...56