Searched full:typical (Results 1 – 25 of 1029) sorted by relevance
12345678910>>...42
56 Timing can be specified either as a typical value or as a tuple78 description: typical number of pixels91 description: typical number of pixels104 description: typical number of pixels117 description: typical number of lines130 description: typical number of lines143 description: typical number of lines
15 A typical device falling into this category would be connected via SPI51 device.txt - elements of a typical device driver.53 trigger.txt - elements of a typical trigger driver.
61 function callback `functionality'. Typical implementations are given64 A typical SMBus-only adapter would list all the SMBus transactions it74 A typical full-I2C adapter would use the following (from the i2c-pxa96 check whether the needed functionality is present. The typical way to do
34 0 -> 20 mA (typical 35mA max)35 1 -> 50 mA (typical 80 mA max)100 * 50 mA typical 80 mA max touchscreen drivers
69 function callback ``functionality``. Typical implementations are given72 A typical SMBus-only adapter would list all the SMBus transactions it82 A typical full-I2C adapter would use the following (from the i2c-pxa104 check whether the needed functionality is present. The typical way to do
12 A typical media device hardware is shown at :ref:`typical_media_device`.20 Typical Media Device
112 the typical solution is to then implement atomic_set{}() with atomic_xchg().200 is a 'typical' RELEASE pattern, the barrier is strictly stronger than206 is an ACQUIRE pattern (though very much not typical), but again the barrier is
24 - st,i-drive: current limit value of the touchscreen drivers (0 -> 20 mA typical 3525 mA max, 1 -> 50 mA typical 80 mA max)
11 space are refused. Used for a typical system. It ensures a47 largest size you think you will need. For typical stack usage this does
131 the typical solution is to then implement atomic_set{}() with atomic_xchg().225 is a 'typical' RELEASE pattern, the barrier is strictly stronger than233 is an ACQUIRE pattern (though very much not typical), but again the barrier is
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()
4 Typical use:
9 and other peripheral components in typical embedded systems.
8 devices. Maximum allowed data rate is 250 kb/s and typical personal
7 devices. Maximum allowed data rate is 250 kb/s and typical personal
16 32768 Hz (a typical low-power clock).
8 is a 3x3 unitary matrix. A typical mounting matrix would look like
13 Typical output looks like this: