| /Documentation/userspace-api/media/v4l/ | 
| D | vidioc-dbg-g-chip-info.rst | 49 To query the driver applications must initialize the ``match.type`` and 50 ``match.addr`` or ``match.name`` fields of a struct 56 When ``match.type`` is ``V4L2_CHIP_MATCH_BRIDGE``, ``match.addr`` 58 chips by starting at zero and incrementing ``match.addr`` by one until 64 When ``match.type`` is ``V4L2_CHIP_MATCH_SUBDEV``, ``match.addr`` 80 .. _name-v4l2-dbg-match: 89       - See :ref:`name-chip-match-types` for a list of possible types. 94       - Match a chip by this number, interpreted according to the ``type`` 98       - Match a chip by this name, interpreted according to the ``type`` 114       - ``match`` [all …] 
 | 
| D | vidioc-dbg-g-register.rst | 55 ``match.type`` and ``match.addr`` or ``match.name`` fields select a chip 59 To read a register applications must initialize the ``match.type``, 60 ``match.addr`` or ``match.name`` and ``reg`` fields, and call 65 When ``match.type`` is ``V4L2_CHIP_MATCH_BRIDGE``, ``match.addr`` 71 When ``match.type`` is ``V4L2_CHIP_MATCH_SUBDEV``, ``match.addr`` 99       - See :ref:`chip-match-types` for a list of possible types. 104       - Match a chip by this number, interpreted according to the ``type`` 108       - Match a chip by this name, interpreted according to the ``type`` 121       - ``match`` 122       - How to match the chip, see :c:type:`v4l2_dbg_match`. [all …] 
 | 
| /Documentation/devicetree/bindings/timer/ | 
| D | renesas,rz-mtu3.yaml | 22         - Waveform output on compare match 27         - Simultaneous clearing on compare match or input capture 122       - description: MTU0.TGRA input capture/compare match 123       - description: MTU0.TGRB input capture/compare match 124       - description: MTU0.TGRC input capture/compare match 125       - description: MTU0.TGRD input capture/compare match 127       - description: MTU0.TGRE compare match 128       - description: MTU0.TGRF compare match 129       - description: MTU1.TGRA input capture/compare match 130       - description: MTU1.TGRB input capture/compare match [all …] 
 | 
| D | brcm,bcm2835-system-timer.yaml | 28       - description: System Timer Compare 0 match (used by VideoCore GPU) 29       - description: System Timer Compare 1 match (usable for ARM core) 30       - description: System Timer Compare 2 match (used by VideoCore GPU) 31       - description: System Timer Compare 3 match (usable for ARM core)
  | 
| D | renesas,mtu2.yaml | 15   and programmable compare match. 17   Channels share hardware resources but their counter and compare match value are
  | 
| /Documentation/driver-api/ | 
| D | isa.rst | 14 use the .match() method for the actual device discovery. 18 the platform_bus, this isa_bus also distributes match() up to the 44 callbacks, and as indicated that .match callback. 58 With this additional .match() callback ISA drivers have all options. If 60 of the old .probe in .match, which would only keep them registered after 63 changeover to platform devices, it could just not provide a .match() and 68 could conceivably succeed, it could use .match() for the prerequisites 79 This causes the bus match method to be called for them, which is:: 86 			if (!isa_driver->match || 87 				isa_driver->match(dev, to_isa_dev(dev)->id)) [all …] 
 | 
| D | tee.rst | 13 match(): 15   match for device UUID. If a match is found, then this particular device is
  | 
| /Documentation/sphinx/ | 
| D | automarkup.py | 110         # Include any text prior to match as a normal text node. 138 # own C role, but both match the same regex, so we try both. 140 def markup_func_ref_sphinx3(docname, app, match):  argument 145     base_target = match.group(2) 146     target_text = nodes.Text(match.group(0)) 181 def markup_c_ref(docname, app, match):  argument 205     base_target = match.group(2) 206     target_text = nodes.Text(match.group(0)) 216             if not (match.re == RE_function and target in Skipfuncs): 217                 lit_text = nodes.literal(classes=['xref', 'c', class_str[match.re]]) [all …] 
 | 
| D | cdomain.py | 60 def markup_namespace(match):  argument 63     namespace = match.group(1) 71 def markup_macro(match):  argument 72     return ".. c:function:: " + match.group(1) + ' ' + match.group(2) 80 def markup_ctype(match):  argument 81     return ".. c:type:: " + match.group(2) 88 def markup_ctype_refs(match):  argument 89     return ":c:type:`" + match.group(2) + '`' 95 def markup_c_expr(match):  argument 96     return '\\ ``' + match.group(2) + '``\\ ' [all …] 
 | 
| D | kernel_abi.py | 112             match = line_regex.search(line) 113             if match: 114                 new_f = match.group(1) 128                 ln = int(match.group(2)) - 1
  | 
| /Documentation/networking/devlink/ | 
| D | devlink-dpipe.rst | 15 For example, the routing longest prefix match (LPM) algorithm used by the 46 modeled as a graph of match/action tables. Each table represents a specific 123 Match  section in Model 126 Matches are kept primitive and close to hardware operation. Match types like 130   * ``field_exact``: Exact match on a specific field. 131   * ``field_exact_mask``: Exact match on a specific field after masking. 132   * ``field_range``: Match on a specific range. 142 Similar to match, the actions are kept primitive and close to hardware 155 match/action values and specific counter. By dumping the tables content the 184       match: { meta.vr_id: exact, [all …] 
 | 
| /Documentation/admin-guide/perf/ | 
| D | arm-cmn.rst | 38   match the underlying pmu_event0_id encoding for the pmu_event_sel 57 The flit match value and mask are passed in config1 and config2 ("val" 60 Where a watchpoint needs to match fields from both match groups on the 63 pair of combined events will be attributed to the primary match.
  | 
| /Documentation/pcmcia/ | 
| D | devicetable.rst | 15 struct pcmcia_device_id[] entries which match devices to drivers. 17 If you want to match product ID strings, you also need to pass the crc32 18 hashes of the string to the macro, e.g. if you want to match the product ID
  | 
| /Documentation/driver-api/driver-model/ | 
| D | binding.rst | 28 ID of the device must match one of the device IDs that the driver 32 a device against the IDs of a driver. The bus returns 1 if a match was 35 int match(struct device * dev, struct device_driver * drv); 37 If a match is found, the device's driver field is set to the driver 83 The bus's list of devices is iterated over to find a match. Devices
  | 
| D | bus.rst | 17 optionally initialize the match callback:: 21           .match	= pci_bus_match, 41 match(): Attaching Drivers to Devices 49 The purpose of the match callback is to give the bus an opportunity to 56 iterated over, and the match callback is called for each device that
  | 
| /Documentation/infiniband/ | 
| D | tag_matching.rst | 7 match the following source and destination parameters: 15 message envelopes may match, the pair that includes the earliest posted-send 52 placed in the unexpected message list. Otherwise the match is processed, 58 the software unexpected message list for a matching receive. If a match is 61 depending on data size. If no match is found, the entire pre-posted receive
  | 
| /Documentation/devicetree/bindings/sifive/ | 
| D | sifive-blocks-ip-versioning.txt | 22 Driver developers can use compatible string "match" values such as 26 match on these IP block-specific compatible strings. 32 or other system software can match on this string to apply them.  The
  | 
| /Documentation/admin-guide/ | 
| D | dynamic-debug-howto.rst | 97 You can also use wildcards in each query term. The match rule supports 99 character). For example, you can match all usb drivers:: 106   command ::= match-spec* flags-spec 108 The match-spec's select *prdbgs* from the catalog, upon which to apply 113 A match specification is a keyword, which selects the attribute of 117   match-spec ::= 'func' string | 169     string.  Note that the string does not need to match the 179 	format nfsd:\040SETATTR // one way to match a format with whitespace 180 	format "nfsd: SETATTR"  // a neater way to match a format with whitespace 181 	format 'nfsd: SETATTR'  // yet another way to match a format with whitespace [all …] 
 | 
| /Documentation/devicetree/bindings/mtd/partitions/ | 
| D | ubi-volume.yaml | 20       Match UBI volume ID 25       Match UBI volume ID
  | 
| /Documentation/devicetree/bindings/pci/ | 
| D | cdns-pcie-host.yaml | 25   cdns,no-bar-match-nbits: 27       Set into the no BAR match register to configure the number of least
  | 
| /Documentation/networking/ | 
| D | fib_trie.rst | 37 	verify that they actually do match the key we are searching for. 127 If we find a match, we are done. 129 If we don't find a match, we enter prefix matching mode. The prefix length, 137 the child index until we find a match or the child index consists of nothing but 143 At this point we will repeatedly descend subtries to look for a match, and there
  | 
| /Documentation/ABI/testing/ | 
| D | sysfs-class-rc | 52 		If the hardware supports it then scancodes which do not match 69 		If the hardware supports it then scancodes which do not match 113 		scancodes which match the filter will wake the system from e.g. 132 		scancodes which match the filter will wake the system from e.g.
  | 
| /Documentation/userspace-api/media/rc/ | 
| D | rc-sysfs-nodes.rst | 65 supports it then scancodes which do not match the filter will be 81 If the hardware supports it then scancodes which do not match the filter 124 scancodes which match the filter will wake the system from e.g. suspend 141 scancodes which match the filter will wake the system from e.g. suspend
  | 
| /Documentation/devicetree/bindings/powerpc/fsl/ | 
| D | srio-rmu.txt | 15 	The version X.Y should match the general SRIO controller's IP Block 46 	The version X.Y should match the general SRIO controller's IP Block 76 	The version X.Y should match the general SRIO controller's IP Block 106 	The version X.Y should match the general SRIO controller's IP Block
  | 
| /Documentation/w1/masters/ | 
| D | ds2490.rst | 36   1 reset bus, 2 write the match rom command and slave rom id, 3 block 37   write and read data.  The write buffer needs to have the match rom 55   match reads and writes as well as data sizes.  Reads and
  |