/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/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 …]
|
/Documentation/sphinx/ |
D | automarkup.py | 103 # Include any text prior to match as a normal text node. 121 # own C role, but both match the same regex, so we try both. 123 def markup_func_ref_sphinx3(docname, app, match): argument 131 target = match.group(2) 132 target_text = nodes.Text(match.group(0)) 158 def markup_c_ref(docname, app, match): argument 182 target = match.group(2) 183 target_text = nodes.Text(match.group(0)) 185 if not ((match.re == RE_function and target in Skipfuncs) 187 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 | 157 match = line_regex.search(line) 158 if match: 159 new_f = match.group(1) 170 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/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/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/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 | 121 Another way is to use wildcards. The match rule supports ``*`` (matches 123 example, you can match all usb drivers:: 127 At the syntactical level, a command comprises a sequence of match 130 command ::= match-spec* flags-spec 132 The match-spec's are used to choose a subset of the known pr_debug() 135 match-specs will select all debug statement callsites. 137 A match specification comprises a keyword, which controls the 141 match-spec ::= 'func' string | 192 string. Note that the string does not need to match the 202 format nfsd:\040SETATTR // one way to match a format with whitespace [all …]
|
/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
|
D | openvswitch.rst | 24 no match, it queues the packet to userspace for processing (as part of 104 A wildcarded flow can represent a group of exact match flows. Each '1' bit 105 in the mask specifies a exact match with the corresponding bit in the flow key. 106 A '0' bit specifies a don't care bit, which will match either a '1' or '0' bit 112 match flow, or reduce the number of don't care bits in the kernel to less than 124 When interacting with userspace, the kernel should maintain the match portion 132 can match at most one flow, wildcarded or not. The current implementation 140 An alternative to using the original match portion of a key as the handle for
|
/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.
|
D | sysfs-bus-pci-devices-aer_stats | 19 TOTAL_ERR_COR at the end of the file may not match the actual 40 TOTAL_ERR_FATAL at the end of the file may not match the actual 70 TOTAL_ERR_NONFATAL at the end of the file may not match the
|
/Documentation/devicetree/bindings/timer/ |
D | renesas,tmu.txt | 4 programmable compare match. 6 Channels share hardware resources but their counter and compare match value
|
D | renesas,mtu2.yaml | 15 and programmable compare match. 17 Channels share hardware resources but their counter and compare match value are
|
/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/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/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 should match reads and writes as well as data sizes. Reads and
|
/Documentation/crypto/ |
D | asymmetric-keys.rst | 53 This can then be used to refer to the key, either by complete match or by 54 partial match. The key type may also use other criteria to refer to a key. 56 The asymmetric key type's match function can then perform a wider range of 60 1) If the criterion string is of the form "id:<hexdigits>" then the match 62 after the "id:" match the tail. For instance:: 66 will match a key with fingerprint:: 71 match will match the ID as in (1), but with the added restriction that 152 doesn't match.
|