Searched full:routed (Results 1 – 25 of 727) sorted by relevance
12345678910>>...30
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6328.yaml | 279 /* USB link/activity routed to USB LED */
286 /* INET activity routed to INET LED */
293 /* EPHY0 link routed to EPHY0 LED */
300 /* EPHY1 link routed to EPHY1 LED */
307 /* EPHY2 link routed to EPHY2 LED */
314 /* EPHY3 link routed to EPHY3 LED */
337 /* USB/INET link/activity routed to USB LED */
344 /* EPHY0/1/2/3 link routed to EPHY0 LED */
367 /* USB link/act and INET act routed to USB LED */
374 /* EPHY3 link routed to EPHY0 LED */
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6328.txt | 207 /* USB link/activity routed to USB LED */
213 /* INET activity routed to INET LED */
219 /* EPHY0 link routed to EPHY0 LED */
225 /* EPHY1 link routed to EPHY1 LED */
231 /* EPHY2 link routed to EPHY2 LED */
237 /* EPHY3 link routed to EPHY3 LED */
259 /* USB/INET link/activity routed to USB LED */
265 /* EPHY0/1/2/3 link routed to EPHY0 LED */
287 /* USB link/act and INET act routed to USB LED */
293 /* EPHY3 link routed to EPHY0 LED */
[all …]
|
| /kernel/linux/linux-6.6/include/linux/bcma/ |
| D | bcma_driver_mips.h | 6 /* which sbflags get routed to mips interrupt 1 */
9 /* which sbflags get routed to mips interrupt 2 */
12 /* which sbflags get routed to mips interrupt 3 */
15 /* which sbflags get routed to mips interrupt 4 */
|
| /kernel/linux/linux-5.10/include/linux/bcma/ |
| D | bcma_driver_mips.h | 6 /* which sbflags get routed to mips interrupt 1 */
9 /* which sbflags get routed to mips interrupt 2 */
12 /* which sbflags get routed to mips interrupt 3 */
15 /* which sbflags get routed to mips interrupt 4 */
|
| /kernel/linux/linux-5.10/Documentation/networking/devlink/ |
| D | devlink-trap.rst | 180 routed and they have a unicast destination IP and a multicast destination
185 routed and their destination IP is the loopback address (i.e., 127.0.0.0/8
190 routed and their source IP is multicast (i.e., 224.0.0.0/8 and ff::/8)
194 routed and their source IP is the loopback address (i.e., 127.0.0.0/8 and ::1/128)
198 routed and their IP header is corrupted: wrong checksum, wrong IP version
203 routed and their source IP is limited broadcast (i.e., 255.255.255.255/32)
207 be routed and their IPv6 multicast destination IP has a reserved scope
212 be routed and their IPv6 multicast destination IP has an interface-local scope
216 - Traps packets that should have been routed by the device, but were bigger
237 supposed to be routed. For example, IGMP queries can be flooded by the
[all …]
|
| D | mlxsw.rst | 73 routed from a disabled router interface (RIF). This can happen during
79 routed through a disabled router interface (RIF). This can happen during
|
| /kernel/linux/linux-6.6/Documentation/networking/devlink/ |
| D | devlink-trap.rst | 180 routed and they have a unicast destination IP and a multicast destination
185 routed and their destination IP is the loopback address (i.e., 127.0.0.0/8
190 routed and their source IP is multicast (i.e., 224.0.0.0/8 and ff::/8)
194 routed and their source IP is the loopback address (i.e., 127.0.0.0/8 and ::1/128)
198 routed and their IP header is corrupted: wrong checksum, wrong IP version
203 routed and their source IP is limited broadcast (i.e., 255.255.255.255/32)
207 be routed and their IPv6 multicast destination IP has a reserved scope
212 be routed and their IPv6 multicast destination IP has an interface-local scope
216 - Traps packets that should have been routed by the device, but were bigger
237 supposed to be routed. For example, IGMP queries can be flooded by the
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| D | fsl,cpm1-scc-qmc.yaml | 14 serial controller using the same TDM physical interface routed from TSA.
94 Channel assigned Tx time-slots within the Tx time-slots routed by the
100 Channel assigned Rx time-slots within the Rx time-slots routed by the
138 /* Ch16 : First 4 even TS from all routed from TSA */
147 /* Ch17 : First 4 odd TS from all routed from TSA */
156 /* Ch19 : 8 TS (TS 8..15) from all routed from TSA */
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-bus-pci-drivers-ehci_hcd | 10 high-speed device is plugged in, the connection is routed
12 is plugged in, the connection is routed to the companion
17 connection to be routed to the companion controller.
19 file causes connections on that port to be routed to the
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-pci-drivers-ehci_hcd | 10 high-speed device is plugged in, the connection is routed
12 is plugged in, the connection is routed to the companion
17 connection to be routed to the companion controller.
19 file causes connections on that port to be routed to the
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/ |
| D | sunplus,sp7021-pinctrl.yaml | 43 can be routed to any pins of fully pin-mux pins.
47 routed to GPIO 10 (3 - 1 + 8 = 10).
49 routed to GPIO 11 (4 - 1 + 8 = 11).
51 be routed to GPIO 12 (5 - 1 + 8 = 12).
53 be routed to GPIO 13 (6 - 1 + 8 = 13).
57 be routed to GPIO 27 (20 - 1 + 8 = 27).
59 will be routed to GPIO 28 (21 - 1 + 9 = 28).
62 routed to any of 64 'fully pin-mux' pins.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/connector/ |
| D | usb-connector.yaml | 179 # Micro-USB connector with HS lines routed via controller (MUIC).
189 # USB-C connector attached to CC controller (s2mm005), HS lines routed
191 # DisplayPort video lines are routed to the connector via SS mux in USB3 PHY.
242 # with SS 2:1 MUX. HS lines routed to SoC, SS lines routed to the MUX and
281 # Micro-USB connector with HS lines routed via controller (MUIC) and MHL
|
| /kernel/linux/linux-6.6/tools/testing/selftests/drivers/net/mlxsw/ |
| D | ingress_rif_conf_1q.sh | 6 # mapping and that packets can be routed via port which is added after the FID
195 # packets can be routed via the existing mapping.
209 check_err $? "Packets were not routed in hardware"
228 # RIF. Verify that packets can be routed via port which is added after
244 check_err $? "Packets were not routed in hardware"
|
| D | ingress_rif_conf_1d.sh | 200 # that packets can be routed via the existing mapping.
214 check_err $? "Packets were not routed in hardware"
231 # can be routed via the new mapping.
245 check_err $? "Packets were not routed in hardware"
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | armada-385-turris-omnia.dts | 167 /* routed to PCIe0/mSATA connector (CN7A) */
175 /* routed to PCIe1/USB2 connector (CN61A) */
183 /* routed to PCIe2 connector (CN62A) */
191 /* routed to SFP+ */
361 /* MISO, MOSI, SCLK and CS2 are routed to pin header CN11 */
|
| /kernel/linux/linux-5.10/arch/mips/pci/ |
| D | fixup-sni.c | 30 * Device 0: PCI EISA Bridge (directly routed)
31 * Device 1: NCR53c810 SCSI (directly routed)
32 * Device 2: PCnet32 Ethernet (directly routed)
33 * Device 3: VGA (routed to INTB)
|
| /kernel/linux/linux-6.6/arch/mips/pci/ |
| D | fixup-sni.c | 30 * Device 0: PCI EISA Bridge (directly routed)
31 * Device 1: NCR53c810 SCSI (directly routed)
32 * Device 2: PCnet32 Ethernet (directly routed)
33 * Device 3: VGA (routed to INTB)
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/connector/ |
| D | usb-connector.yaml | 273 # Micro-USB connector with HS lines routed via controller (MUIC).
283 # USB-C connector attached to CC controller (s2mm005), HS lines routed
285 # DisplayPort video lines are routed to the connector via SS mux in USB3 PHY.
349 # with SS 2:1 MUX. HS lines routed to SoC, SS lines routed to the MUX and
388 # Micro-USB connector with HS lines routed via controller (MUIC) and MHL
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | imx.rst | 150 containing each virtual channel that are routed to CSIs or video
153 On i.MX6 solo/dual-lite, all four virtual channel buses are routed to
157 On i.MX6 Quad, virtual channel 0 is routed to IPU1-CSI0 (after selected
159 and IPU2-CSI0, respectively, and virtual channel 3 is routed to
194 When the direct source pad is routed to the ipuX_ic_prp entity, frames
198 When the direct source pad is routed to the ipuX_vdic entity, the VDIC
204 source pad is routed to a capture device node, with a node name of the
315 routed to a capture device node, with a node name of the format
330 pad from ipuX_ic_prp, and a single source pad. The source pad is routed
427 routed as follows: vc0 to the IPU1 CSI0 mux, vc1 directly to IPU1 CSI1,
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/media/ |
| D | imx.rst | 150 containing each virtual channel that are routed to CSIs or video
153 On i.MX6 solo/dual-lite, all four virtual channel buses are routed to
157 On i.MX6 Quad, virtual channel 0 is routed to IPU1-CSI0 (after selected
159 and IPU2-CSI0, respectively, and virtual channel 3 is routed to
194 When the direct source pad is routed to the ipuX_ic_prp entity, frames
198 When the direct source pad is routed to the ipuX_vdic entity, the VDIC
204 source pad is routed to a capture device node, with a node name of the
315 routed to a capture device node, with a node name of the format
330 pad from ipuX_ic_prp, and a single source pad. The source pad is routed
427 routed as follows: vc0 to the IPU1 CSI0 mux, vc1 directly to IPU1 CSI1,
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | interrupts.txt | 13 which the interrupts are routed; see section 2 below for details.
20 interrupts are routed and contains a single phandle referring to the interrupt
116 interrupts routed to them, so that they can wakeup the SoC from suspend. These
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/interrupt-controller/ |
| D | interrupts.txt | 13 which the interrupts are routed; see section 2 below for details.
20 interrupts are routed and contains a single phandle referring to the interrupt
116 interrupts routed to them, so that they can wakeup the SoC from suspend. These
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mailbox/ |
| D | omap-mailbox.txt | 11 interrupt lines. An output interrupt line is routed to an interrupt controller
25 routed to different processor sub-systems on DRA7xx as they are routed through
29 all these clusters are multiplexed and routed to different processor subsystems
|
| /kernel/linux/linux-6.6/include/sound/ |
| D | seq_virmidi.h | 55 * ATTACH = input/output events from midi device are routed to the
60 * DISPATCH = input/output events are routed to subscribers.
|
| /kernel/linux/linux-5.10/include/sound/ |
| D | seq_virmidi.h | 55 * ATTACH = input/output events from midi device are routed to the
60 * DISPATCH = input/output events are routed to subscribers.
|
12345678910>>...30