Searched full:typical (Results 1 – 25 of 666) sorted by relevance
12345678910>>...27
/linux-6.14.4/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-6.14.4/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-6.14.4/Documentation/devicetree/bindings/pinctrl/ |
D | spacemit,k1-pinctrl.yaml | 56 typical value for selecting bias pull up or strong pull up. 63 typical current when output high level. 69 typical threshold for schmitt trigger.
|
D | sophgo,cv1800-pinctrl.yaml | 71 description: typical current when output high level. 74 description: typical threshold for schmitt trigger.
|
/linux-6.14.4/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-6.14.4/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-6.14.4/Documentation/mm/ |
D | overcommit-accounting.rst | 9 space are refused. Used for a typical system. It ensures a 45 largest size you think you will need. For typical stack usage this does
|
/linux-6.14.4/drivers/pinctrl/sophgo/ |
D | pinctrl-cv18xx.h | 68 * @get_oc_map: get mapping for typical low level output current value to 70 * @get_schmitt_map: get mapping for register value to typical schmitt
|
/linux-6.14.4/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-6.14.4/drivers/cxl/ |
D | Kconfig | 81 In addition to typical memory resources a platform may also advertise 96 memory were attached to the typical CPU memory controller. This is
|
/linux-6.14.4/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-6.14.4/Documentation/devicetree/bindings/hwmon/ |
D | adi,ltc4282.yaml | 58 10% and 15% settings with the actual min, typical and max tolerances. 70 10% and 15% settings with the actual min, typical and max tolerances.
|
/linux-6.14.4/tools/virtio/ringtest/ |
D | README | 4 Typical use:
|
/linux-6.14.4/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-6.14.4/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-6.14.4/Documentation/admin-guide/pm/ |
D | cpuidle.rst | 277 that 6 times the standard deviation), the average is regarded as the "typical 281 taken as the "typical interval" value and so on, until either the "typical 283 the "typical interval" is assumed to equal "infinity" (the maximum unsigned 286 If the "typical interval" computed this way is long enough, the governor obtains 304 compared to the "typical interval" determined previously and the minimum of 307 If the "typical interval" value is small, which means that the CPU is likely 309 be costly and the idle duration is simply predicted to equal the "typical
|
/linux-6.14.4/Documentation/ABI/testing/ |
D | debugfs-iio-backend | 11 Directly access the registers of backend Y. Typical usage is:
|
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)
|
/linux-6.14.4/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-6.14.4/drivers/mtd/chips/ |
D | cfi_probe.c | 370 printk("Typical byte/word write timeout: %d µs\n", 1<<cfip->WordWriteTimeoutTyp); in print_cfi_ident() 374 printk("Typical full buffer write timeout: %d µs\n", 1<<cfip->BufWriteTimeoutTyp); in print_cfi_ident() 380 printk("Typical block erase timeout: %d ms\n", 1<<cfip->BlockEraseTimeoutTyp); in print_cfi_ident() 383 printk("Typical chip erase timeout: %d ms\n", 1<<cfip->ChipEraseTimeoutTyp); in print_cfi_ident()
|
/linux-6.14.4/net/ieee802154/ |
D | Kconfig | 8 devices. Maximum allowed data rate is 250 kb/s and typical personal
|
/linux-6.14.4/drivers/slimbus/ |
D | Kconfig | 9 and other peripheral components in typical embedded systems.
|
/linux-6.14.4/drivers/staging/media/atomisp/pci/runtime/pipeline/interface/ |
D | ia_css_pipeline.h | 226 * @param[in] key The query key, typical use is pipe_num. 256 * @param[in] Query key, typical use is pipe_num
|
/linux-6.14.4/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()
|
12345678910>>...27