Home
last modified time | relevance | path

Searched full:typical (Results 1 – 25 of 550) sorted by relevance

12345678910>>...22

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/panel/
Dpanel-timing.yaml56 Timing can be specified either as a typical value or as a tuple
78 description: typical number of pixels
91 description: typical number of pixels
104 description: typical number of pixels
117 description: typical number of lines
130 description: typical number of lines
143 description: typical number of lines
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/touchscreen/
Dstmpe.txt34 0 -> 20 mA (typical 35mA max)
35 1 -> 50 mA (typical 80 mA max)
100 * 50 mA typical 80 mA max touchscreen drivers
/kernel/linux/linux-5.10/Documentation/i2c/
Dfunctionality.rst69 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
/kernel/linux/linux-5.10/Documentation/userspace-api/media/
Dintro.rst12 A typical media device hardware is shown at :ref:`typical_media_device`.
20 Typical Media Device
/kernel/linux/linux-5.10/Documentation/vm/
Dovercommit-accounting.rst11 space are refused. Used for a typical system. It ensures a
47 largest size you think you will need. For typical stack usage this does
/kernel/linux/linux-5.10/Documentation/
Datomic_t.txt131 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
/kernel/linux/linux-5.10/arch/arm/mach-omap2/
Dvp.c134 * 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()
/kernel/linux/linux-5.10/tools/virtio/ringtest/
DREADME4 Typical use:
/kernel/linux/linux-5.10/drivers/slimbus/
DKconfig9 and other peripheral components in typical embedded systems.
/kernel/linux/linux-5.10/net/ieee802154/
DKconfig8 devices. Maximum allowed data rate is 250 kb/s and typical personal
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-bus-iio-mpu60508 is a 3x3 unitary matrix. A typical mounting matrix would look like
Dsysfs-driver-w1_therm7 (typical -55 degC to 125 degC), if not values will be trimmed
24 limited EEPROM writing cycles (typical 50k)
Dsysfs-class-power-wilco11 typical battery usage pattern.
Dprocfs-smaps_rollup17 Typical output looks like this::
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/rtc/
Dfaraday,ftrtc010.txt16 32768 Hz (a typical low-power clock).
/kernel/linux/linux-5.10/Documentation/driver-api/media/
Ddtv-frontend.rst24 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
/kernel/linux/linux-5.10/drivers/mtd/chips/
Dcfi_probe.c369 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()
/kernel/linux/linux-5.10/arch/sh/mm/
Dsram.c17 * added either by the CPU or the platform code. Typical SRAM sizes
/kernel/linux/linux-5.10/arch/powerpc/platforms/82xx/
DKconfig60 The MPC8260 is a typical embedded CPU made by Freescale. Selecting
/kernel/linux/linux-5.10/Documentation/litmus-tests/rcu/
DRCU+sync+free.litmus10 * This is a typical pattern of RCU usage, where the write before the grace
/kernel/linux/linux-5.10/drivers/cpufreq/
Dgx-suspmod.c88 #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()
/kernel/linux/linux-5.10/arch/arc/include/uapi/asm/
Dunistd.h13 * Non-typical guard macro to enable inclusion twice in ARCH sys.c
/kernel/linux/linux-5.10/kernel/
DKconfig.hz23 100 Hz is a typical choice for servers, SMP and NUMA systems
/kernel/linux/linux-5.10/tools/arch/arc/include/uapi/asm/
Dunistd.h13 * Non-typical guard macro to enable inclusion twice in ARCH sys.c
/kernel/linux/linux-5.10/include/linux/platform_data/
Di2c-hid.h29 * A typical example is the following:

12345678910>>...22