Searched full:routes (Results 1 – 25 of 70) sorted by relevance
123
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-subdev-g-routing.rst | 44 ``VIDIOC_SUBDEV_G_ROUTING`` ioctl and application may enable or disable routes
45 with the ``VIDIOC_SUBDEV_S_ROUTING`` ioctl, by adding or removing routes and
48 ``VIDIOC_SUBDEV_S_ROUTING`` returns the routes back to the user.
56 The ``len_routes`` field indicates the number of routes that can fit in the
57 ``routes`` array allocated by userspace. It is set by applications for both
58 ioctls to indicate how many routes the kernel can return, and is never modified
61 The ``num_routes`` field indicates the number of routes in the routing
63 routes that the application stored in the ``routes`` array. For both ioctls, it
64 is returned by the kernel and indicates how many routes are stored in the
70 both ioctls. This indicates thare are more routes in the routing table than fits
[all …]
|
| D | dev-subdev.rst | 556 Interaction between routes, streams, formats and selections
567 other. Any number of routes from streams on sink pads towards streams on
579 depending on the hardware. In all cases, however, only routes that have the
583 routes or have a fixed routing configuration. If the routes can be disabled, not
584 declaring the routes (or declaring them without
586 disable the routes. ``VIDIOC_SUBDEV_S_ROUTING`` will still return such routes
587 back to the user in the routes array, with the ``V4L2_SUBDEV_STREAM_FL_ACTIVE``
592 pads is possible, and multiple routes (usually up to certain limited number) may
593 be active simultaneously. For such devices, no routes are created by the driver
594 and user-created routes are fully replaced when ``VIDIOC_SUBDEV_S_ROUTING`` is
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | ti,omap4-wugen-mpu | 4 routes interrupts to the GIC, and also serves as a wakeup source. It
18 - Because this HW ultimately routes interrupts to the GIC, the
|
| D | nvidia,tegra20-ictlr.txt | 3 All Tegra SoCs contain a legacy interrupt controller that routes
25 - Because this HW ultimately routes interrupts to the GIC, the
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| D | fsl,cpm1-tsa.yaml | 116 '^fsl,[rt]x-ts-routes$':
119 A list of tuple that indicates the Tx or Rx time-slots routes.
195 fsl,tx-ts-routes = <2 0>, /* TS 0..1 */
200 fsl,rx-ts-routes = <2 0>, /* TS 0..1 */
|
| D | fsl,qe-tsa.yaml | 121 '^fsl,[rt]x-ts-routes$':
124 A list of tuple that indicates the Tx or Rx time-slots routes.
200 fsl,tx-ts-routes = <2 0>, /* TS 0..1 */
205 fsl,rx-ts-routes = <2 0>, /* TS 0..1 */
|
| /Documentation/devicetree/bindings/sound/ |
| D | rt274.txt | 16 Pins on the device (for linking into audio routes) for RT274:
|
| D | tda7419.txt | 15 Pins on the device (for linking into audio routes):
|
| D | rt5660.txt | 29 Pins on the device (for linking into audio routes) for RT5660:
|
| D | wlf,wm8753.yaml | 10 Pins on the device (for linking into audio routes):
|
| D | realtek,rt5631.yaml | 15 Pins on the device (for linking into audio routes):
|
| D | maxim,max9867.yaml | 11 Pins on the device (for linking into audio routes):
|
| D | realtek,alc5632.yaml | 10 Pins on the device (for linking into audio routes):
|
| D | realtek,rt5616.yaml | 10 Pins on the device (for linking into audio routes) for RT5616:
|
| D | rt5668.txt | 30 Pins on the device (for linking into audio routes) for RT5668B:
|
| D | realtek,rt5514.yaml | 15 Pins on the device (for linking into audio routes) for I2C:
|
| D | wlf,wm8904.yaml | 13 Pins on the device (for linking into audio routes):
|
| D | rt5651.txt | 41 Pins on the device (for linking into audio routes) for RT5651:
|
| D | rt5665.txt | 37 Pins on the device (for linking into audio routes) for RT5659/RT5658:
|
| D | everest,es8328.yaml | 11 Pins on the device (for linking into audio routes) are
|
| /Documentation/networking/ |
| D | batman-adv.rst | 10 Layer 2 only and uses and routes (or better: bridges) Ethernet Frames. It
130 $ batctl -m bat0 loglevel routes tt
132 will enable debug messages for when routes and translation table entries change.
|
| D | vrf.rst | 96 Local and connected routes for enslaved devices are automatically moved to
97 the table associated with VRF device. Any additional routes depending on
106 5. Additional VRF routes are added to associated table::
218 On enslavement connected and local routes are automatically moved to the
309 7. Show Routes for a VRF
311 To show routes for a VRF use the ip command to display the table associated
372 Connected routes are moved back to the default table and local entries are
|
| /Documentation/networking/devlink/ |
| D | devlink-dpipe.rst | 170 table contains routes with the same prefix length. The root of the list is
176 host table for directly connected routes, or adjacency table for next-hops.
197 In the case of local routes the LPM lookup already resolves the egress
215 In case of remote routes this table does the ECMP. The LPM lookup results in
|
| /Documentation/sound/soc/ |
| D | dapm.rst | 19 DAPM is based on two basic elements, called widgets and routes:
28 the whole sound card, so some DAPM routes connect two widgets belonging to
261 Similarly, routes connecting them are implemented statically in a ``static
290 In more complex cases the list of DAPM widgets and/or routes can be only
293 separate widgets and routes arrays implementing the case-specific features
|
| /Documentation/devicetree/bindings/misc/ |
| D | ti,j721e-esm.yaml | 17 the SoC, and they are handled by the ESM, which routes them to the proper
|
123