| /openbmc/linux/Documentation/riscv/ |
| H A D | patch-acceptance.rst | 47 Additionally, the RISC-V specification allows implementers to create
58 (Implementers, may, of course, maintain their own Linux kernel trees containing
|
| /openbmc/bmcweb/ |
| H A D | DBUS_USAGE.md | 8 verified that _all_ OpenBMC implementers of the interface support that
|
| /openbmc/linux/Documentation/devicetree/bindings/rtc/ |
| H A D | faraday,ftrtc010.yaml | 36 should be 1 Hz, but implementers actually seem to choose different
|
| /openbmc/linux/rust/kernel/sync/ |
| H A D | lock.rs | 23 /// - Implementers must ensure that only one thread/CPU may access the protected data once the lock
25 /// - Implementers must also ensure that `relock` uses the same locking method as the original
|
| /openbmc/linux/Documentation/devicetree/bindings/input/touchscreen/ |
| H A D | zinitix,bt400.yaml | 66 the vdd-supply represents VCCA instead of VDD. Implementers should first
|
| /openbmc/linux/Documentation/driver-api/soundwire/ |
| H A D | error_handling.rst | 64 or Master driver implementers are responsible for writing valid values in
|
| /openbmc/linux/include/crypto/internal/ |
| H A D | des.h | 51 * same as DES. Implementers MUST reject keys that exhibit this
|
| /openbmc/linux/Documentation/networking/ |
| H A D | cdc_mbim.rst | 322 1) USB Implementers Forum, Inc. - "Universal Serial Bus
328 2) USB Implementers Forum, Inc. - "Universal Serial Bus
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-net-cdc_ncm | 86 24, 2010 from USB Implementers Forum, Inc. The descriptions are
|
| /openbmc/linux/rust/kernel/ |
| H A D | types.rs | 276 /// Implementers must ensure that increments to the reference count keep the object alive in memory
279 /// Implementers must also ensure that all instances are reference-counted. (Otherwise they
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Protocol.json | 129 …"USB": "This value shall indicate conformance to the USB Implementers Forum Universal Serial Bus S…
|
| /openbmc/docs/designs/ |
| H A D | redfish-resource-supplement-for-pfr.md | 28 guidelines to implementers, including Original Equipment Manufacturers (OEMs)
|
| /openbmc/u-boot/drivers/usb/host/ |
| H A D | Kconfig | 267 USB-Implementers Forum (USB-IF) USB 2.0 specifications.
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | Protocol.json | 129 …"USB": "This value shall indicate conformance to the USB Implementers Forum Universal Serial Bus S…
|
| /openbmc/linux/arch/arm/include/asm/ |
| H A D | cputype.h | 237 * implementer: implementers are free to define their own part numbers
|
| /openbmc/sdeventplus/src/sdeventplus/source/ |
| H A D | base.hpp | 169 * This needs to be called by all source implementers.
|
| /openbmc/docs/ |
| H A D | cpp-style-and-conventions.md | 108 2. Implementers should include the lowest level header required to solve the
|
| /openbmc/linux/drivers/soundwire/ |
| H A D | mipi_disco.c | 10 * The helper functions read the Master and Slave properties. Implementers
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | pmbus-core.rst | 18 promoted by the PMBus Implementers Forum (PMBus-IF), comprising 30+ adopters
|
| /openbmc/linux/arch/s390/crypto/ |
| H A D | des_s390.c | 194 * same as DES. Implementers MUST reject keys that exhibit this
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | cec.rst | 234 Note for CEC application implementers: the <Image View On> message must
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
| H A D | Protocol_v1.xml | 52 …Description" String="This value shall indicate conformance to the USB Implementers Forum Universal…
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | Protocol_v1.xml | 52 …Description" String="This value shall indicate conformance to the USB Implementers Forum Universal…
|
| /openbmc/linux/include/linux/ |
| H A D | dma-fence.h | 54 * ways by different fence implementers, so do not rely on this.
|
| /openbmc/linux/Documentation/hid/ |
| H A D | hidintro.rst | 56 available from the `USB Implementers Forum <https://www.usb.org/>`_
|