Home
last modified time | relevance | path

Searched full:main (Results 1 – 25 of 538) sorted by relevance

12345678910>>...22

/Documentation/devicetree/bindings/interrupt-controller/
Dsamsung,s3c24xx-irq.txt4 varying number of interrupt sources. The set consists of a main- and sub-
5 controller and on newer SoCs even a second main controller.
22 - 0 ... main controller
24 - 2 ... second main controller on s3c2416 and s3c2450
25 parent_irq contains the parent bit in the main controller and will be
26 ignored in main controllers
/Documentation/devicetree/bindings/sound/
Domap-abe-twl6040.txt27 * Main Handset Mic
49 * Main Mic Bias
83 "MAINMIC", "Main Handset Mic",
84 "Main Handset Mic", "Main Mic Bias",
86 "Sub Handset Mic", "Main Mic Bias",
Dsamsung,aries-wm8994.yaml50 For samsung,aries-wm8994: HP, SPK, RCV, LINE, Main Mic, Headset Mic,
52 For samsung,fascinate4g-wm8994: HP, SPK, RCV, LINE, Main Mic,
58 main-micbias-supply:
59 description: Supply for the micbias on the main mic
87 - main-micbias-supply
106 main-micbias-supply = <&main_micbias_reg>;
129 "IN1LP", "Main Mic",
130 "IN1LN", "Main Mic",
Dsamsung,tm2-audio.txt20 board: HP, SPK, Main Mic, Sub Mic, Third Mic,
22 - mic-bias-gpios : GPIO pin that enables the Main Mic bias regulator
40 "Main Mic", "MICBIAS2",
41 "IN1R", "Main Mic";
Dsamsung,midas-audio.yaml47 on the board: HP, SPK, Main Mic, Sub Mic, Headset Mic.
50 description: Supply for the micbias on the Main microphone
97 "IN1LP", "Main Mic",
98 "IN1LN", "Main Mic",
Domap-twl4030.txt24 * Main Mic
52 * Mic Bias 1 /* Used for Main Mic or Digimic0 */
/Documentation/devicetree/bindings/media/
Dmediatek-vpu.txt11 "cfg_reg": Main configuration registers base
14 - clock-names: must be main. It is the main clock of VPU
30 clock-names = "main";
/Documentation/driver-api/firmware/
Drequest_firmware.rst20 .. kernel-doc:: drivers/base/firmware_loader/main.c
25 .. kernel-doc:: drivers/base/firmware_loader/main.c
30 .. kernel-doc:: drivers/base/firmware_loader/main.c
35 .. kernel-doc:: drivers/base/firmware_loader/main.c
40 .. kernel-doc:: drivers/base/firmware_loader/main.c
54 .. kernel-doc:: drivers/base/firmware_loader/main.c
68 .. kernel-doc:: drivers/base/firmware_loader/main.c
/Documentation/devicetree/bindings/clock/
Dkeystone-pll.txt3 Binding for keystone PLLs. The main PLL IP typically has a multiplier,
5 and PAPLL are controlled by the memory mapped register where as the Main
15 - compatible : shall be "ti,keystone,main-pll-clock" or "ti,keystone,pll-clock"
19 post-divider registers are applicable only for main pll clock
26 compatible = "ti,keystone,main-pll-clock";
Dst,nomadik.txt18 i.e. the driver output for the main (~19.2 MHz) chrystal,
24 which should both have the main chrystal, represented as a
31 - clocks: this clock will have main chrystal as parent
Dartpec6.txt9 There are two external inputs to the main clock controller which should be
14 Main clock controller
/Documentation/devicetree/bindings/bus/
Dbaikal,bt1-axi.yaml14 AXI3-bus is the main communication bus of Baikal-T1 SoC connecting all
17 called AXI Main Interconnect) routing IO requests from one block to
57 - description: Main Interconnect uplink reference clock
65 - description: Main Interconnect reset line
/Documentation/watchdog/
Dmlx-wdt.rst38 Old systems still have only one main watchdog.
40 Mellanox system can have 2 watchdogs: main and auxiliary.
41 Main and auxiliary watchdog devices can be enabled together
58 Mellanox watchdog device, identity name (mlx-wdt-main or mlx-wdt-aux),
/Documentation/devicetree/bindings/display/
Dst,stih4xx.txt13 - compatible: "st,vtac-main" or "st,vtac-aux"
42 - st,vtg: phandle(s) on vtg device (main and aux) nodes.
115 - st,vtg: phandle on vtg main device node.
122 vtg_main_slave: sti-vtg-main-slave@fe85a800 {
128 vtg_main: sti-vtg-main-master@fd348000 {
147 sti-vtac-rx-main@fee82800 {
148 compatible = "st,vtac-main";
161 sti-vtac-tx-main@fd349000 {
162 compatible = "st,vtac-main";
186 reset-names = "compo-main", "compo-aux";
/Documentation/devicetree/bindings/iommu/
Drenesas,ipmmu-vmsa.yaml67 renesas,ipmmu-main:
70 Reference to the main IPMMU phandle plus 1 cell. The cell is
72 device. The interrupt bit number needs to match the main IPMMU IMSSTR
85 - renesas,ipmmu-main
/Documentation/devicetree/bindings/media/i2c/
Dadv7604.txt18 main I2C ports. Each map has it own I2C address and acts as a standard
19 slave device on the I2C bus. The main address is mandatory, others are
45 "main", "avlink", "cec", "infoframe", "esdp", "dpp", "afe",
69 reg-names = "main", "edid";
Dadv748x.txt15 main I2C ports. Each map has it own I2C address and acts as a standard
16 slave device on the I2C bus. The main address is mandatory, others are
28 "main", "dpll", "cp", "hdmi", "edid", "repeater",
70 reg-names = "main", "dpll", "cp", "hdmi", "edid", "repeater",
/Documentation/devicetree/bindings/net/
Drockchip-dwmac.txt20 - clocks: <&cru SCLK_MAC>: clock selector for main clock, from PLL or PHY.
32 - clock_in_out: For RGMII, it must be "input", means main clock(125MHz)
38 - assigned-clocks: main clock, should be <&cru SCLK_MAC>;
39 - assigned-clock-parents = parent of main clock.
/Documentation/devicetree/bindings/mfd/
Dbfticu.txt4 Its main functionality is to collect IRQs from the whole chassis and signals
10 - interrupts: the main IRQ line to signal the collected IRQs
Dallwinner,sun8i-a23-prcm.yaml50 # Already checked in the main schema
84 # Already checked in the main schema
115 # Already checked in the main schema
134 # Already checked in the main schema
Dallwinner,sun6i-a31-prcm.yaml48 # Already checked in the main schema
82 # Already checked in the main schema
113 # Already checked in the main schema
146 # Already checked in the main schema
/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-zx.txt4 a main controller and an auxiliary one. For example, on ZX296718 SoC, the
5 main controller is TOP_PMM and the auxiliary one is AON_IOCFG. Both
20 TOP_PMM (main) AON_IOCFG (aux)
/Documentation/process/
Dstable-api-nonsense.rst30 you get that only if your driver is in the main kernel tree. You also
31 get lots of other good benefits if your driver is in the main kernel
53 So, there are two main topics here, binary kernel interfaces and stable
105 keep a Linux kernel driver that is not in the main kernel tree up to
166 So, if you have a Linux kernel driver that is not in the main kernel
172 Simple, get your kernel driver into the main kernel tree (remember we are
180 The very good side effects of having your driver in the main kernel tree
/Documentation/devicetree/bindings/remoteproc/
Dmtk,scp.txt15 should be named "main".
35 clock-names = "main";
/Documentation/devicetree/bindings/soc/qcom/
Dqcom,smem.txt15 Definition: handle to memory reservation for main SMEM memory region.
29 The following example shows the SMEM setup for MSM8974, with a main SMEM region

12345678910>>...22