Searched full:match (Results 1 – 25 of 348) sorted by relevance
12345678910>>...14
| /Documentation/media/uapi/v4l/ |
| D | vidioc-dbg-g-register.rst | 62 ``match.type`` and ``match.addr`` or ``match.name`` fields select a chip
66 To read a register applications must initialize the ``match.type``,
67 ``match.addr`` or ``match.name`` and ``reg`` fields, and call
72 When ``match.type`` is ``V4L2_CHIP_MATCH_BRIDGE``, ``match.addr``
78 When ``match.type`` is ``V4L2_CHIP_MATCH_SUBDEV``, ``match.addr``
107 - See :ref:`chip-match-types` for a list of possible types.
113 - Match a chip by this number, interpreted according to the ``type``
118 - Match a chip by this name, interpreted according to the ``type``
130 - ``match``
131 - How to match the chip, see :c:type:`v4l2_dbg_match`.
[all …]
|
| D | vidioc-dbg-g-chip-info.rst | 57 To query the driver applications must initialize the ``match.type`` and
58 ``match.addr`` or ``match.name`` fields of a struct
64 When ``match.type`` is ``V4L2_CHIP_MATCH_BRIDGE``, ``match.addr``
66 chips by starting at zero and incrementing ``match.addr`` by one until
72 When ``match.type`` is ``V4L2_CHIP_MATCH_SUBDEV``, ``match.addr``
89 .. _name-v4l2-dbg-match:
98 - See :ref:`name-chip-match-types` for a list of possible types.
104 - Match a chip by this number, interpreted according to the ``type``
109 - Match a chip by this name, interpreted according to the ``type``
124 - ``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/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 | 113 Another way is to use wildcards. The match rule supports ``*`` (matches
115 example, you can match all usb drivers::
119 At the syntactical level, a command comprises a sequence of match
122 command ::= match-spec* flags-spec
124 The match-spec's are used to choose a subset of the known pr_debug()
127 match-specs will select all debug statement callsites.
129 A match specification comprises a keyword, which controls the
133 match-spec ::= 'func' string |
180 string. Note that the string does not need to match the
190 format nfsd:\040SETATTR // one way to match a format with whitespace
[all …]
|
| /Documentation/networking/ |
| D | fib_trie.txt | 33 verify that they actually do match the key we are searching for.
123 If we find a match, we are done.
125 If we don't find a match, we enter prefix matching mode. The prefix length,
133 the child index until we find a match or the child index consists of nothing but
139 At this point we will repeatedly descend subtries to look for a match, and there
|
| D | openvswitch.txt | 21 no match, it queues the packet to userspace for processing (as part of
101 A wildcarded flow can represent a group of exact match flows. Each '1' bit
102 in the mask specifies a exact match with the corresponding bit in the flow key.
103 A '0' bit specifies a don't care bit, which will match either a '1' or '0' bit
109 match flow, or reduce the number of don't care bits in the kernel to less than
121 When interacting with userspace, the kernel should maintain the match portion
129 can match at most one flow, wildcarded or not. The current implementation
137 An alternative to using the original match portion of a key as the handle for
|
| /Documentation/devicetree/bindings/timer/ |
| D | renesas,mtu2.txt | 4 clock inputs and programmable compare match.
6 Channels share hardware resources but their counter and compare match value
|
| D | renesas,tmu.txt | 4 programmable compare match.
6 Channels share hardware resources but their counter and compare match value
|
| D | renesas,cmt.txt | 1 * Renesas R-Car Compare Match Timer (CMT)
4 inputs and programmable compare match.
6 Channels share hardware resources but their counter and compare match value
9 position of the channel in the CMT and don't match the channel numbers in the
|
| /Documentation/devicetree/bindings/pci/ |
| D | cdns,cdns-pcie-host.txt | 22 - cdns,no-bar-match-nbits: Set into the no BAR match register to configure the
41 cdns,no-bar-match-nbits = <32>;
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-rc | 44 If the hardware supports it then scancodes which do not match
59 If the hardware supports it then scancodes which do not match
93 scancodes which match the filter will wake the system from e.g.
108 scancodes which match the filter will wake the system from e.g.
|
| /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 should match reads and writes as well as data sizes. Reads and
|
| /Documentation/ABI/stable/ |
| D | sysfs-firmware-efi-vars | 37 should always match the GUID in the
50 match byte for byte with the structure
|
| /Documentation/media/uapi/rc/ |
| D | rc-sysfs-nodes.rst | 72 supports it then scancodes which do not match the filter will be
88 If the hardware supports it then scancodes which do not match the filter
131 scancodes which match the filter will wake the system from e.g. suspend
148 scancodes which match the filter will wake the system from e.g. suspend
|
| /Documentation/devicetree/bindings/mfd/ |
| D | lp87565.txt | 11 populated under regulators node. xxx should match
57 populated under regulators node. xxx should match
|
| /Documentation/devicetree/bindings/goldfish/ |
| D | audio.txt | 7 - compatible : should contain "google,goldfish-audio" to match emulator
|
| D | tty.txt | 7 - compatible : should contain "google,goldfish-tty" to match emulator
|
| D | battery.txt | 7 - compatible : should contain "google,goldfish-battery" to match emulator
|
| D | pipe.txt | 7 - compatible : should contain "google,android-pipe" to match emulator
|
12345678910>>...14