| /openbmc/linux/drivers/iio/test/ |
| H A D | iio-test-rescale.c | 34 * Typical use cases
37 .name = "typical IIO_VAL_INT, positive",
45 .name = "typical IIO_VAL_INT, negative",
53 .name = "typical IIO_VAL_FRACTIONAL, positive",
62 .name = "typical IIO_VAL_FRACTIONAL, negative",
71 .name = "typical IIO_VAL_FRACTIONAL_LOG2, positive",
80 .name = "typical IIO_VAL_FRACTIONAL_LOG2, negative",
89 .name = "typical IIO_VAL_INT_PLUS_NANO, positive",
98 .name = "typical IIO_VAL_INT_PLUS_NANO, negative",
107 .name = "typical IIO_VAL_INT_PLUS_MICRO, positive",
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/display/panel/ |
| H A D | panel-timing.yaml | 56 Timing can be specified either as a typical value or as a tuple
78 description: typical number of pixels
90 description: typical number of pixels
102 description: typical number of pixels
114 description: typical number of lines
126 description: typical number of lines
138 description: typical number of lines
|
| /openbmc/sdbusplus/test/server/ |
| H A D | object.cpp | 38 // Simulate the typical usage of a service in TEST_F()
62 // Simulate the typical usage of a service in TEST_F()
94 // Simulate the typical usage of a service in TEST_F()
124 // Simulate the typical usage of a service in TEST_F()
149 // Simulate the typical usage of a service in TEST_F()
|
| /openbmc/linux/Documentation/i2c/ |
| H A D | functionality.rst | 69 function callback ``functionality``. Typical implementations are given
72 A typical SMBus-only adapter would list all the SMBus transactions it
82 A typical full-I2C adapter would use the following (from the i2c-pxa
104 check whether the needed functionality is present. The typical way to do
|
| /openbmc/phosphor-dbus-monitor/src/ |
| H A D | watch.hpp | 17 * or initialization. Typical implementations might register dbus
22 * their setup. Typical implementations will forward the call
|
| /openbmc/linux/Documentation/userspace-api/media/ |
| H A D | intro.rst | 12 A typical media device hardware is shown at :ref:`typical_media_device`.
20 Typical Media Device
|
| /openbmc/phosphor-fan-presence/presence/ |
| H A D | psensor.hpp | 40 * for detecting presence. Typical implementations
52 * state change notifications. Typical implementations
|
| /openbmc/linux/Documentation/mm/ |
| H A D | overcommit-accounting.rst | 9 space are refused. Used for a typical system. It ensures a
46 largest size you think you will need. For typical stack usage this does
|
| /openbmc/linux/Documentation/devicetree/bindings/mfd/ |
| H A D | fsl,imx8qxp-csr.yaml | 16 to a mix of standalone hardware devices within that subsystem. One typical
18 by phandle, and the other typical use-case is that the operating system
|
| /openbmc/linux/arch/arm/mach-omap2/ |
| H A D | vp.c | 134 * Clear all pending TransactionDone interrupt/status. Typical latency in omap_vp_forceupdate_scale()
156 * Wait for TransactionDone. Typical latency is <200us. in omap_vp_forceupdate_scale()
272 * Wait for VP idle Typical latency is <2us. Maximum latency is ~100us in omap_vp_disable()
|
| /openbmc/linux/tools/virtio/ringtest/ |
| H A D | README | 4 Typical use:
|
| /openbmc/linux/drivers/cxl/ |
| H A D | Kconfig | 76 In addition to typical memory resources a platform may also advertise
91 memory were attached to the typical CPU memory controller. This is
|
| /openbmc/u-boot/doc/ |
| H A D | README.pblimage | 70 Typical example of rcw.cfg file:
81 Typical example of pbi.cfg file:
|
| /openbmc/gpioplus/ |
| H A D | README.md | 16 For a test / debug build, a typical configuration is
|
| /openbmc/openbmc/poky/meta-yocto-bsp/conf/machine/ |
| H A D | genericx86.conf | 3 …. Supports a moderately wide range of drivers that should boot and be usable on "typical" hardware.
|
| H A D | genericx86-64.conf | 3 …. Supports a moderately wide range of drivers that should boot and be usable on "typical" hardware.
|
| /openbmc/sdeventplus/ |
| H A D | README.md | 21 For a test / debug build, a typical configuration is
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Decorator/ |
| H A D | MeetsMinimumShipLevel.interface.yaml | 7 that do or do not meet the MSL. Typical reactions might be to prevent a
|
| /openbmc/openbmc-test-automation/redfish/extended/ |
| H A D | test_websocket.robot | 64 # Typical monitor_file contents:
86 # Typical monitor_file contents:
|
| /openbmc/qemu/docs/devel/ |
| H A D | secure-coding-practices.rst | 46 accesses and data read from guest memory must be validated. A typical example
75 typical "theory of operation" presented in driver writer manuals. The guest
|
| /openbmc/qemu/docs/ |
| H A D | xbzrle.txt | 7 workloads that are typical of large enterprise applications such as SAP ERP
55 XBZRLE has a sustained bandwidth of 2-2.5 GB/s for typical workloads making it
|
| /openbmc/linux/virt/kvm/ |
| H A D | binary_stats.c | 38 * as in the limit) from any position, the typical usage would follow below
116 * The descriptors copy would be skipped in the typical case that in kvm_stats_read()
|
| /openbmc/linux/Documentation/ |
| H A D | atomic_t.txt | 131 the typical solution is to then implement atomic_set{}() with atomic_xchg().
225 is a 'typical' RELEASE pattern, the barrier is strictly stronger than
233 is an ACQUIRE pattern (though very much not typical), but again the barrier is
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/ |
| H A D | ActivationBlocksTransition.interface.yaml | 7 A typical use of this would be to prevent (delay) the power-on of a managed
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ |
| H A D | ErrorBlocksTransition.interface.yaml | 7 A typical use of this would be to prevent the power-on of a managed host
|