| /linux-4.4.14/Documentation/devicetree/bindings/clock/st/ |
| D | st,clkgen-prediv.txt | 3 This binding uses the common clock binding[1].
4 Base address is located to the parent node. See clock binding[2]
15 - #clock-cells : From common clock binding; shall be set to 0.
17 - clocks : From common clock binding
19 - clock-output-names : From common clock binding.
|
| D | st,clkgen-divmux.txt | 3 This binding uses the common clock binding[1].
4 Base address is located to the parent node. See clock binding[2]
19 - #clock-cells : From common clock binding; shall be set to 1.
21 - clocks : From common clock binding
23 - clock-output-names : From common clock binding.
|
| D | st,clkgen-mux.txt | 3 This binding supports only simple indexed multiplexers, it does not
6 This binding uses the common clock binding[1].
22 - #clock-cells : from common clock binding; shall be set to 0.
26 - clocks : from common clock binding
|
| D | st,clkgen-pll.txt | 3 This binding uses the common clock binding[1].
4 Base address is located to the parent node. See clock binding[2]
31 - #clock-cells : From common clock binding; shall be set to 1.
33 - clocks : From common clock binding
35 - clock-output-names : From common clock binding.
|
| D | st,quadfs.txt | 8 This binding uses the common clock binding[1].
22 - #clock-cells : from common clock binding; shall be set to 1.
26 - clocks : from common clock binding
28 - clock-output-names : From common clock binding. The block has 4
|
| D | st,clkgen-vcc.txt | 9 This binding uses the common clock binding[1].
19 - #clock-cells : from common clock binding; shall be set to 1.
23 - clocks : from common clock binding
25 - clock-output-names : From common clock binding. The block has 16
|
| D | st,clkgen.txt | 42 This binding uses the common clock binding[1].
43 Each subnode should use the binding discribe in [2]..[7]
|
| D | st,flexgen.txt | 55 This binding uses the common clock binding[2].
64 - #clock-cells : from common clock binding; shall be set to 1 (multiple clock
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ |
| D | pwm-clock.txt | 3 This binding uses the common clock binding[1] and the common PWM binding[2].
10 - #clock-cells : from common clock binding; shall be set to 0.
11 - pwms : from common PWM binding; this determines the clock frequency
15 - clock-output-names : From common clock binding.
|
| D | fixed-factor-clock.txt | 3 This binding uses the common clock binding[1].
9 - #clock-cells : from common clock binding; shall be set to 0.
15 - clock-output-names : From common clock binding.
|
| D | fixed-clock.txt | 3 This binding uses the common clock binding[1].
9 - #clock-cells : from common clock binding; shall be set to 0.
15 - clock-output-names : From common clock binding.
|
| D | axi-clkgen.txt | 3 This binding uses the common clock binding[1].
9 - #clock-cells : from common clock binding; Should always be set to 0.
14 - clock-output-names : From common clock binding.
|
| D | keystone-pll.txt | 9 This binding uses the common clock binding[1].
14 - #clock-cells : from common clock binding; shall be set to 0.
43 - #clock-cells : from common clock binding; shall be set to 0.
51 - clock-output-names : From common clock binding.
65 - #clock-cells : from common clock binding; shall be set to 0.
73 - clock-output-names : From common clock binding.
|
| D | keystone-gate.txt | 5 This binding uses the common clock binding[1].
11 - #clock-cells : from common clock binding; shall be set to 0.
18 - clock-output-names : From common clock binding to override the
|
| D | gpio-mux-clock.txt | 3 This binding uses the common clock binding[1].
10 - #clock-cells : from common clock binding; shall be set to 0.
|
| D | gpio-gate-clock.txt | 3 This binding uses the common clock binding[1].
9 - #clock-cells : from common clock binding; shall be set to 0.
|
| D | calxeda.txt | 3 This binding uses the common clock binding[1].
17 - #clock-cells : from common clock binding; shall be set to 0.
|
| D | at91-clock.txt | 3 This binding uses the common clock binding[1].
101 - #clock-cells : from common clock binding; shall be set to 0.
115 - #clock-cells : from common clock binding; shall be set to 0.
130 - #clock-cells : from common clock binding; shall be set to 0.
191 - #clock-cells : from common clock binding; shall be set to 0.
212 - #clock-cells : from common clock binding; shall be set to 0.
227 - #clock-cells : from common clock binding; shall be set to 0.
255 * #clock-cells : from common clock binding; shall be set to 0.
286 - #clock-cells : from common clock binding; shall be set to 0.
327 - #clock-cells : from common clock binding; shall be set to 0.
[all …]
|
| D | vt8500.txt | 3 This binding uses the common clock binding[1].
19 - #clock-cells : from common clock binding; shall be set to 0.
24 - #clock-cells : from common clock binding; shall be set to 0.
|
| D | altr_socfpga.txt | 3 This binding uses the common clock binding[1].
18 - #clock-cells : from common clock binding, shall be set to 0.
|
| D | silabs,si514.txt | 4 This binding uses the common clock binding[1]. Details about the device can be
|
| D | rockchip.txt | 3 This binding uses the common clock binding[1].
21 - #clock-cells : from common clock binding; shall be set to 1
|
| D | alphascale,acc.txt | 13 It is encouraged to use dt-binding for clock index definitions. SoC specific
14 dt-binding should be included to the device tree descriptor. For example
18 This binding contains two types of clock providers:
|
| D | zx296702-clk.txt | 3 This binding uses the common clock binding[1].
|
| D | ti,cdce706.txt | 9 - #clock-cells: from common clock binding; shall be set to 1.
10 - clocks: from common clock binding; list of parent clock
|
| D | marvell,berlin.txt | 3 This binding uses the common clock binding[1].
|
| D | moxa,moxart-clock.txt | 3 This binding uses the common clock binding[1].
|
| D | maxim,max77686.txt | 13 - #clock-cells: from common clock binding; shall be set to 1.
16 - clock-output-names: From common clock binding.
|
| D | maxim,max77802.txt | 12 - #clock-cells: From common clock binding; shall be set to 1.
15 - clock-output-names: From common clock binding.
|
| D | clk-palmas-clk32kg-clocks.txt | 5 This binding uses the common clock binding ./clock-bindings.txt.
|
| D | ti,cdce925.txt | 4 This binding uses the common clock binding[1].
|
| D | brcm,bcm2835-cprman.txt | 3 This binding uses the common clock binding:
|
| D | nvidia,tegra30-car.txt | 3 This binding uses the common clock binding:
|
| D | nvidia,tegra114-car.txt | 3 This binding uses the common clock binding:
|
| D | silabs,si570.txt | 5 This binding uses the common clock binding[1]. Details about the devices can be
|
| D | nvidia,tegra20-car.txt | 3 This binding uses the common clock binding:
|
| D | st,nomadik.txt | 3 This binding uses the common clock binding:
|
| D | lpc1850-ccu.txt | 9 This binding uses the common clock binding:
|
| D | brcm,kona-ccu.txt | 3 This binding is associated with Broadcom SoCs having "Kona" style
8 This binding uses the common clock binding:
|
| D | qoriq-clock.txt | 92 Most of the bindings are from the common clock binding[1].
107 - #clock-cells: From common clock binding. The number of cells in a
118 - clock-names: From common clock binding, indicates the clock name
119 - clock-output-names: From common clock binding, indicates the names of
|
| D | emev2-clock.txt | 3 This binding uses the common clock binding.
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ti/ |
| D | clockdomain.txt | 5 This binding uses the common clock binding[1] in consumer role.
9 enabled/disabled. This binding doesn't define a new clock
10 binding type, it is used to group existing clock nodes under
17 - #clock-cells : from common clock binding; shall be set to 0.
|
| D | dra7-atl.txt | 12 Clock tree binding:
13 This binding uses the common clock binding[1].
16 Since the clock instances are part of a single IP this binding is used as a node
24 - #clock-cells : from common clock binding; shall be set to 0.
28 This binding is used to configure the IP driver which is going to handle the
75 /* binding for the IP */
|
| D | composite.txt | 5 This binding uses the common clock binding[1]. It assumes a
16 The binding must provide a list of the component clocks that shall be
28 - #clock-cells : from common clock binding; shall be set to 0.
|
| D | fapll.txt | 5 This binding uses the common clock binding[1]. It assumes a
14 - #clock-cells : from common clock binding; shall be set to 0.
|
| D | divider.txt | 5 This binding uses the common clock binding[1]. It assumes a
44 The binding must also provide the register to control the divider and
49 This binding can also optionally provide support to the hardware autoidle
57 - #clock-cells : from common clock binding; shall be set to 0.
62 - clock-output-names : from common clock binding.
|
| D | fixed-factor-clock.txt | 5 This binding uses the common clock binding[1], and also uses the autoidle
13 - #clock-cells : from common clock binding; shall be set to 0.
|
| D | mux.txt | 5 This binding uses the common clock binding[1]. It assumes a
31 The binding must provide the register to control the mux. Optionally
40 - #clock-cells : from common clock binding; shall be set to 0.
|
| D | apll.txt | 5 This binding uses the common clock binding[1]. It assumes a
18 - #clock-cells : from common clock binding; shall be set to 0.
|
| D | interface.txt | 5 This binding uses the common clock binding[1]. This clock is
26 - #clock-cells : from common clock binding; shall be set to 0
|
| D | dpll.txt | 5 This binding uses the common clock binding[1]. It assumes a
10 modes (locked, low power stop etc.) This binding has several
36 - #clock-cells : from common clock binding; shall be set to 0.
|
| D | autoidle.txt | 5 This binding uses the common clock binding[1]. It assumes a register mapped
|
| D | gate.txt | 5 This binding uses the common clock binding[1]. This clock is
33 - #clock-cells : from common clock binding; shall be set to 0
|
| /linux-4.4.14/Documentation/devicetree/bindings/ |
| D | ABI.txt | 7 "That still leaves the question of, what does a stable binding look
8 like? Certainly a stable binding means that a newer kernel will not
9 break on an older device tree, but that doesn't mean the binding is
12 then default to the previous behaviour if it is missing. If a binding
18 II. General binding rules
21 binding because it isn't perfect.
27 the old binding. ie. add additional properties, but don't change the
|
| D | submitting-patches.txt | 2 Submitting devicetree (DT) binding patches
19 the code implementing the binding.
22 previously documented in the corresponding DT binding text file
46 1) If you aren't comfortable reviewing a given binding, reply to it and ask
51 binding, and it hasn't received an Acked-by from the devicetree
57 3) For a series going though multiple trees, the binding patch should be
58 kept with the driver using the binding.
|
| D | chosen.txt | 28 must be specified in the relevant binding documentation.
30 For UART devices, the preferred binding is a string in the form:
|
| D | common-properties.txt | 21 If a binding supports these properties, then the binding should also
|
| /linux-4.4.14/Documentation/devicetree/bindings/sound/ |
| D | ak4642.txt | 12 - #clock-cells : common clock binding; shall be set to 0
13 - clocks : common clock binding; MCKI clock
14 - clock-frequency : common clock binding; frequency of MCKO
15 - clock-output-names : common clock binding; MCKO clock name
|
| D | nvidia,tegra-audio-rt5640.txt | 15 sinks are the RT5640's pins (as documented in its binding), and the jacks
24 - nvidia,audio-codec : The phandle of the RT5640 audio codec. This binding
|
| D | nvidia,tegra-audio-rt5677.txt | 15 sinks are the RT5677's pins (as documented in its binding), and the jacks
26 - nvidia,audio-codec : The phandle of the RT5677 audio codec. This binding
|
| /linux-4.4.14/drivers/char/ |
| D | raw.c | 30 struct block_device *binding; member
70 bdev = raw_devices[minor].binding; in raw_open()
107 bdev = raw_devices[minor].binding; in raw_release()
163 if (rawdev->binding) { in bind_set()
164 bdput(rawdev->binding); in bind_set()
169 rawdev->binding = NULL; in bind_set()
172 rawdev->binding = bdget(dev); in bind_set()
173 if (rawdev->binding == NULL) { in bind_set()
198 bdev = rawdev->binding; in bind_get()
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/ |
| D | elan_i2c.txt | 7 binding[0]).
9 binding[0]).
13 - pinctrl-names: should be "default" (see pinctrl binding [1]).
15 pinctrl binding [1]).
|
| D | elants_i2c.txt | 7 binding[0]).
9 binding[0]).
13 - pinctrl-names: should be "default" (see pinctrl binding [1]).
15 pinctrl binding [1]).
|
| D | cypress,cyapa.txt | 7 binding[0]).
9 binding[0]).
13 - pinctrl-names: should be "default" (see pinctrl binding [1]).
15 pinctrl binding [1]).
|
| D | tca8418_keypad.txt | 1 This binding is based on the matrix-keymap binding with the following
|
| D | lpc32xx-key.txt | 3 This binding is based on the matrix-keymap binding with the following
|
| D | omap-keypad.txt | 9 This binding is based on the matrix-keymap binding with the following
|
| D | twl4030-keypad.txt | 9 This binding is based on the matrix-keymap binding with the following
|
| D | matrix-keymap.txt | 1 A simple common binding for matrix-connected key boards. Currently targeted at
18 Some users of this binding might choose to specify secondary keymaps for
|
| D | brcm,bcm-keypad.txt | 9 This binding is based on the matrix-keymap binding with the following
61 - linux,keymap: The keymap for keys as described in the binding document
|
| D | st-keyscan.txt | 3 The ST keyscan controller Device Tree binding is based on the
19 - linux,keymap: The keymap for keys as described in the binding document
|
| D | gpio-beeper.txt | 7 - gpios: From common gpio binding; gpio connection to beeper enable pin.
|
| /linux-4.4.14/drivers/gpu/drm/vmwgfx/ |
| D | vmwgfx_execbuf.c | 865 struct vmw_ctx_bindinfo_view binding; in vmw_view_bindings_add() local
883 binding.bi.ctx = ctx_node->res; in vmw_view_bindings_add()
884 binding.bi.res = view; in vmw_view_bindings_add()
885 binding.bi.bt = binding_type; in vmw_view_bindings_add()
886 binding.shader_slot = shader_slot; in vmw_view_bindings_add()
887 binding.slot = first_slot + i; in vmw_view_bindings_add()
888 vmw_binding_add(ctx_node->staged_bindings, &binding.bi, in vmw_view_bindings_add()
889 shader_slot, binding.slot); in vmw_view_bindings_add()
954 struct vmw_ctx_bindinfo_view binding; in vmw_cmd_set_render_target_check() local
956 binding.bi.ctx = ctx_node->res; in vmw_cmd_set_render_target_check()
[all …]
|
| D | vmwgfx_binding.c | 494 struct vmw_ctx_bindinfo_shader *binding = in vmw_binding_scrub_shader() local
495 container_of(bi, typeof(*binding), bi); in vmw_binding_scrub_shader()
512 cmd->body.type = binding->shader_slot + SVGA3D_SHADERTYPE_MIN; in vmw_binding_scrub_shader()
529 struct vmw_ctx_bindinfo_view *binding = in vmw_binding_scrub_render_target() local
530 container_of(bi, typeof(*binding), bi); in vmw_binding_scrub_render_target()
547 cmd->body.type = binding->slot; in vmw_binding_scrub_render_target()
568 struct vmw_ctx_bindinfo_tex *binding = in vmw_binding_scrub_texture() local
569 container_of(bi, typeof(*binding), bi); in vmw_binding_scrub_texture()
589 cmd->body.s1.stage = binding->texture_stage; in vmw_binding_scrub_texture()
605 struct vmw_ctx_bindinfo_shader *binding = in vmw_binding_scrub_dx_shader() local
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/spi/ |
| D | spi-octeon.txt | 7 - #address-cells : <1>, as required by generic SPI binding.
8 - #size-cells : <0>, also as required by generic SPI binding.
10 Child nodes as per the generic SPI binding.
|
| D | spi-ath79.txt | 8 - #address-cells: <1>, as required by generic SPI binding.
9 - #size-cells: <0>, also as required by generic SPI binding.
11 Child nodes as per the generic SPI binding.
|
| D | snps,dw-apb-ssi.txt | 7 - #address-cells : <1>, as required by generic SPI binding.
8 - #size-cells : <0>, also as required by generic SPI binding.
16 Child nodes as per the generic SPI binding.
|
| D | omap-spi.txt | 15 as described in the generic DMA client binding. A tx and rx
34 [generic DMA request binding]
|
| D | fsl-imx-cspi.txt | 18 See the clock consumer binding,
20 - dmas: DMA specifiers for tx and rx dma. See the DMA client binding,
|
| D | spi-fsl-dspi.txt | 7 - clocks: from common clock binding: handle to dspi clock.
8 - clock-names: from common clock binding: Shall be "dspi".
|
| D | spi-bus.txt | 6 SPI master mode. This binding does not describe SPI controllers
18 However, the binding does not attempt to define the specific method for
20 flexible and non-standardized, it is left out of this binding with the
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ux500/ |
| D | boards.txt | 23 see binding for arm/scu.txt
26 see binding for arm/gic.txt
29 see binding for arm/twd.txt
32 see binding for clocks/ux500.txt
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | primecell.txt | 16 - clocks : From common clock binding. First clock is phandle to clock for apb
18 - clock-names : From common clock binding. Shall be "apb_pclk" for first clock.
19 - dmas : From common DMA binding. If present, refers to one or more dma channels.
20 - dma-names : From common DMA binding, needs to match the 'dmas' property.
|
| D | marvell,berlin.txt | 7 considered "unstable". Any Marvell Berlin device tree binding may change at any
12 stable binding/ABI.
55 * Marvell Berlin2 chip control binding
71 * Marvell Berlin2 system control binding
|
| D | sp810.txt | 27 - assigned-clocks: from the common clock binding;
31 - assigned-clock-parents: from the common clock binding;
|
| D | psci.txt | 12 firmware (specified as part of the binding below) and passing arguments
42 in this binding.
45 in this binding.
|
| /linux-4.4.14/net/netfilter/ |
| D | nft_lookup.c | 25 struct nft_set_binding binding; member
94 priv->binding.flags = set->flags & NFT_SET_MAP; in nft_lookup_init()
96 err = nf_tables_bind_set(ctx, set, &priv->binding); in nft_lookup_init()
109 nf_tables_unbind_set(ctx, priv->set, &priv->binding); in nft_lookup_destroy()
|
| D | nft_dynset.c | 27 struct nft_set_binding binding; member
194 err = nf_tables_bind_set(ctx, set, &priv->binding); in nft_dynset_init()
212 nf_tables_unbind_set(ctx, priv->set, &priv->binding); in nft_dynset_destroy()
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/panel/ |
| D | ortustech,com43h4m85ulc.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | lg,lb070wv8.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | innolux,at043tn24.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | panasonic,vvx10f004b00.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | lg,lp129qe.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | innolux,n156bge-l21.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | samsung,ltn101nt05.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | giantplus,gpg482739qs5.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | auo,b101xtn01.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | auo,b101aw03.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | lg,lh500wx1-sd03.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | foxlink,fl500wvr00-a0t.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | samsung,ltn140at29-301.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | innolux,n116bge.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | auo,b101ean01.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | lg,ld070wx3-sl01.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | auo,b080uan01.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | hannstar,hsd100pxn1.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | innolux,g121i1-l01.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | edt,et057090dhu.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | chunghwa,claa101wb03.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | innolux,zj070na-01p.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | auo,b133xtn01.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | hannstar,hsd070pww1.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | hit,tx23d38vm0caa.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | avic,tm070ddh03.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | ampire,am800480r3tmqwa1h.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | chunghwa,claa101wa01a.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | auo,b116xw03.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | auo,b133htn01.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | nec,nl4827hc19-05b.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | shelly,sca07010-bfn-lnn.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | okaya,rs800480t-7x0gp.txt | 6 This binding is compatible with the simple-panel binding, which is specified
|
| D | edt,et070080dh6.txt | 9 This binding is compatible with the simple-panel binding, which is specified
|
| D | edt,etm0700g0dh6.txt | 9 This binding is compatible with the simple-panel binding, which is specified
|
| /linux-4.4.14/Documentation/devicetree/bindings/leds/backlight/ |
| D | pwm-backlight.txt | 5 - pwms: OF device-tree PWM specification (see PWM binding[0])
17 "pwms" property (see PWM binding[0])
19 and disables the backlight (see GPIO binding[1])
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/ |
| D | tsc2007.txt | 11 (see GPIO binding[1] for more details).
13 (see interrupt binding[0]).
15 (see interrupt binding[0]).
|
| /linux-4.4.14/Documentation/devicetree/bindings/usb/ |
| D | exynos-usb.txt | 13 - clocks: from common clock binding: handle to usb clock.
14 - clock-names: from common clock binding: Shall be "usbhost".
54 - clocks: from common clock binding: handle to usb clock.
55 - clock-names: from common clock binding: Shall be "usbhost".
99 The binding details of dwc3 can be found in:
|
| D | dwc3-st.txt | 23 See: Documentation/devicetree/bindings/pinctrl/pinctrl-binding.txt
26 See: Documentation/devicetree/bindings/pinctrl/pinctrl-binding.txt
33 example below. The DT binding details of dwc3 can be found in:
|
| /linux-4.4.14/Documentation/devicetree/bindings/phy/ |
| D | pxa1928-usb-phy.txt | 6 - clocks - A single clock. From common clock binding.
7 - #phys-cells: should be 0. From commmon phy binding.
|
| D | phy-mt65xx-usb.txt | 1 mt65xx USB3.0 PHY binding
4 This binding describes a usb3.0 phy for mt65xx platforms of Medaitek SoC.
|
| D | phy-bindings.txt | 1 This document explains only the device tree data binding. For general
9 cells is defined by the binding for the phy node. The PHY
|
| D | brcm,kona-usb2-phy.txt | 7 Refer to phy/phy-bindings.txt for the generic PHY binding properties
|
| D | phy-miphy365x.txt | 1 STMicroelectronics STi MIPHY365x PHY binding
4 This binding describes a miphy device that is used to control PHY hardware
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | fixed-link.txt | 1 Fixed link Device Tree binding
6 binding allows to describe a "fixed link".
23 Old, deprecated 'fixed-link' binding:
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | sky81452.txt | 8 - backlight : container node for backlight following the binding
10 - regulator : container node for regulators following the binding
|
| /linux-4.4.14/Documentation/devicetree/bindings/reset/ |
| D | brcm,bcm63138-pmb.txt | 1 Broadcom BCM63138 Processor Monitor Bus binding
5 controller binding usage.
|
| D | reset.txt | 3 This binding is intended to represent the hardware reset signals present
11 ordinate module is reset). This binding exists to represent the provider and
17 are dictated by the binding of the reset provider, although common schemes
27 block node for dedicated reset signals. The intent of this binding is to give
|
| D | st,sti-picophyreset.txt | 4 This binding describes a reset controller device that is used to enable and
14 for common reset controller binding usage.
|
| D | st,sti-softreset.txt | 4 This binding describes a reset controller device that is used to enable and
15 controller binding usage.
|
| D | st,sti-powerdown.txt | 4 This binding describes a reset controller device that is used to enable and
16 controller binding usage.
|
| D | berlin,reset.txt | 5 controller binding usage.
|
| D | allwinner,sunxi-clock-reset.txt | 5 controller binding usage.
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/ |
| D | fsl,dcu.txt | 9 - clocks: From common clock binding: handle to dcu clock.
10 - clock-names: From common clock binding: Shall be "dcu".
|
| D | st,stih4xx.txt | 15 - clocks: from common clock binding: handle hardware IP needed clocks, the
33 - clocks: from common clock binding: handle hardware IP needed clocks, the
66 - clocks: from common clock binding: handle hardware IP needed clocks, the
79 - clocks: from common clock binding: handle hardware IP needed clocks, the
92 - clocks: from common clock binding: handle hardware IP needed clocks, the
106 - clocks: from common clock binding: handle hardware IP needed clocks, the
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/exynos/ |
| D | exynos_dp.txt | 25 from common clock binding: handle to dp clock.
27 from common clock binding: Shall be "dp".
31 from general PHY binding: the phandle for the PHY device.
33 from general PHY binding: Should be "dp".
|
| /linux-4.4.14/Documentation/devicetree/bindings/power/ |
| D | power_domain.txt | 7 This device tree binding can be used to bind PM domain consumer devices with
20 as specified by device tree binding documentation of particular provider.
27 a standard PM domain consumer binding is used. When provided, all domains
29 specified by this binding. More details about power domain specifier are
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/mediatek/ |
| D | mediatek,pericfg.txt | 15 The pericfg controller uses the common clk binding from
18 Also it uses the common reset controller binding from
|
| D | mediatek,infracfg.txt | 15 The infracfg controller uses the common clk binding from
18 Also it uses the common reset controller binding from
|
| D | mediatek,vencltsys.txt | 12 The vencltsys controller uses the common clk binding from
|
| D | mediatek,apmixedsys.txt | 13 The apmixedsys controller uses the common clk binding from
|
| D | mediatek,topckgen.txt | 13 The topckgen controller uses the common clk binding from
|
| D | mediatek,imgsys.txt | 12 The imgsys controller uses the common clk binding from
|
| D | mediatek,vdecsys.txt | 12 The vdecsys controller uses the common clk binding from
|
| /linux-4.4.14/Documentation/devicetree/bindings/serial/ |
| D | digicolor-usart.txt | 3 Note: this binding is only applicable for using the USART peripheral as
5 the binding that matches the wiring of your system.
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | open-pic.txt | 3 This binding specifies what properties must be available in the device tree
4 representation of an Open PIC compliant interrupt controller. This binding is
5 based on the binding defined for Open PIC in [1] and is a superset of that
6 binding.
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 18 own binding.
41 Each client device's own binding determines the set of states that must be
61 the binding for that IP block requires certain pin states to
90 * For an IP block whose binding supports pin configuration,
121 entirely by the binding for the individual pin controller device. There
127 nodes, is again defined entirely by the binding for the individual pin
164 for all hardware or binding structures. Each individual binding document
224 binding for the hardware defines:
|
| D | nvidia,tegra124-pinmux.txt | 3 The Tegra124 pinctrl binding is very similar to the Tegra20 and Tegra30
4 pinctrl binding, as described in nvidia,tegra20-pinmux.txt and
5 nvidia,tegra30-pinmux.txt. In fact, this document assumes that binding as
18 include/dt-binding/pinctrl/pinctrl-tegra.h.
|
| D | fsl,mxs-pinctrl.txt | 21 actually tristates in this binding: unspecified, off, or on. Unspecified is
27 configurations, and it's called group node in the binding document. The other
29 different configuration than what is defined in group node. The binding
32 On mxs, there is no hardware pin group. The pin group in this binding only
|
| D | fsl,imx-pinctrl.txt | 22 Please refer to each fsl,<soc>-pinctrl.txt binding doc for supported SoCs.
41 Please refer to each fsl,<soc>-pinctrl,txt binding doc for SoC specific part
45 Some requirements for using fsl,imx-pinctrl binding:
|
| D | nvidia,tegra124-xusb-padctl.txt | 1 Device tree binding for NVIDIA Tegra XUSB pad controller
8 This document defines the device-specific binding for the XUSB pad controller.
43 values are actually tristates in this binding: unspecified, off or on.
|
| D | fsl,imx25-pinctrl.txt | 3 Please refer to fsl,imx-pinctrl.txt in this directory for common binding part
|
| D | nvidia,tegra114-pinmux.txt | 3 The Tegra114 pinctrl binding is very similar to the Tegra20 and Tegra30
4 pinctrl binding, as described in nvidia,tegra20-pinmux.txt and
5 nvidia,tegra30-pinmux.txt. In fact, this document assumes that binding as
|
| D | nvidia,tegra30-pinmux.txt | 3 The Tegra30 pinctrl binding is very similar to the Tegra20 pinctrl binding,
5 that binding as a baseline, and only documents the differences between the
|
| /linux-4.4.14/Documentation/i2c/ |
| D | old-module-parameters | 1 I2C device driver binding control from user-space
12 binding model, it became clear that these per-module parameters were no
42 other drivers from binding to it later on. If there is a real device at the
|
| /linux-4.4.14/drivers/gpu/drm/tilcdc/ |
| D | Kconfig | 17 bool "Support device tree blobs using TI LCDC Slave binding"
25 binding. If you find "ti,tilcdc,slave"-string from your DTB,
|
| D | tilcdc_slave_compat.dts | 2 * DTS overlay for converting ti,tilcdc,slave binding to new binding.
|
| /linux-4.4.14/Documentation/devicetree/bindings/power_supply/ |
| D | lp8727_charger.txt | 8 - interrupt-parent: interrupt controller node (see interrupt binding[0])
9 - interrupts: interrupt specifier (see interrupt binding[0])
|
| /linux-4.4.14/drivers/staging/clocking-wizard/ |
| D | dt-binding.txt | 3 This binding uses the common clock binding[1]. Details about the devices can be
|
| /linux-4.4.14/Documentation/devicetree/bindings/dma/ |
| D | dma.txt | 3 Generic binding to provide a way for a driver using DMA Engine to retrieve the
12 specific information. See DMA client binding below for
44 information. See DMA client binding below for more
79 are defined in the binding of the DMA client device.
|
| /linux-4.4.14/Documentation/devicetree/bindings/regulator/ |
| D | tps65023.txt | 13 these nodes is defined using the standard binding for regulators found at
16 Each regulator is defined using the standard binding for regulators.
|
| D | tps65217.txt | 11 using the standard binding for regulators found at
20 Each regulator is defined using the standard binding for regulators.
|
| D | regulator.txt | 39 device tree binding document.
41 modes depends on the capabilities of every hardware so each device binding
50 regulators, and if the chip's binding contains a child node that
|
| /linux-4.4.14/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smem.txt | 1 Qualcomm Shared Memory Manager binding
3 This binding describes the Qualcomm Shared Memory Manager, used to share data
|
| D | qcom,smd.txt | 1 Qualcomm Shared Memory Driver (SMD) binding
3 This binding describes the Qualcomm Shared Memory Driver, a fifo based
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-bus-platform | 13 matching rules binding. Writing to driver_override does not
18 devices to opt-out of driver binding using a driver_override
|
| D | sysfs-bus-amba | 12 This returns the device to standard matching rules binding.
18 driver binding using a driver_override name such as "none".
|
| /linux-4.4.14/Documentation/devicetree/bindings/mmc/ |
| D | synopsys-dw-mshc.txt | 42 * clocks: from common clock binding: handle to biu and ciu clocks for the
45 * clock-names: from common clock binding: Shall be "biu" and "ciu".
79 in the generic DMA client binding. Refer to dma.txt for details.
81 * dma-names: request names for generic DMA client binding. Must be "rx-tx".
119 [board specific generic DMA request binding]
|
| /linux-4.4.14/Documentation/devicetree/bindings/leds/ |
| D | common.txt | 10 have to be tightly coupled with the LED device binding. They are represented
11 by child nodes of the parent LED device binding.
16 in the LED device binding documentation.
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | gpio.txt | 30 binding of the device.
59 be documented in the device tree binding for the device.
93 defined by the binding for the device. If the board inverts the signal between
97 When the device's signal polarity is configurable, the binding for the
101 any software using that binding would statically program the device to use
106 a1) (Preferred) Dictated by a binding-specific DT property.
110 a2) Defined statically by the DT binding itself.
120 in the binding. The gpio-specifier should represent the polarity of the signal
241 Previous versions of this binding required all pin controller nodes that
|
| /linux-4.4.14/Documentation/devicetree/bindings/pci/ |
| D | rcar-pci.txt | 19 - clocks: from common clock binding: clock specifiers for the PCIe controller
21 - clock-names: from common clock binding: should be "pcie" and "pcie_bus".
|
| /linux-4.4.14/tools/perf/ui/browsers/ |
| D | map.c | 30 sym->binding == STB_GLOBAL ? 'g' : in map_browser__write()
31 sym->binding == STB_LOCAL ? 'l' : 'w'); in map_browser__write()
|
| /linux-4.4.14/Documentation/devicetree/bindings/iommu/ |
| D | iommu.txt | 1 This document describes the generic device tree binding for IOMMUs and their
26 Device nodes compatible with this binding represent hardware with some of the
43 The meaning of the IOMMU specifier is defined by the device tree binding of
64 IOMMU binding for the exact meaning of the cells that make up the specifier.
99 this binding.
|
| /linux-4.4.14/Documentation/devicetree/bindings/media/ |
| D | s5p-mfc.txt | 20 - clocks : from common clock binding: handle to mfc clock.
21 - clock-names : from common clock binding: must contain "mfc",
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c-versatile.txt | 10 - Child nodes conforming to i2c bus binding
|
| D | i2c.txt | 16 clocks, etc. check the binding documentation of the specific driver.
45 binding, then primary interrupt will be used as wakeup interrupt.
|
| D | i2c-st-ddci2c.txt | 12 - Child nodes conforming to i2c bus binding
|
| D | i2c-xiic.txt | 11 - Child nodes conforming to i2c bus binding
|
| D | i2c-cbus-gpio.txt | 10 - child nodes conforming to i2c bus binding
|
| /linux-4.4.14/Documentation/devicetree/bindings/soc/mediatek/ |
| D | pwrap.txt | 3 This document describes the binding for the MediaTek PMIC wrapper.
15 bridge. In the binding description below the properties needed for bridging
|
| /linux-4.4.14/Documentation/devicetree/bindings/spmi/ |
| D | qcom,spmi-pmic-arb.txt | 10 See spmi.txt for the generic SPMI controller binding requirements for child
14 generic interrupt controller binding documentation.
|
| /linux-4.4.14/Documentation/devicetree/bindings/rtc/ |
| D | digicolor-rtc.txt | 3 This binding currently supports the CX92755 SoC.
|
| D | imxdi-rtc.txt | 3 This binding supports the following chips: i.MX25, i.MX53
|
| D | haoyu,hym8563.txt | 12 - clock-output-names: From common clock binding
|
| /linux-4.4.14/Documentation/devicetree/bindings/misc/ |
| D | brcm,kona-smc.txt | 3 This binding defines the location of the bounce buffer
|
| D | arm-charlcd.txt | 3 This binding defines the character LCD interface found on ARM Versatile AB
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/freescale/ |
| D | fsl,vf610-mscm-cpucfg.txt | 3 The MSCM IP contains multiple sub modules, this binding describes the first
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpic-msgr.txt | 3 This binding specifies what properties must be available in the device tree
35 required, though. However, a particular implementation of this binding
|
| /linux-4.4.14/Documentation/devicetree/bindings/pwm/ |
| D | atmel-tcb-pwm.txt | 6 the cells format. The only third cell flag supported by this binding is
|
| /linux-4.4.14/Documentation/console/ |
| D | console.txt | 79 Device Drivers -> Character devices -> Support for binding and unbinding
82 NOTE2: If any of the virtual consoles are in KD_GRAPHICS mode, then binding or
109 In order for binding to and unbinding from the console to properly work,
138 The current crop of console drivers should still work correctly, but binding
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | binding.txt | 4 Driver binding is the process of associating a device with a device
8 structures, most of the binding can take place using common code.
19 two events which trigger driver binding.
|
| /linux-4.4.14/Documentation/devicetree/bindings/extcon/ |
| D | extcon-usb-gpio.txt | 8 - id-gpio: gpio for USB ID pin. See gpio binding.
|