Home
last modified time | relevance | path

Searched full:routed (Results 1 – 25 of 352) sorted by relevance

12345678910>>...15

/linux/arch/arm64/boot/dts/rockchip/
H A Drk3588-jaguar-pre-ict-tester.dtso76 * routed to the mezzanine connector to report a proper
78 * incorrect value if VCC_1V8_S0_1 isn't properly routed,
80 * If VCC_IN_2 is properly routed, GPIO3_A3 should be
82 * GPIO3_A3 isn't properly routed due to soldering
88 * GPIO3_A4 is directly routed to VCC_1V8_S0_2 power
98 * routed to the mezzanine connector to report a proper
100 * incorrect value if VCC_1V8_S0_1 isn't properly routed,
102 * If VCC_IN_1 is properly routed, GPIO3_B2 should be
104 * routed due to soldering issue, because GPIO3_B2
113 * GPIO3_C6 is directly routed to VCC_1V8_S0_1 power
[all …]
/linux/Documentation/devicetree/bindings/leds/
H A Dleds-bcm6328.yaml275 /* USB link/activity routed to USB LED */
282 /* INET activity routed to INET LED */
289 /* EPHY0 link routed to EPHY0 LED */
296 /* EPHY1 link routed to EPHY1 LED */
303 /* EPHY2 link routed to EPHY2 LED */
310 /* EPHY3 link routed to EPHY3 LED */
333 /* USB/INET link/activity routed to USB LED */
340 /* EPHY0/1/2/3 link routed to EPHY0 LED */
363 /* USB link/act and INET act routed to USB LED */
370 /* EPHY3 link routed to EPHY0 LED */
[all …]
/linux/include/linux/bcma/
H A Dbcma_driver_mips.h6 /* 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 */
/linux/Documentation/devicetree/bindings/soc/fsl/cpm_qe/
H A Dfsl,cpm1-scc-qmc.yaml14 serial controller using the same TDM physical interface routed from TSA.
95 Channel assigned Tx time-slots within the Tx time-slots routed by the
101 Channel assigned Rx time-slots within the Rx time-slots routed by the
165 /* Ch16 : First 4 even TS from all routed from TSA */
174 /* Ch17 : First 4 odd TS from all routed from TSA */
183 /* Ch19 : 8 TS (TS 8..15) from all routed from TSA */
H A Dfsl,qe-ucc-qmc.yaml14 serial controller using the same TDM physical interface routed from TSA.
107 Channel assigned Tx time-slots within the Tx time-slots routed by the
113 Channel assigned Rx time-slots within the Rx time-slots routed by the
169 /* Ch16 : First 4 even TS from all routed from TSA */
178 /* Ch17 : First 4 odd TS from all routed from TSA */
187 /* Ch19 : 8 TS (TS 8..15) from all routed from TSA */
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-pci-drivers-ehci_hcd10 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
H A Dsysfs-class-tee6 RPMB frames can be routed to the RPMB device via the
10 "kernel" means that the frames are routed via the RPMB
12 should be assumed that RPMB frames are routed via user
/linux/Documentation/devicetree/bindings/pinctrl/
H A Dsunplus,sp7021-pinctrl.yaml43 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.
/linux/tools/testing/selftests/drivers/net/mlxsw/
H A Dingress_rif_conf_1q.sh6 # 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"
H A Dingress_rif_conf_1d.sh200 # 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"
/linux/arch/arm64/boot/dts/marvell/
H A Dcn9132-clearfog.dts135 /* This bus is also routed to STM32 BMC Microcontroller (U2) */
226 /* Routed to Full PCIe (J4) */
230 /* Routed to USB Hub (U29) */
234 /* Routed to M.2 (CON4) */
238 /* Routed to M.2 (CON5) */
242 /* Routed to M.2 (J21) */
250 /* Routed to mini-PCIe (J14) */
258 /* Routed to various optional PTP related components */
/linux/net/bridge/netfilter/
H A Debtable_broute.c22 * EBT_DROP means the frame will be routed
66 * skb should be routed, not bridged. in ebt_broute()
138 MODULE_DESCRIPTION("Force packets to be routed instead of bridged");
/linux/arch/mips/pci/
H A Dfixup-sni.c30 * 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)
/linux/Documentation/admin-guide/media/
H A Dimx.rst150 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 …]
/linux/arch/arm64/boot/dts/renesas/
H A Drzg3s-smarc-switches.h35 * SW_OFF - The SMARC SER0 signals are routed to M.2 Key E UART
36 * SW_ON - The SMARC SER0 signals are routed to PMOD1
/linux/Documentation/devicetree/bindings/interrupt-controller/
H A Dinterrupts.txt13 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
H A Driscv,cpu-intc.yaml13 to the core. Every interrupt is ultimately routed through a hart's HLIC
22 the HLIC, which are routed via the platform-level interrupt controller
/linux/include/sound/
H A Dseq_virmidi.h55 * ATTACH = input/output events from midi device are routed to the
60 * DISPATCH = input/output events are routed to subscribers.
/linux/drivers/dma/
H A Dlpc32xx-dmamux.c82 dev_dbg(dev, "releasing dma request signal %d routed to %s\n", in lpc32xx_dmamux_release()
133 dev_err(dev, "dma request signal %d busy, routed to %s\n", in lpc32xx_dmamux_reserve()
148 dev_dbg(dev, "dma request signal %d routed to %s\n", in lpc32xx_dmamux_reserve()
/linux/Documentation/devicetree/bindings/clock/
H A Dlpc1850-ccu.txt22 Shall contain a list of phandles for the base clocks routed
26 Shall contain a list of names for the base clock routed
/linux/Documentation/devicetree/bindings/thermal/
H A Dti_soc_thermal.txt20 the talert signal is routed to;
23 line the tshut signal is routed to. The informed GPIO will
/linux/Documentation/devicetree/bindings/mailbox/
H A Dti,omap-mailbox.yaml20 output interrupt lines. An output interrupt line is routed to an interrupt
35 lines can also be routed to different processor sub-systems on DRA7xx as they
36 are routed through the Crossbar, a kind of interrupt router/multiplexer. The
39 NavSS. The interrupt lines from all these clusters are multiplexed and routed
/linux/Documentation/networking/devlink/
H A Dmlxsw.rst97 routed from a disabled router interface (RIF). This can happen during
103 routed through a disabled router interface (RIF). This can happen during
/linux/net/can/
H A DKconfig51 msg sending and can optionally modify routed CAN frames on the fly.
52 CAN frames can be routed between CAN network interfaces (one hop).
/linux/Documentation/devicetree/bindings/gpio/
H A Dgpio.txt159 For lines which are routed to on-board devices, this name should be
168 However, in the case of lines that are routed to a general purpose header
251 Some or all of the GPIOs provided by a GPIO controller may be routed to pins
296 Here, a single GPIO controller has GPIOs 0..9 routed to pin controller
297 pinctrl1's pins 20..29, and GPIOs 10..29 routed to pin controller pinctrl2's

12345678910>>...15