| /linux-5.10/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
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
|
| /linux-5.10/Documentation/devicetree/bindings/input/touchscreen/ ! |
| D | stmpe.txt | 34 0 -> 20 mA (typical 35mA max)
35 1 -> 50 mA (typical 80 mA max)
100 * 50 mA typical 80 mA max touchscreen drivers
|
| /linux-5.10/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-5.10/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-5.10/Documentation/vm/ ! |
| D | overcommit-accounting.rst | 11 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
|
| /linux-5.10/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-5.10/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-5.10/tools/virtio/ringtest/ ! |
| D | README | 4 Typical use:
|
| /linux-5.10/drivers/slimbus/ ! |
| D | Kconfig | 9 and other peripheral components in typical embedded systems.
|
| /linux-5.10/net/ieee802154/ ! |
| D | Kconfig | 8 devices. Maximum allowed data rate is 250 kb/s and typical personal
|
| /linux-5.10/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.
|
| D | procfs-smaps_rollup | 17 Typical output looks like this::
|
| /linux-5.10/Documentation/devicetree/bindings/rtc/ ! |
| D | faraday,ftrtc010.txt | 16 32768 Hz (a typical low-power clock).
|
| /linux-5.10/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-5.10/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-5.10/arch/sh/mm/ ! |
| D | sram.c | 17 * added either by the CPU or the platform code. Typical SRAM sizes
|
| /linux-5.10/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-5.10/arch/powerpc/platforms/82xx/ ! |
| D | Kconfig | 60 The MPC8260 is a typical embedded CPU made by Freescale. Selecting
|
| /linux-5.10/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-5.10/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:
|
| /linux-5.10/Documentation/core-api/ ! |
| D | symbol-namespaces.rst | 138 A typical scenario for module authors would be::
155 You can also run nsdeps for external module builds. A typical usage is::
|
| /linux-5.10/drivers/staging/media/atomisp/pci/runtime/pipeline/interface/ ! |
| D | ia_css_pipeline.h | 237 * @param[in] key The query key, typical use is pipe_num.
269 * @param[in] Query key, typical use is pipe_num
|
| /linux-5.10/arch/arc/include/uapi/asm/ ! |
| D | unistd.h | 13 * Non-typical guard macro to enable inclusion twice in ARCH sys.c
|