Searched full:order (Results 1 – 25 of 1009) sorted by relevance
12345678910>>...41
| /Documentation/media/uapi/v4l/ |
| D | field-order.rst | 10 .. _field-order:
13 Field Order
32 which field of a frame is older, the *temporal order*.
37 even) fields, the *spatial order*: The first line of the top field is
46 creating a natural order.
51 and spatial order of fields. The diagrams below should make this
55 bus in the same order they were captured, so if the top field was
60 order. Some drivers may permit the selection of a different order, to
83 - Applications request this field order when any field format
85 e.g. the requested image size, and return the actual field order.
[all …]
|
| /Documentation/trace/postprocess/ |
| D | trace-vmscan-postprocess.pl | 31 # Per-order events
110 my $regex_direct_begin_default = 'order=([0-9]*) may_writepage=([0-9]*) gfp_flags=([A-Z_|]*)';
112 my $regex_kswapd_wake_default = 'nid=([0-9]*) order=([0-9]*)';
114 my $regex_wakeup_kswapd_default = 'nid=([0-9]*) zid=([0-9]*) order=([0-9]*) gfp_flags=([A-Z_|]*)';
115 my $regex_lru_isolate_default = 'isolate_mode=([0-9]*) classzone_idx=([0-9]*) order=([0-9]*) nr_req…
166 # Verify fields are in the right order
187 "order", "may_writepage",
196 "nid", "order");
204 "nid", "zid", "order", "gfp_flags");
208 "isolate_mode", "classzone_idx", "order",
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | fsl-vdoa.txt | 1 Freescale Video Data Order Adapter
4 The Video Data Order Adapter (VDOA) is present on the i.MX6q. Its sole purpose
5 is to reorder video data from the macroblock tiled order produced by the CODA
6 960 VPU to the conventional raster-scan order for scanout.
|
| D | st,st-hva.txt | 8 order.
13 - clock-names: names of the clocks listed in clocks property in the same order.
|
| /Documentation/sound/soc/ |
| D | pops-clicks.rst | 22 components in a specific order. This order is different for startup and
26 Startup Order :- DAC --> Mixers --> Output PGA --> Digital Unmute
28 Shutdown Order :- Digital Mute --> Output PGA --> Mixers --> DAC
43 Startup Order - Input PGA --> Mixers --> ADC
45 Shutdown Order - ADC --> Mixers --> Input PGA
|
| /Documentation/vm/ |
| D | swap_numa.rst | 15 Swap device has priority and that decides the order of it to be used. To make
24 Then node 0 will use the two swap devices in the order of swapA then swapB and
25 node 1 will use the two swap devices in the order of swapB then swapA. Note
26 that the order of them being swapped on doesn't matter.
40 Then node 0 will use them in the order of::
46 node 1 will use them in the order of::
50 node 2 will use them in the order of::
57 node 3 will use them in the order of::
|
| D | zsmalloc.rst | 9 never attempts higher order page allocation which is very likely to
11 (0-order) pages, it would suffer from very high fragmentation --
15 To overcome these issues, zsmalloc allocates a bunch of 0-order pages
17 pages act as a single higher-order page i.e. an object can span 0-order
70 the number of 0-order pages to make a zspage
|
| D | page_frags.rst | 8 which resides within a 0 or higher order compound page. Multiple
18 In order to make use of the page fragment APIs a backing page fragment
38 level. In order to enable these cases it is necessary to provide a generic
42 cleaning up the multiple references that were added to a page in order to
|
| D | slub.rst | 10 SLUB can enable debugging only for selected slabs in order to avoid
14 In order to switch debugging on one can add an option ``slub_debug``
58 F.e. in order to boot just with sanity checks and red zoning one would specify::
67 end of the slab name, in order to cover all slabs with the same prefix. For
78 Debugging options may require the minimum possible slab order to increase as
105 in order to reduce overhead and increase cache hotness of objects.
112 order to do so you must have the ``slabinfo`` tool. Then you can do
129 governed by the order of the allocation for each slab. The allocations
138 slab in order for the allocation order to be acceptable. In
144 specifies a minimum order of slabs. A similar effect like
[all …]
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 11 always acquire the locks in order by increasing address. We'll call
12 that "inode pointer" order in the following.
29 lock it. If we need to lock both, lock them in inode pointer order.
47 * lock parents in "ancestors first" order.
55 lock it. If we need to lock both, do so in inode pointer order.
79 (2) if cross-directory rename holds the lock on filesystem, order will not
82 the order until we had acquired all locks).
85 directory objects, and are acquired in inode pointer order.
88 target in inode pointer order in the case they are not directories.)
118 means that cross-directory rename is taking locks out of order. Due
[all …]
|
| /Documentation/devicetree/bindings/timer/ |
| D | qcom,msm-timer.txt | 13 optionally as well, 2 watchdog interrupts, in that order.
18 must appear in the same order as the clock names.
21 the same order as the clocks.
24 timer(s) in Hz in that order.
|
| /Documentation/devicetree/bindings/display/ |
| D | st,stih4xx.txt | 19 order.
37 order.
41 order.
50 the same order.
54 order.
62 the same order.
65 the same order
69 order.
78 the same order.
83 order.
[all …]
|
| /Documentation/trace/ |
| D | events-kmem.rst | 49 mm_page_alloc page=%p pfn=%lu order=%d migratetype=%d gfp_flags=%s
50 mm_page_alloc_zone_locked page=%p pfn=%lu order=%u migratetype=%d cpu=%d percpu_refill=%d
51 mm_page_free page=%p pfn=%lu order=%d
52 mm_page_free_batched page=%p pfn=%lu order=%d cold=%d
78 mm_page_alloc_zone_locked page=%p pfn=%lu order=%u migratetype=%d cpu=%d percpu_refill=%d
79 mm_page_pcpu_drain page=%p pfn=%lu order=%d cpu=%d migratetype=%d
82 for order-0 pages, reduces contention on the zone->lock and reduces the
109 External fragmentation affects whether a high-order allocation will be
116 high-order allocations will start failing at some time in the future. One
|
| /Documentation/networking/caif/ |
| D | spi_porting.txt | 6 Two extra GPIOs have been added in order to negotiate the transfers
26 In order to implement a SPI device you will, as a minimum,
51 This function is called by the CAIF SPI slave device in order to
54 This function can be called from IRQ context (recommended in order
60 This function is called by the CAIF SPI slave device in order to
63 This function can be called from IRQ context (recommended in order
83 In order to optimize throughput, a number of SPI padding options are provided.
123 * order not to add any delay. */
|
| /Documentation/security/keys/ |
| D | ecryptfs.rst | 12 the FEK is encrypted by 'ecryptfsd' with the help of external libraries in order
23 format 'ecryptfs' in order to be used in conjunction with the eCryptfs
28 In order to avoid known-plaintext attacks, the datablob obtained through
35 time after the unsealing of a 'trusted' key in order to perform the mount in a
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-trigger-sysfs | 18 trigger. In order to associate the trigger with an IIO device
28 In order to achieve this, one should write a positive integer
38 created trigger from the list of available triggers. In order to
|
| /Documentation/devicetree/bindings/powerpc/4xx/ |
| D | cpm.txt | 10 one of two different order for the CPM
12 in the following order (ER,FR,SR). The
13 others have them in the following order
|
| /Documentation/devicetree/bindings/sound/ |
| D | st,sti-asoc-card.txt | 20 - clock-names: name of the clocks listed in clocks property in the same order
23 order than the CPU_DAI properties.
26 the same order.
28 - interrupts: CPU_DAI interrupt line, listed in the same order than the
32 order than the CPU_DAI properties.
39 - clocks: CPU_DAI IP clock source, listed in the same order than the
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | st,stm32-dfsdm-adc.txt | 56 - st,filter-order: SinC filter order from 0 to 5.
58 [1-5]: order 1 to 5.
59 For audio purpose it is recommended to use order 3 to 5.
121 st,filter-order = <3>;
133 st,filter-order = <5>;
|
| /Documentation/driver-api/firmware/ |
| D | lookup-order.rst | 2 Firmware lookup order
6 Below is chronological order of how firmware will be looked for once
|
| /Documentation/devicetree/bindings/display/exynos/ |
| D | exynos7-decon.txt | 13 order: FIFO Level, VSYNC, LCD_SYSTEM. The interrupt specifier
17 "lcd_sys", in the same order as they were listed in the interrupts
27 - clock-names: list of clock names sorted in the same order as the clocks
|
| /Documentation/networking/ |
| D | tls-offload.rst | 25 on a packet by packet basis, provided the packets arrive in order.
139 Assuming segments are received in order, the device should be able to perform
150 in order the device should be able to handle them separately and make
162 For segments passed in order, the driver marks the packets with
210 two mechanisms for dealing with out of order segments.
215 Whenever an out of order segment is transmitted the driver provides
226 (next expected segment is the one after the out of order one), or continue
227 with the previous stream state - assuming that the out of order segment
235 Whenever an out of order segment is detected the driver requests
278 Segment 2 was dropped so 3 arrives out of order. The device knows
[all …]
|
| D | net_dim.txt | 28 interrupt moderation configuration of a channel in order to optimize packet
73 algorithm would increase in order to reduce calculation overhead. Also, after
76 done in order to avoid getting stuck in a "deep sleep" scenario. Once a
104 data sample stored in struct dim in order to decide on the algorithm's next
108 In order to use Net DIM from a networking driver, the driver needs to call the
122 will be scheduled and run in a separate thread in order not to add overhead to
124 the proper state in order to move to the next iteration.
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | keystone-reset.txt | 22 in order to use mux block registers for all watchdogs.
32 in format: <0>, <2>; It can be in random order and
34 reset watchdogs and can be in random order.
|
| /Documentation/devicetree/bindings/display/tilcdc/ |
| D | panel.txt | 13 - raster-order: Raster Data Order Select: 1=Most-to-least 0=Least-to-most
47 raster-order = <0>;
|
12345678910>>...41