Home
last modified time | relevance | path

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

12345678910>>...40

/openbmc/linux/sound/hda/
H A 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
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
/openbmc/x86-power-control/src/
H A Dpower_control.hpp24 * This manager supposed to store runtime parameters that supposed to be
35 * This class only exists to unite all PowerRestore-related code. It supposed
/openbmc/linux/Documentation/devicetree/bindings/pci/
H A Dsnps,dw-pcie.yaml125 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
H A Dbaikal,bt1-pcie.yaml17 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
H A Dsnps,dw-pcie-common.yaml136 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.
/openbmc/u-boot/doc/
H A DREADME.memory-test12 This function is supposed to be used in each and every U-Boot port
14 memory banks on this piece of hardware. The code is supposed to be
96 errors, not a single one ever. The problems this code was supposed
/openbmc/linux/drivers/usb/core/
H A Dotg_productlist.h18 /* FIXME actually, printers are NOT supposed to use device classes;
19 * they're supposed to use interface classes...
/openbmc/phosphor-logging/extensions/openpower-pels/registry/tools/
H A Dvalidate_registry.py55 supposed to match.
61 # Don't check on "11" SRCs as those reason codes aren't supposed to
/openbmc/linux/drivers/mtd/maps/
H A Dphysmap-bt1-rom.c107 /* 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()
/openbmc/u-boot/scripts/
H A Dfill_scrapyard.py12 When we remove support for boards, we are supposed to add entries to
21 supposed to fill in the blank fields before adding new entries to
H A Dshow-gnu-make6 # U-Boot is supposed to be built on various platforms.
/openbmc/qemu/tests/decode/
H A Derr_pattern_group_ident2.decode10 # comments are supposed to be indented
/openbmc/linux/include/linux/mailbox/
H A Dzynqmp-ipi-message.h13 * Client is supposed to be aware of this.
/openbmc/linux/net/core/
H A Dof_net.c106 * 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
/openbmc/linux/Documentation/driver-api/tty/
H A Dtty_driver.rst62 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
/openbmc/linux/drivers/i3c/
H A DKconfig9 It's supposed to be backward compatible with I2C while providing
/openbmc/openbmc/meta-openpower/recipes-phosphor/vpd/
H A Dopenpower-fru-inventory-example-native.bb17 # This recipe is supposed to create a systemd environment file
H A Dopenpower-fru-properties-example-native.bb17 # This recipe is supposed to create an output yaml file with
/openbmc/openbmc/meta-phosphor/recipes-phosphor/ipmi/
H A Dphosphor-ipmi-sensor-inventory-native.bb16 # This recipe is supposed to create an output yaml file with
H A Dphosphor-ipmi-fru-properties-native.bb16 # This recipe is supposed to create an output yaml file with
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DMMIXware13 the master source files in any way. Everybody is supposed to use
/openbmc/linux/drivers/staging/sm750fb/
H A DTODO7 are supposed to be sample code which is given here if someone wants to
/openbmc/linux/include/linux/input/
H A Dvivaldi-fmap.h16 * This structure is supposed to be used by ChromeOS keyboards using
/openbmc/qemu/tests/tcg/mips/user/ase/msa/
H A DREADME1 The tests in subdirectories of this directory are supposed to be compiled for
/openbmc/linux/arch/powerpc/platforms/52xx/
H A Dlite5200.c48 * 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

12345678910>>...40