Home
last modified time | relevance | path

Searched refs:routed (Results 1 – 74 of 74) sorted by relevance

/linux-4.4.14/Documentation/devicetree/bindings/leds/
Dleds-bcm6328.txt207 /* 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 …]
/linux-4.4.14/Documentation/ABI/testing/
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
/linux-4.4.14/Documentation/devicetree/bindings/thermal/
Dti_soc_thermal.txt20 the talert signal is routed to;
23 line the tshut signal is routed to. The informed GPIO will
/linux-4.4.14/Documentation/devicetree/bindings/clock/
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
Dexynos5260-clock.txt29 These clocks are fed into the clock controller and then routed to
/linux-4.4.14/net/can/
DKconfig49 msg sending and can optionally modify routed CAN frames on the fly.
50 CAN frames can be routed between CAN network interfaces (one hop).
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dv3-v360epc-pci.txt15 as routed on the system.
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dmsi-pic.txt20 and routed to the host interrupt controller. the interrupts should
26 are routed to IPIC, and for 85xx/86xx cpu the interrupts are routed
/linux-4.4.14/Documentation/ia64/
DIRQ-redir.txt49 The IRQ is routed to the CPU with lowest XTP register value, the
55 manner. IRQs will be routed only to the selected target CPUs. Check
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
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
Dti,omap4-wugen-mpu15 - interrupt-parent : a phandle to the GIC these interrupts are routed
Dnvidia,tegra-ictlr.txt22 - interrupt-parent : a phandle to the GIC these interrupts are routed
Dbrcm,bcm7038-l1-intc.txt14 peripheral IRQs to be routed to any CPU
/linux-4.4.14/arch/powerpc/boot/dts/
Dmpc5121ads.dts78 * all irqs but touch screen are routed to irq0 (ipic 48)
79 * touch screen is statically routed to irq1 (ipic 17)
Drainier.dts340 /* All PCI interrupts are routed to IRQ 67 */
Dsequoia.dts402 /* All PCI interrupts are routed to IRQ 67 */
Dicon.dts313 /* PCI-X interrupt (SM502) is routed to extIRQ10 (UIC1, 19) */
Dcanyonlands.dts450 /* All PCI interrupts are routed to ext IRQ 2 -> UIC1-0 */
Dglacier.dts487 /* All PCI interrupts are routed to ext IRQ 2 -> UIC1-0 */
/linux-4.4.14/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,bcm2835.txt17 early model B with I2C0 rather than I2C1 routed to the expansion header
/linux-4.4.14/Documentation/devicetree/bindings/mailbox/
Domap-mailbox.txt11 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
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Dsamsung-hsotg.txt18 interrupt signal of the HSOTG block is routed,
Dmsm-hsusb.txt76 - qcom,manual-pullup: If present, vbus is not routed to USB controller/phy
/linux-4.4.14/drivers/staging/lustre/lnet/lnet/
Dlib-ptl.c268 bool routed; in lnet_mt_of_match() local
281 routed = LNET_NIDNET(msg->msg_hdr.src_nid) != in lnet_mt_of_match()
285 (portal_rotor != LNET_PTL_ROTOR_ON && !routed)) { in lnet_mt_of_match()
292 if (portal_rotor == LNET_PTL_ROTOR_HASH_RT && routed) in lnet_mt_of_match()
/linux-4.4.14/Documentation/devicetree/bindings/display/msm/
Dedp.txt29 - interrupt-parent: phandle to the MDP block if the interrupt signal is routed
Ddsi.txt39 - interrupt-parent: phandle to the MDP block if the interrupt signal is routed
/linux-4.4.14/Documentation/networking/
Dipvs-sysctl.txt203 realservers so that they are routed as if they originate from the
204 director. Otherwise they are routed as if they are forwarded by the
208 of a packet originating from a director is routed differently to a
Dpolicy-routing.txt143 If it is set, locally originated packets are routed
Dgeneric-hdlc.txt7 - Normal (routed) and Ethernet-bridged (Ethernet device emulation)
Dip-sysctl.txt1522 routed via this interface are restricted to the set of addresses
/linux-4.4.14/Documentation/sound/alsa/
DHD-Audio-Controls.txt66 When this enum control is enabled, the headphone output is routed
114 When this enum control is enabled, the headphone output is routed
DCMIPCI.txt30 disabled. Otherwise no signal will be routed to the rear speakers.
48 playback should be routed there as default. If not, there is a
162 "IEC958 In Monitor" - SPDIF input is routed to DAC.
Dhdspm.txt353 channel (routed). This is against the ALSA-convention, where all
362 note: here the analog output is enabled (but not routed).
Dcompress_offload.txt64 decoded samples are routed to a physical output or logical back-end.
/linux-4.4.14/Documentation/devicetree/bindings/soc/mediatek/
Dpwrap.txt14 The signals of these pins are routed over the SPI bus using the pwrap
/linux-4.4.14/arch/arm/boot/dts/
Dkirkwood-blackarmor-nas220.dts96 * Serial port routed to connector CN5
Dste-nomadik-nhk15.dts68 /* This is where the interrupt is routed on the NHK-15 debug board */
Dlogicpd-torpedo-som.dtsi104 * MMC3 can be routed with jumpers to the second MMC slot on the devkit and
Dsun5i-r8-chip.dts86 * The interrupt is routed through the "External Fast
Dste-nomadik-stn8815.dtsi805 * routed and used for its 4-bit levelshifter.
/linux-4.4.14/Documentation/devicetree/bindings/arm/omap/
Dcrossbar.txt15 - ti,max-crossbar-sources: Maximum number of crossbar sources that can be routed.
/linux-4.4.14/drivers/irqchip/
DKconfig160 routed to one of the free irqchip interrupt lines.
/linux-4.4.14/drivers/i2c/muxes/
DKconfig58 This is useful for SoCs whose I2C module's signals can be routed to
/linux-4.4.14/Documentation/arm/pxa/
Dmfp.txt43 can be routed from GPIO19 of the GPIO controller.
50 which can be routed to external through one or more MFPs (e.g. GPIO<0>
51 can be routed through either MFP_PIN_GPIO0 as well as MFP_PIN_GPIO0_2,
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio.txt207 Some or all of the GPIOs provided by a GPIO controller may be routed to pins
258 Here, a single GPIO controller has GPIOs 0..9 routed to pin controller
259 pinctrl1's pins 20..29, and GPIOs 10..19 routed to pin controller pinctrl2's
/linux-4.4.14/Documentation/sound/alsa/soc/
DDPCM.txt13 way as the analog signal is routed in an ASoC codec driver. DPCM uses a DAPM
302 A hostless PCM stream is a stream that is not routed through the host CPU. An
320 In this case the PCM data is routed via the DSP. The host CPU in this use case
/linux-4.4.14/Documentation/leds/
Dleds-class-flash.txt69 flash API device would. The calls are simply routed to the LED flash API.
/linux-4.4.14/arch/x86/crypto/
Dcrc32c-pcl-intel-asm_64.S63 # Define threshold where buffers are considered "small" and routed to more
/linux-4.4.14/Documentation/pti/
Dpti_intel_mid.txt15 be collected and routed to the pti driver, such as trace
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Dti-edma.txt121 - interrupt-parent: Interrupt controller the interrupt is routed through
/linux-4.4.14/drivers/gpu/drm/msm/
DNOTES61 etc) are routed through MDP.
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dmax8998.txt24 the interrupts from MAX8998 are routed to.
/linux-4.4.14/Documentation/hwmon/
Dw83627hf58 it is possible or even likely for a w83627thf to have the VID signals routed
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-st.txt3 Each multi-function pin is controlled, driven and routed through the
Dqcom,pmic-mpp.txt142 Definition: Selects which dtest rail to be routed in the various functions.
/linux-4.4.14/arch/blackfin/mach-bf548/
DKconfig41 BF548 ATAPI data and address PINs can be routed through
/linux-4.4.14/Documentation/x86/
Dearlyprintk.txt24 Interrupt: pin D routed to IRQ 19
/linux-4.4.14/sound/drivers/
DKconfig84 the standard ALSA PCM device. The devices are routed 0->1 and
/linux-4.4.14/Documentation/power/
Dsuspend-and-interrupts.txt64 (such as an SoC) so that signals from a given line are routed in a different way
Dpci.txt242 are routed separately and they need not pass through bridges (in principle they
243 may be routed directly to the system's core logic), but for PCI Express devices
/linux-4.4.14/Documentation/isdn/
DREADME.x25167 "01" to be routed to your created isdn network interface.
/linux-4.4.14/net/ipv6/netfilter/
DKconfig272 which can effect how the packet is routed.
/linux-4.4.14/Documentation/scsi/
Dadvansys.txt109 b. Kernel messages are routed to console output. Check
/linux-4.4.14/net/ipv4/netfilter/
DKconfig323 which can effect how the packet is routed.
/linux-4.4.14/Documentation/arm/OMAP/
DDSS106 These framebuffers can be routed flexibly to any overlays, thus allowing very
/linux-4.4.14/Documentation/nfc/
Dnfc-hci.txt18 routed through netlink sockets to NFC Core and then to HCI. From this point,
/linux-4.4.14/drivers/net/
DKconfig403 domain network stack. These can then be bridged or routed
/linux-4.4.14/Documentation/cdrom/
Dcdrom-standard.tex538 are routed through the call $dev_ioctl()$. In principle, `private'
813 operations, ones that are routed through the call $audio_ioctl()$, and
833 \subsubsection{$Ioctl$s routed through $audio_ioctl()$}
/linux-4.4.14/drivers/misc/
DKconfig133 trace data routed from various parts in the system out
/linux-4.4.14/Documentation/PCI/
Dpci-error-recovery.txt402 interrupts are routed to error-management capable slots and can deal
/linux-4.4.14/Documentation/
Dpinctrl.txt441 of the package the silicon performing the SPI logic can alternatively be routed
452 contain several I2C, SPI, SDIO/MMC, etc silicon blocks that can be routed to
/linux-4.4.14/Documentation/virtual/kvm/
Dtimekeeping.txt192 The RTC generates an interrupt which is usually routed to IRQ 8. The interrupt
/linux-4.4.14/Documentation/filesystems/
Dproc.txt740 The way IRQs are routed is handled by the IO-APIC, and it's Round Robin
1131 your system and how much traffic was routed over those devices:
/linux-4.4.14/Documentation/gpio/
Dgpio-legacy.txt288 Some platforms allow some or all GPIO signals to be routed to different pins.