Home
last modified time | relevance | path

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

12345678910>>...28

/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.yaml55 For samsung,aries-wm8994: HP, SPK, RCV, LINE, Main Mic, Headset Mic,
57 For samsung,fascinate4g-wm8994: HP, SPK, RCV, LINE, Main Mic,
64 main-micbias-supply:
65 description: Supply for the micbias on the main mic
95 - main-micbias-supply
114 main-micbias-supply = <&main_micbias_reg>;
137 "IN1LP", "Main Mic",
138 "IN1LN", "Main Mic",
Dsamsung,midas-audio.yaml47 on the board: HP, SPK, Main Mic, Sub Mic, Headset Mic.
51 description: Supply for the micbias on the Main microphone
132 "IN1LP", "Main Mic",
133 "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/admin-guide/
Ddynamic-debug-howto.rst41 init/main.c:1179 [main]initcall_blacklist =_ "blacklisting initcall %s\012
42 init/main.c:1218 [main]initcall_blacklisted =_ "initcall %s blacklisted\012"
43 init/main.c:1424 [main]run_init_process =_ " with arguments:\012"
44 init/main.c:1426 [main]run_init_process =_ " %s\012"
45 init/main.c:1427 [main]run_init_process =_ " with environment:\012"
46 init/main.c:1429 [main]run_init_process =_ " %s\012"
60 :#> ddcmd '-p; module main func run* +p'
62 init/main.c:1424 [main]run_init_process =p " with arguments:\012"
63 init/main.c:1426 [main]run_init_process =p " %s\012"
64 init/main.c:1427 [main]run_init_process =p " with environment:\012"
[all …]
/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/iommu/
Drenesas,ipmmu-vmsa.yaml75 renesas,ipmmu-main:
80 - description: phandle to main IPMMU
84 the main IPMMU IMSSTR register. Only used by cache IPMMU
87 Reference to the main IPMMU.
98 - renesas,ipmmu-main
120 renesas,ipmmu-main:
125 renesas,ipmmu-main:
/Documentation/devicetree/bindings/clock/
Dkeystone-pll.txt1 Binding for keystone PLLs. The main PLL IP typically has a multiplier,
3 and PAPLL are controlled by the memory mapped register where as the Main
13 - compatible : shall be "ti,keystone,main-pll-clock" or "ti,keystone,pll-clock"
17 post-divider registers are applicable only for main pll clock
24 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
Dstarfive,jh7110-aoncrg.yaml22 - description: Main Oscillator (24 MHz)
29 - description: Main Oscillator (24 MHz)
37 - description: Main Oscillator (24 MHz)
Dmobileye,eyeq5-clk.yaml10 The EyeQ5 clock controller handles 10 read-only PLLs derived from the main
37 Input parent clock to all PLLs. Expected to be the main crystal.
Dartpec6.txt9 There are two external inputs to the main clock controller which should be
14 Main clock controller
/Documentation/devicetree/bindings/phy/
Dti,phy-gmii-sel.yaml65 ti,qsgmii-main-ports:
69 main mode. The size of the array corresponds to the number of QSGMII
70 interfaces and thus, the number of distinct QSGMII main ports,
72 but only one QSGMII interface is desired, repeat the QSGMII main port
106 ti,qsgmii-main-ports:
121 ti,qsgmii-main-ports:
139 ti,qsgmii-main-ports: false
/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/pwm/
Dmediatek,pwm-disp.yaml48 - description: Main Clock
53 - const: main
79 clock-names = "main", "mm";
/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
Dst,stmfx.yaml10 communication with the main MCU. Its main features are GPIO expansion,
11 main MCU IDD measurement (IDD is the amount of current that flows
/Documentation/gpu/rfc/
Dindex.rst9 * Each RFC should be a section in this file, explaining the goal and main design
17 the main core, helper or driver sections.
/Documentation/firmware-guide/acpi/
Dchromeos-acpi-device.rst96 This control method returns the firmware version for the rewritable portion of the main
106 portion of the main processor firmware.
110 This control method returns the firmware version for the read-only portion of the main
120 (bootstrap + recovery ) portion of the main processor firmware.
139 Active Main Firmware Type
168 * - Active Main Firmware Type
170 - The main firmware type which was used during boot.
294 This control method returns the physical memory address of the start of the main processor
303 A DWORD containing the physical memory address of the start of the main processor firmware
/Documentation/devicetree/bindings/soc/mediatek/
Dmtk-svs.yaml39 description: Main clock for MTK SVS controller to work.
42 const: main
90 clock-names = "main";
/Documentation/devicetree/bindings/usb/
Dmediatek,musb.yaml37 - description: The main/core clock
43 - const: main
104 clock-names = "main","mcu","univpll";
/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

12345678910>>...28