Home
last modified time | relevance | path

Searched full:aliases (Results 1 – 25 of 59) sorted by relevance

123

/Documentation/devicetree/bindings/media/
Dexynos5-gsc.txt26 Aliases:
27 Each G-Scaler node should have a numbered alias in the aliases node,
28 in the form of gscN, N = 0...3. G-Scaler driver uses these aliases
33 aliases {
Dst,stih4xx.txt24 Aliases:
25 Each BDISP should have a numbered alias in the aliases node, in the form of
30 aliases {
/Documentation/devicetree/bindings/spi/
Dnuvoton,npcm-pspi.txt22 Aliases:
23 - All the SPI controller nodes should be represented in the aliases node using
24 the following format 'spi{n}' withe the correct numbered in "aliases" node.
28 aliases {
Dnuvoton,npcm-fiu.txt25 Aliases:
26 - All the FIU controller nodes should be represented in the aliases node using
/Documentation/networking/
Dalias.rst7 IP-aliases are an obsolete way to manage multiple IP-addresses/masks
9 address/prefixes per interface, but aliases are still supported
42 Aliases are not real devices, but programs should be able to configure
49 If the base device is shut down the added aliases will be deleted too.
/Documentation/devicetree/bindings/powerpc/fsl/
Dmpic-msgr.txt32 Aliases:
36 may require aliases to be present. Aliases are of the form
42 aliases {
/Documentation/devicetree/bindings/net/
Dmdio-gpio.txt11 Note: Each gpio-mdio bus should have an alias correctly numbered in "aliases"
16 aliases {
/Documentation/devicetree/bindings/display/
Dsimple-framebuffer.yaml30 It is advised to add display# aliases to help the OS determine how
31 to number things. If display# aliases are used, then if the simplefb
32 node contains a display property then the /aliases/display# path
39 aliases. If display aliases are used then it should be set to the
155 aliases {
/Documentation/devicetree/bindings/serial/
Dqca,ar9330-uart.txt16 Each UART port must have an alias correctly numbered in "aliases"
21 aliases {
Darc-uart.txt20 Note: Each port should have an alias correctly numbered in "aliases" node.
23 aliases {
Dvt8500-uart.txt15 Aliases may be defined to ensure the correct ordering of the uarts.
18 aliases {
Ddigicolor-usart.txt15 in "aliases" node.
18 aliases {
Dcirrus,clps711x-uart.txt15 in "aliases" node.
18 aliases {
Dfsl-imx-uart.txt22 in "aliases" node.
26 aliases {
Dqcom,msm-uartdm.txt36 Note: Aliases may be defined to ensure the correct ordering of the UARTs.
39 serialN aliases should be in a .dts file instead of in a .dtsi file.
68 aliases {
Dfsl-mxs-auart.txt42 Note: Each auart port should have an alias correctly numbered in "aliases"
47 aliases {
Dsamsung_uart.txt36 "aliases" node, according to serialN format, where N is the port number
41 aliases {
/Documentation/devicetree/bindings/timer/
Dcirrus,clps711x-timer.txt9 Note: Each timer should have an alias correctly numbered in "aliases" node.
12 aliases {
/Documentation/devicetree/bindings/gpio/
Dgpio-clps711x.txt14 Note: Each GPIO port should have an alias correctly numbered in "aliases"
19 aliases {
Dgpio-vf610.txt33 Note: Each GPIO port should have an alias correctly numbered in "aliases"
38 aliases {
Dnvidia,tegra186-gpio.txt25 controllers, these registers are exposed via multiple "physical aliases" in
28 just one of these physical aliases.
79 b) All physical aliases that exist in the controller. This is
81 the physical aliases.
Dgpio-mxs.txt27 Note: Each GPIO port should have an alias correctly numbered in "aliases"
32 aliases {
/Documentation/devicetree/bindings/sound/
Dmxs-saif.txt17 in "aliases" node.
21 aliases {
/Documentation/devicetree/bindings/display/ti/
Dti,omap-dss.txt35 Aliases
38 The board dts file may define aliases for displays to assign "displayX" style
39 name for each display. If no aliases are defined, a semi-random number is used
94 aliases {
/Documentation/devicetree/bindings/display/exynos/
Dexynos_hdmi.txt33 - clock-names: aliases as per driver requirements for above clock IDs:
51 - clock-names: aliases for above clock specfiers.

123