Searched full:split (Results  1 – 25 of 267) sorted by relevance
1234567891011
| /Documentation/devicetree/bindings/display/mediatek/ | 
| D | mediatek,split.yaml | 4 $id: http://devicetree.org/schemas/display/mediatek/mediatek,split.yaml# 7 title: Mediatek display split 14   Mediatek display split, namely SPLIT, is used to split stream to two 16   SPLIT device node must be siblings to the central MMSYS_CONFIG node. 25           - mediatek,mt8173-disp-split 26           - mediatek,mt8195-mdp3-split 28           - const: mediatek,mt6795-disp-split 29           - const: mediatek,mt8173-disp-split 60       - description: SPLIT Clock 76             const: mediatek,mt8195-mdp3-split [all …] 
 | 
| /Documentation/mm/ | 
| D | split_page_table_lock.rst | 2 Split page table lock 8 scalability, split page table lock was introduced. 10 With split page table lock we have separate per-table lock to serialize 11 access to the table. At the moment we use split lock for PTE and PMD 40 Split page table lock for PTE tables is enabled compile-time if 42 If split lock is disabled, all tables are guarded by mm->page_table_lock. 44 Split page table lock for PMD tables is enabled, if it's enabled for PTE 47 Hugetlb and split page table lock 50 Hugetlb can support several page sizes. We use split lock only for PMD 56 	takes pmd split lock for PMD_SIZE page, mm->page_table_lock [all …] 
 | 
| D | transhuge.rst | 14   if necessary, split a transparent hugepage. Therefore these components 46 prevent the page from being split by anyone. 67 that you can't handle natively in your code, you can split it by 133 requests to split pinned huge pages: it expects page count to be equal to 149 clear where references should go after split: it will stay on the head page. 152 pmd can be split at any point and never fails.
  | 
| /Documentation/arch/x86/ | 
| D | buslock.rst | 16 A split lock is any atomic operation whose operand crosses two cache lines. 20 A bus lock is acquired through either split locked access to writeback (WB) 29 mechanisms to detect split locks and bus locks. 31 #AC exception for split lock detection 34 Beginning with the Tremont Atom CPU split lock operations may raise an 35 Alignment Check (#AC) exception when a split lock operation is attempted. 51 |split_lock_detect=|#AC for split lock		|#DB for bus lock	| 60 |		   |split lock in parallel.	|			| 89 generating split lock and bus lock to block the hard real time code to 102 Disable checking for split lock and bus lock. This option can be useful if
  | 
| /Documentation/networking/devlink/ | 
| D | sfc.rst | 23      - For boards where the management function is split between multiple 27      - For boards where the management function is split between multiple 52      - Expansion ROM version. For boards where the expansion ROM is split between
  | 
| D | ice.rst | 238 Port split 242 a predefined set of available port split options for the whole device. 244 A system reboot is required for port split to be applied. 246 The following command will select the port split option with 4 ports: 250     $ devlink port split pci/0000:16:00.0/0 count 4 253 each ``split`` and ``unsplit`` command. The first option is the default. 257     ice 0000:16:00.0: Available port split options and max port speeds (Gbps): 258     ice 0000:16:00.0: Status  Split      Quad 0          Quad 1 267 There could be multiple FW port options with the same port split count. When 268 the same port split count request is issued again, the next FW port option with [all …] 
 | 
| /Documentation/devicetree/bindings/dma/ti/ | 
| D | k3-bcdma.yaml | 17   BCDMA includes block copy channels and Split channels. 23   Split channels can be used to service PSI-L based peripherals. 28   PDMAs can be configured via BCDMA split channel's peer registers to match with 50         0 - split channel 56         if cell 1 is 0 (split channel): 100       Array of BCDMA split tx channel resource subtypes for resource allocation 111       Array of BCDMA split rx channel resource subtypes for resource allocation
  | 
| D | k3-pktdma.yaml | 17   PKTDMA only includes Split channels to service PSI-L based peripherals. 23   PDMAs can be configured via PKTDMA split channel's peer registers to match 76       Array of PKTDMA split tx channel resource subtypes for resource allocation 87       Array of PKTDMA split tx flow resource subtypes for resource allocation 98       Array of PKTDMA split rx channel resource subtypes for resource allocation 109       Array of PKTDMA split rx flow resource subtypes for resource allocation
  | 
| /Documentation/networking/ | 
| D | devmem.rst | 42 normally. The NIC must support header split to achieve this. 79 Header split, flow steering, & RSS are required features for devmem TCP. 81 Header split is used to split incoming packets into a header buffer in host 87 Enable header split & flow steering:: 89 	# enable header split 90 	ethtool -G eth1 tcp-data-split on 206   This typically happens when the NIC is unable to split the packet at the
  | 
| /Documentation/admin-guide/mm/ | 
| D | transhuge.rst | 206 and will therefore be split under memory presure if they are considered 469 	is incremented every time a huge page is split into base 475 	is incremented if kernel fails to split huge 479 	is incremented when a huge page is put onto split 481 	splitting it would free up some memory. Pages on split queue are 482 	going to be split under memory pressure. 485 	is incremented when a huge page on the split queue was split 491 	is incremented every time a PMD split into table of PTEs. 493 	munmap() on part of huge page. It doesn't split huge page, only 510 	is incremented if a huge page has to be split before swapout. [all …] 
 | 
| /Documentation/devicetree/bindings/display/bridge/ | 
| D | fsl,imx8qxp-ldb.yaml | 23   LDB split mode to support a dual link LVDS display.  The channel indexes 29   in dual mode or split mode.  In dual mode, the two channels output identical 30   data.  In split mode, channel0 outputs odd pixels and channel1 outputs even 66       A phandle which points to companion LDB which is used in LDB split mode.
  | 
| /Documentation/trace/ | 
| D | function-graph-fold.vim | 29   let s = split(getline(v:foldstart), '|', 1) 33     let e = split(getline(v:foldend), '|', 1)
  | 
| /Documentation/sphinx/ | 
| D | maintainers_include.py | 122                     field, details = line.split(':', 1) 146             # Re-split on any added newlines in any above parsing. 148                 for separated in output.split('\n'): 163             for separated in field_content.split('\n'): 183             (path, tail) = os.path.split(path)
  | 
| D | kernel_feat.py | 102         for line in lines.split("\n"): 121             for l in lines.split("\n"): 125         for c, l in enumerate(lines.split("\n")):
  | 
| D | kerneldoc.py | 84             export_file_patterns = str(self.options.get('export')).split() 87             export_file_patterns = str(self.options.get('internal')).split() 91             identifiers = self.options.get('identifiers').split() 99             no_identifiers = self.options.get('no-identifiers').split()
  | 
| /Documentation/gpu/amdgpu/display/ | 
| D | dc-debug.rst | 33 * Pipe split can be observed if there are two bars with a difference in height 39 split configuration. 48 Pipe Split Debug 57 In this case, if you have a pipe split, you will see one small red bar at the
  | 
| /Documentation/gpu/ | 
| D | komeda-kms.rst | 66 introduces Layer Split, which splits the whole image to two half parts and feeds 73 Similar to Layer Split, but Splitter is used for writeback, which splits the 238    :alt: Layer Split digraph 239    :caption: Layer Split pipeline 269    :alt: split writeback digraph 270    :caption: Writeback(output) Split data flow 328 achieve this, split the komeda device into two layers: CORE and CHIP. 382 -   Layer Split, See `Layer(input) pipeline`_ 386     imports an edge problem or effect in the middle of the image after the split. 387     To avoid such a problem, it needs a complicated Split calculation and some
  | 
| /Documentation/devicetree/bindings/remoteproc/ | 
| D | ti,k3-r5f-rproc.yaml | 16   Split mode providing two individual compute cores for doubling the compute 72       It should be either a value of 1 (LockStep mode) or 0 (Split mode) on 76       It  should be either a value of 0 (Split mode) or 2 (Single-CPU mode) and 77       default is Split mode if omitted. 99       internal memories split between two banks - TCMA and TCMB (further 144 # The following properties are mandatory for R5F Core0 in both LockStep and Split 145 # modes, and are mandatory for R5F Core1 _only_ in Split mode. They are unused for
  | 
| /Documentation/admin-guide/device-mapper/ | 
| D | dm-crypt.rst | 171       is received, dm-crypt will split the request. The splitting improves 172       concurrency (the split requests could be encrypted in parallel by multiple 178       is received, dm-crypt will split the request. The splitting improves 179       concurrency (the split requests could be encrypted in parallel by multiple
  | 
| /Documentation/block/ | 
| D | biovecs.rst | 76    bios with more than a single bvec! Now, we can efficiently split arbitrary 79    Care must be taken to ensure the biovec isn't freed while the split bio is 115  * The current interface allows the block layer to split bios as needed, so we 128   shouldn't use them because the bio may have been split before it reached the
  | 
| /Documentation/ABI/obsolete/ | 
| D | sysfs-driver-hid-roccat-kovaplus | 66 		press of a button. A profile is split in settings and buttons. 81 		press of a button. A profile is split in settings and buttons. 93 		press of a button. A profile is split in settings and buttons. 109 		press of a button. A profile is split in settings and buttons.
  | 
| D | sysfs-driver-hid-roccat-pyra | 55 		press of a button. A profile is split in settings and buttons. 70 		press of a button. A profile is split in settings and buttons. 82 		press of a button. A profile is split in settings and buttons. 98 		press of a button. A profile is split in settings and buttons.
  | 
| /Documentation/scheduler/ | 
| D | sched-nice-design.rst | 78 and another task with +2, the CPU split between the two tasks would 80 CPU split was different than if it was at +5 or +10. 102 utilization "split" between them as running a nice -5 and a nice -4
  | 
| /Documentation/driver-api/media/drivers/ccs/ | 
| D | mk-ccs-regs | 202 	$args = [split /,\s*/, $args]; 214 	my @l = split "\n", $_; 290 			my ($bit, $addr) = split /\t+/; 295 			my @a = split /\s+/; 306 			my ($enum, $addr) = split /\s+/; 310 			my ($arg, $min, $max, $elsize, @discontig) = split /\s+/; 344 					my ($lim, $offset) = split /,/, $d->[0]; 372 				my ($first_discontig) = split /,/, $da->{discontig}->[0]; 400 	my ($name, $addr, @flags) = split /\t+/, $_;
  | 
| /Documentation/devicetree/bindings/memory-controllers/ | 
| D | intel,ixp4xx-expansion-peripheral-props.yaml | 64   intel,ixp4xx-eb-ahb-split-transfers: 65     description: Enable AHB split transfers.
  | 
        1234567891011