Home
last modified time | relevance | path

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

12345678910>>...40

/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/display/panel/
H A 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
/OK3568_Linux_fs/external/mpp/inc/
H A Dmpp_task.h129 * 1. typical decoder mode:
138 * typical flow
161 * 1. typical encoder mode:
171 * typical / user input flow
199 * 1. typical image process mode:
203 * typical / user input flow
H A Dmpp_buffer.h62 * typical call flow:
75 * typical call flow:
210 * Typical usage is on Android. MediaPlayer gralloc Graphic buffer then commit these buffer
218 * Typical usage is for image processing. Image processing normally will be a oneshot operation
/OK3568_Linux_fs/external/rknpu2/examples/3rdparty/mpp/include/rockchip/
H A Dmpp_task.h129 * 1. typical decoder mode:
138 * typical flow
161 * 1. typical encoder mode:
171 * typical / user input flow
199 * 1. typical image process mode:
203 * typical / user input flow
H A Dmpp_buffer.h62 * typical call flow:
75 * typical call flow:
210 * Typical usage is on Android. MediaPlayer gralloc Graphic buffer then commit these buffer
218 * Typical usage is for image processing. Image processing normally will be a oneshot operation
/OK3568_Linux_fs/kernel/Documentation/i2c/
H A 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
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/input/touchscreen/
H A 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
/OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/deps/boost/1.65.1/include/boost/proto/
H A Drepeat.hpp78 /// BOOST_PROTO_REPEAT_FROM_TO_EX() is used generate the kind of repetitive code that is typical
92 /// BOOST_PROTO_REPEAT_FROM_TO() is used generate the kind of repetitive code that is typical
174 /// BOOST_PROTO_REPEAT_EX() is used generate the kind of repetitive code that is typical
188 /// BOOST_PROTO_REPEAT() is used generate the kind of repetitive code that is typical
202 /// BOOST_PROTO_LOCAL_ITERATE() is used generate the kind of repetitive code that is typical
/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/
H A Dintro.rst12 A typical media device hardware is shown at :ref:`typical_media_device`.
20 Typical Media Device
/OK3568_Linux_fs/kernel/Documentation/vm/
H A 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
/OK3568_Linux_fs/kernel/Documentation/
H A 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
/OK3568_Linux_fs/kernel/drivers/gpu/arm/mali400/mali/common/
H A Dmali_kernel_common.h46 * Note no closing semicolon - this is supplied in typical usage:
54 * Note no closing semicolon - this is supplied in typical usage:
66 * else clauses. Note also no closing semicolon - this is supplied in typical usage:
/OK3568_Linux_fs/u-boot/doc/
H A DREADME.vxworks48 parameter called BOOT_LINE_ADRS. Assign its value to "bootaddr". A typical
77 location at 0x4000 for "e820data" and 0x4a00 for "e820info". Typical values
H A DREADME.pblimage70 Typical example of rcw.cfg file:
81 Typical example of pbi.cfg file:
/OK3568_Linux_fs/kernel/arch/arm/mach-omap2/
H A 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()
/OK3568_Linux_fs/kernel/Documentation/driver-api/media/
H A 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
/OK3568_Linux_fs/kernel/drivers/mtd/chips/
H A 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()
/OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/deps/boost/1.65.1/include/boost/algorithm/string/
H A Diter_find.hpp57 Typical type of the result is
128 Typical type of the result is
/OK3568_Linux_fs/external/rockit/mpi/sdk/include/
H A Drk_comm_sys.h124 * seconds,a typical format like "dd/1,mm/1,ss/1",
135 * and seconds,a typical format like "dd/1,mm/1,ss/1",
/OK3568_Linux_fs/kernel/drivers/cpufreq/
H A 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()
/OK3568_Linux_fs/kernel/Documentation/ABI/testing/
H A Dsysfs-driver-w1_therm7 (typical -55 degC to 125 degC), if not values will be trimmed
24 limited EEPROM writing cycles (typical 50k)
/OK3568_Linux_fs/kernel/Documentation/driver-api/
H A Dntb.rst35 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:
/OK3568_Linux_fs/kernel/tools/virtio/ringtest/
H A DREADME4 Typical use:
/OK3568_Linux_fs/buildroot/package/gtksourceview/
H A DConfig.in10 printing and other features typical of a source code editor.
/OK3568_Linux_fs/buildroot/package/biosdevname/
H A DConfig.in13 typical ethX naming.

12345678910>>...40