Searched full:correspondence (Results 1 – 25 of 55) sorted by relevance
123
/openbmc/phosphor-fan-presence/control/ |
H A D | fan.hpp | 18 * a 1 to 1 correspondence between rotors and sensors, depending
|
/openbmc/linux/drivers/crypto/cavium/zip/ |
H A D | zip_deflate.h | 41 * ENJOYMENT, QUIET POSSESSION OR CORRESPONDENCE TO DESCRIPTION. THE
|
H A D | zip_inflate.h | 41 * ENJOYMENT, QUIET POSSESSION OR CORRESPONDENCE TO DESCRIPTION. THE
|
H A D | zip_mem.h | 41 * ENJOYMENT, QUIET POSSESSION OR CORRESPONDENCE TO DESCRIPTION. THE
|
H A D | zip_crypto.h | 41 * ENJOYMENT, QUIET POSSESSION OR CORRESPONDENCE TO DESCRIPTION. THE
|
H A D | zip_device.h | 41 * ENJOYMENT, QUIET POSSESSION OR CORRESPONDENCE TO DESCRIPTION. THE
|
H A D | zip_main.h | 41 * ENJOYMENT, QUIET POSSESSION OR CORRESPONDENCE TO DESCRIPTION. THE
|
H A D | zip_mem.c | 41 * ENJOYMENT, QUIET POSSESSION OR CORRESPONDENCE TO DESCRIPTION. THE
|
H A D | common.h | 41 * ENJOYMENT, QUIET POSSESSION OR CORRESPONDENCE TO DESCRIPTION. THE
|
H A D | zip_deflate.c | 41 * ENJOYMENT, QUIET POSSESSION OR CORRESPONDENCE TO DESCRIPTION. THE
|
H A D | zip_inflate.c | 41 * ENJOYMENT, QUIET POSSESSION OR CORRESPONDENCE TO DESCRIPTION. THE
|
H A D | zip_device.c | 41 * ENJOYMENT, QUIET POSSESSION OR CORRESPONDENCE TO DESCRIPTION. THE
|
H A D | zip_crypto.c | 41 * ENJOYMENT, QUIET POSSESSION OR CORRESPONDENCE TO DESCRIPTION. THE
|
/openbmc/linux/Documentation/devicetree/bindings/net/dsa/ |
H A D | nxp,sja1105.yaml | 41 # The PHY addresses to port correspondence is as follows: for 100base-T1,
|
/openbmc/linux/arch/ia64/include/asm/ |
H A D | hw_irq.h | 141 * vectors. On smaller systems, there is a one-to-one correspondence between interrupt
|
/openbmc/linux/Documentation/devicetree/bindings/pci/ |
H A D | host-generic-pci.yaml | 22 accessed via an ioport) and laid out with a direct correspondence to the
|
/openbmc/openbmc/poky/documentation/ref-manual/ |
H A D | features.rst | 41 one-to-one correspondence to packages, and they can go beyond simply 100 your distribution. Features do not have a one-to-one correspondence to
|
/openbmc/docs/ |
H A D | code-of-conduct.md | 179 to messages to mailing lists, private correspondence, Web pages, chat channels,
|
/openbmc/linux/include/uapi/linux/ |
H A D | rds.h | 314 * The correspondence between bits and ports is
|
/openbmc/qemu/target/avr/ |
H A D | helper.c | 104 return addr; /* I assume 1:1 address correspondence */ in avr_cpu_get_phys_page_debug()
|
/openbmc/linux/Documentation/core-api/irq/ |
H A D | irq-domain.rst | 18 Here the interrupt number loose all kind of correspondence to
|
/openbmc/linux/Documentation/networking/ |
H A D | representors.rst | 118 correspondence between VF netdevices and VF representors, more advanced device
|
/openbmc/linux/drivers/crypto/intel/qat/qat_4xxx/ |
H A D | adf_4xxx_hw_data.c | 169 * The default routing is set to have a one to one correspondence between the
|
/openbmc/linux/Documentation/livepatch/ |
H A D | module-elf-format.rst | 91 multiple functions within the same object). There is a 1-1 correspondence
|
/openbmc/linux/arch/arm/boot/dts/arm/ |
H A D | vexpress-v2m-rs1.dtsi | 15 * correspondence between the two configurations.
|
123