Searched full:typical (Results 1 – 25 of 605) sorted by relevance
12345678910>>...25
| /Linux-v6.1/drivers/iio/test/ |
| 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 …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/display/panel/ |
| 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
|
| /Linux-v6.1/Documentation/devicetree/bindings/input/touchscreen/ |
| D | stmpe.txt | 34 0 -> 20 mA (typical 35mA max)
35 1 -> 50 mA (typical 80 mA max)
99 * 50 mA typical 80 mA max touchscreen drivers
|
| /Linux-v6.1/Documentation/i2c/ |
| 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
|
| /Linux-v6.1/Documentation/userspace-api/media/ |
| D | intro.rst | 12 A typical media device hardware is shown at :ref:`typical_media_device`.
20 Typical Media Device
|
| /Linux-v6.1/Documentation/mm/ |
| 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
|
| /Linux-v6.1/drivers/cxl/ |
| D | Kconfig | 74 In addition to typical memory resources a platform may also advertise
89 memory were attached to the typical CPU memory controller. This is
|
| /Linux-v6.1/arch/arm/mach-omap2/ |
| 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()
|
| /Linux-v6.1/Documentation/devicetree/bindings/mfd/ |
| 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
|
| /Linux-v6.1/tools/virtio/ringtest/ |
| D | README | 4 Typical use:
|
| /Linux-v6.1/virt/kvm/ |
| 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()
|
| /Linux-v6.1/Documentation/ |
| 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
|
| /Linux-v6.1/drivers/mtd/chips/ |
| D | cfi_probe.c | 369 printk("Typical byte/word write timeout: %d µs\n", 1<<cfip->WordWriteTimeoutTyp); in print_cfi_ident()
373 printk("Typical full buffer write timeout: %d µs\n", 1<<cfip->BufWriteTimeoutTyp); in print_cfi_ident()
379 printk("Typical block erase timeout: %d ms\n", 1<<cfip->BlockEraseTimeoutTyp); in print_cfi_ident()
382 printk("Typical chip erase timeout: %d ms\n", 1<<cfip->ChipEraseTimeoutTyp); in print_cfi_ident()
|
| /Linux-v6.1/Documentation/driver-api/media/ |
| D | dtv-frontend.rst | 24 A typical example of such struct in a driver ``foo`` is::
64 A typical example of such struct in a driver ``bar`` meant to be used on
277 A typical example of the logic that handle status and statistics is::
391 On such drivers, a typical routine to get statistics would be like
|
| /Linux-v6.1/arch/arm64/boot/dts/qcom/ |
| D | sc7280-herobrine-lte-sku.dtsi | 7 /* Modem setup is different on Chrome setups than typical Qualcomm setup */
|
| /Linux-v6.1/net/ieee802154/ |
| D | Kconfig | 8 devices. Maximum allowed data rate is 250 kb/s and typical personal
|
| /Linux-v6.1/drivers/slimbus/ |
| D | Kconfig | 9 and other peripheral components in typical embedded systems.
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-mpu6050 | 8 is a 3x3 unitary matrix. A typical mounting matrix would look like
|
| D | sysfs-driver-w1_therm | 7 (typical -55 degC to 125 degC), if not values will be trimmed
24 limited EEPROM writing cycles (typical 50k)
|
| D | sysfs-class-power-wilco | 11 typical battery usage pattern.
|
| /Linux-v6.1/drivers/cpufreq/ |
| D | gx-suspmod.c | 88 #define PCI_IRQTC 0x8c /* irq speedup timer counter register:typical 2 to 4ms */
89 #define PCI_VIDTC 0x8d /* video speedup timer counter register: typical 50 to 100ms */
273 /* typical 2 to 4ms */ in gx_set_cpuspeed()
275 /* typical 50 to 100ms */ in gx_set_cpuspeed()
|
| /Linux-v6.1/arch/sh/mm/ |
| D | sram.c | 17 * added either by the CPU or the platform code. Typical SRAM sizes
|
| /Linux-v6.1/Documentation/litmus-tests/rcu/ |
| D | RCU+sync+free.litmus | 10 * This is a typical pattern of RCU usage, where the write before the grace
|
| /Linux-v6.1/arch/powerpc/platforms/82xx/ |
| D | Kconfig | 60 The MPC8260 is a typical embedded CPU made by Freescale. Selecting
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | ntb.rst | 35 NTB Typical client driver implementation
55 So typical scenario of the first type memory window initialization looks:
73 Typical scenario of the second type interface initialization would be:
|
12345678910>>...25
