Home
last modified time | relevance | path

Searched refs:configuration (Results 1 – 200 of 1093) sorted by relevance

123456

/linux-4.1.27/Documentation/frv/
Dconfiguring.txt10 presented in the configuration tools available):
18 the kernel configuration that need to be considered.
44 There are some architecture specific configuration options in the "General
45 Setup" section of the kernel configuration too:
68 kernel configuration especially for debugging a kernel on this
80 Default configuration for the MB93091-VDK with both CPU board and
86 Default configuration for the MB93091-VDK with CPU board,
93 Default configuration for the MB93093-PDK board running uClinux.
98 Default configuration for the MB93091-VDK with only CB70 CPU board
104 Default configuration for the MB93091-VDK with both CB451 CPU board and
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-bindings.txt3 Hardware modules that control pin multiplexing or configuration parameters
8 Hardware modules whose signals are affected by pin configuration are
14 single static pin configuration, e.g. set up during initialization. Others
22 configuration used by those states.
26 driver loads. This would allow representing a board's static pin configuration
31 they require certain specific named states for dynamic pin configuration.
37 property exists to define the pin configuration. Each state may also be
47 pinctrl-0: List of phandles, each pointing at a pin configuration
48 node. These referenced pin configuration nodes must be child
53 contributing part of the overall configuration. See the next
[all …]
Drenesas,pfc-pinctrl.txt35 The PFC node also acts as a container for pin configuration nodes. Please refer
37 configuration node" and for the common pinctrl bindings used by client devices.
39 Each pin configuration node represents a desired configuration for a pin, a
40 pin group, or a list of pins or pin groups. The configuration can include the
41 function to select on those pin(s) and pin configuration parameters (such as
44 Pin configuration nodes contain pin configuration properties, either directly
45 or grouped in child subnodes. Both pin muxing and configuration parameters can
46 be grouped in that way and referenced as a single pin configuration node by
49 A configuration node or subnode must reference at least one pin (through the
51 configuration parameter. When the function is present only pin groups can be
[all …]
Dqcom,apq8064-pinctrl.txt19 phrase "pin configuration node".
21 Qualcomm's pin configuration nodes act as a container for an arbitrary number of
22 subnodes. Each of these subnodes represents some desired configuration for a
23 pin, a group, or a list of pins or groups. This configuration can include the
24 mux function to select on those pin(s)/group(s), and various pin configuration
31 other words, a subnode that lists a mux function but no pin configuration
32 parameters implies no information about any pin configuration parameters.
38 to specify in a pin configuration subnode:
Dste,nomadik.txt10 phrase "pin configuration node".
12 ST Ericsson's pin configuration nodes act as a container for an arbitrary number of
13 subnodes. Each of these subnodes represents some desired configuration for a
14 pin, a group, or a list of pins or groups. This configuration can include the
15 mux function to select on those pin(s)/group(s), and various pin configuration
30 Required pin configuration subnode properties:
31 - pins: A string array describing the pins affected by the configuration
33 - ste,config: Handle of pin configuration node
54 3: sleep input and keep last input configuration (no pull, pull up or pull down).
Dqcom,ipq8064-pinctrl.txt19 phrase "pin configuration node".
21 Qualcomm's pin configuration nodes act as a container for an arbitrary number of
22 subnodes. Each of these subnodes represents some desired configuration for a
23 pin, a group, or a list of pins or groups. This configuration can include the
24 mux function to select on those pin(s)/group(s), and various pin configuration
31 other words, a subnode that lists a mux function but no pin configuration
32 parameters implies no information about any pin configuration parameters.
38 to specify in a pin configuration subnode:
Dxlnx,zynq-pinctrl.txt10 phrase "pin configuration node".
12 Zynq's pin configuration nodes act as a container for an arbitrary number of
13 subnodes. Each of these subnodes represents some desired configuration for a
14 pin, a group, or a list of pins or groups. This configuration can include the
15 mux function to select on those pin(s)/group(s), and various pin configuration
18 Each configuration node can consist of multiple nodes describing the pinmux and
29 Required properties for configuration nodes:
68 a pin configuration subnode:
Dpinctrl-palmas.txt4 the configuration for Pull UP/DOWN, open drain etc.
14 phrase "pin configuration node".
16 Palmas's pin configuration nodes act as a container for an arbitrary number of
17 subnodes. Each of these subnodes represents some desired configuration for a
18 list of pins. This configuration can include the mux function to select on
19 those pin(s), and various pin configuration parameters, such as pull-up,
26 other words, a subnode that lists a mux function but no pin configuration
27 parameters implies no information about any pin configuration parameters.
Dfsl,imx-pinctrl.txt12 phrase "pin configuration node".
14 Freescale IMX pin configuration node is a node of a group of pins which can be
24 Required properties for pin configuration node:
48 2. The pin configuration node intends to work on a specific function should
51 this group of pins in this pin configuration node are working on.
52 3. The driver can use the function node's name and pin configuration node's
55 as the function name and pin configuration node's name as group name to
57 4. Each pin configuration node should have a phandle, devices can set pins
58 configurations by referring to the phandle of that pin configuration node.
Dlantiq,falcon-pinumx.txt10 phrase "pin configuration node".
12 Lantiq's pin configuration nodes act as a container for an arbitrary number of
13 subnodes. Each of these subnodes represents some desired configuration for a
14 pin, a group, or a list of pins or groups. This configuration can include the
15 mux function to select on those group(s), and two pin configuration parameters:
22 other words, a subnode that lists a mux function but no pin configuration
23 parameters implies no information about any pin configuration parameters.
Dqcom,msm8974-pinctrl.txt19 phrase "pin configuration node".
21 Qualcomm's pin configuration nodes act as a container for an arbitrary number of
22 subnodes. Each of these subnodes represents some desired configuration for a
23 pin, a group, or a list of pins or groups. This configuration can include the
24 mux function to select on those pin(s)/group(s), and various pin configuration
31 other words, a subnode that lists a mux function but no pin configuration
32 parameters implies no information about any pin configuration parameters.
38 to specify in a pin configuration subnode:
Dqcom,pmic-mpp.txt43 phrase "pin configuration node".
45 The pin configuration nodes act as a container for an arbitrary number of
46 subnodes. Each of these subnodes represents some desired configuration for a
47 pin or a list of pins. This configuration can include the
48 mux function to select on those pin(s), and various pin configuration
57 other words, a subnode that lists a mux function but no pin configuration
58 parameters implies no information about any pin configuration parameters.
63 to specify in a pin configuration subnode:
98 outputs are enabled. The hardware ignores the configuration
Dlantiq,xway-pinumx.txt10 phrase "pin configuration node".
12 Lantiq's pin configuration nodes act as a container for an arbitrary number of
13 subnodes. Each of these subnodes represents some desired configuration for a
14 pin, a group, or a list of pins or groups. This configuration can include the
15 mux function to select on those group(s), and two pin configuration parameters:
22 other words, a subnode that lists a mux function but no pin configuration
23 parameters implies no information about any pin configuration parameters.
Dimg,tz1090-pdc-pinctrl.txt10 phrase "pin configuration node".
12 TZ1090-PDC's pin configuration nodes act as a container for an arbitrary number
13 of subnodes. Each of these subnodes represents some desired configuration for a
14 pin, a group, or a list of pins or groups. This configuration can include the
15 mux function to select on those pin(s)/group(s), and various pin configuration
22 other words, a subnode that lists a mux function but no pin configuration
23 parameters implies no information about any pin configuration parameters.
Dmarvell,mvebu-pinctrl.txt9 phrase "pin configuration node".
11 A Marvell SoC pin configuration node is a node of a group of pins which can
19 Required properties for pin configuration node:
22 marvell,pins given in this pin configuration node. The function has to be
Dqcom,apq8084-pinctrl.txt48 phrase "pin configuration node".
50 The pin configuration nodes act as a container for an arbitrary number of
51 subnodes. Each of these subnodes represents some desired configuration for a
52 pin, a group, or a list of pins or groups. This configuration can include the
53 mux function to select on those pin(s)/group(s), and various pin configuration
63 other words, a subnode that lists a mux function but no pin configuration
64 parameters implies no information about any pin configuration parameters.
70 to specify in a pin configuration subnode:
Dqcom,msm8960-pinctrl.txt48 phrase "pin configuration node".
50 The pin configuration nodes act as a container for an arbitrary number of
51 subnodes. Each of these subnodes represents some desired configuration for a
52 pin, a group, or a list of pins or groups. This configuration can include the
53 mux function to select on those pin(s)/group(s), and various pin configuration
63 other words, a subnode that lists a mux function but no pin configuration
64 parameters implies no information about any pin configuration parameters.
70 to specify in a pin configuration subnode:
Dqcom,msm8916-pinctrl.txt48 phrase "pin configuration node".
50 The pin configuration nodes act as a container for an arbitrary number of
51 subnodes. Each of these subnodes represents some desired configuration for a
52 pin, a group, or a list of pins or groups. This configuration can include the
53 mux function to select on those pin(s)/group(s), and various pin configuration
63 other words, a subnode that lists a mux function but no pin configuration
64 parameters implies no information about any pin configuration parameters.
70 to specify in a pin configuration subnode:
Datmel,at91-pinctrl.txt12 phrase "pin configuration node".
14 Atmel AT91 pin configuration node is a node of a group of pins which can be
82 Required properties for pin configuration node:
108 2. The driver can use the function node's name and pin configuration node's
111 as the function name and pin configuration node's name as group name to
113 3. Each pin configuration node should have a phandle, devices can set pins
114 configurations by referring to the phandle of that pin configuration node.
Dqcom,pmic-gpio.txt47 phrase "pin configuration node".
49 The pin configuration nodes act as a container for an arbitrary number of
50 subnodes. Each of these subnodes represents some desired configuration for a
51 pin or a list of pins. This configuration can include the
52 mux function to select on those pin(s), and various pin configuration
62 other words, a subnode that lists a mux function but no pin configuration
63 parameters implies no information about any pin configuration parameters.
68 to specify in a pin configuration subnode:
Dpinctrl-vt8500.txt21 phrase "pin configuration node".
23 Each pin configuration node lists the pin(s) to which it applies, and one or
25 configuration. Each subnode only affects those parameters that are explicitly
27 information about any pull configuration. Similarly, a subnode that lists only
Dnvidia,tegra210-pinmux.txt11 phrase "pin configuration node".
13 Tegra's pin configuration nodes act as a container for an arbitrary number of
14 subnodes. Each of these subnodes represents some desired configuration for a
15 pin, a group, or a list of pins or groups. This configuration can include the
16 mux function to select on those pin(s)/group(s), and various pin configuration
23 other words, a subnode that lists a mux function but no pin configuration
24 parameters implies no information about any pin configuration parameters.
52 - nvidia,lock: Integer. Lock the pin configuration against further changes
Dbrcm,bcm2835-gpio.txt30 phrase "pin configuration node".
32 Each pin configuration node lists the pin(s) to which it applies, and one or
34 configuration. Each subnode only affects those parameters that are explicitly
36 information about any pull configuration. Similarly, a subnode that lists only
Dimg,tz1090-pinctrl.txt6 configuration registers (CR_PADS_* and CR_IF_CTL0).
10 phrase "pin configuration node".
12 TZ1090's pin configuration nodes act as a container for an arbitrary number of
13 subnodes. Each of these subnodes represents some desired configuration for a
14 pin, a group, or a list of pins or groups. This configuration can include the
15 mux function to select on those pin(s)/group(s), and various pin configuration
22 other words, a subnode that lists a mux function but no pin configuration
23 parameters implies no information about any pin configuration parameters.
Dnvidia,tegra20-pinmux.txt10 phrase "pin configuration node".
12 Tegra's pin configuration nodes act as a container for an arbitrary number of
13 subnodes. Each of these subnodes represents some desired configuration for a
14 pin, a group, or a list of pins or groups. This configuration can include the
15 mux function to select on those pin(s)/group(s), and various pin configuration
22 other words, a subnode that lists a mux function but no pin configuration
23 parameters implies no information about any pin configuration parameters.
Dfsl,mxs-pinctrl.txt5 function is GPIO. The configuration on the pins includes drive strength,
17 subnodes. Each of these subnodes represents some desired configuration for
28 one is to adjust the pin configuration for some particular pins that need a
29 different configuration than what is defined in group node. The binding
120 adjusting the configuration for pins card-detection and clock from what group
121 node mmc0-8bit defines. Only the configuration properties to be adjusted need
Dpinctrl-st.txt104 Required properties for pin configuration node:
105 - st,pins : Child node with list of pins with configuration.
111 Every PIO is represented with 4-7 parameters depending on retime configuration.
118 -mode :pin configuration is selected from one of the below values.
126 Possible retime configuration are:
Dmeson,pinctrl.txt28 configuration for a pin or a group. Those nodes can be pinmux nodes or
29 configuration nodes.
38 Required properties for configuration nodes:
Dste,abx500.txt9 phrase "pin configuration node".
11 ST Ericsson's pin configuration nodes use the generic pin multiplexing
12 and pin configuration bindings, see pinctrl-bindings.txt
Dsamsung-pinctrl.txt55 function selection or pin configuration (or both) have to applied. This
75 configuration that should be applied on all the pins listed in the
76 "samsung,pins" property of the child node. The following pin configuration
80 - samsung,pin-pud: Pull up/down configuration.
81 - samsung,pin-drv: Drive strength configuration.
82 - samsung,pin-pud-pdn: Pull up/down configuration in power down mode.
83 - samsung,pin-drv-pdn: Drive strength configuration in power down mode.
90 pin configuration property (one or more) or both.
93 pin configuration should use the bindings listed in the "pinctrl-bindings.txt"
Dallwinner,sunxi-pinctrl.txt5 the first two functions being GPIO in and out. The configuration on
28 configuration, drive strength and pullups. If one of these options is
Dbrcm,bcm11351-pinctrl.txt22 should also contain the pin configuration nodes that client devices reference,
27 Each pin configuration node is a sub-node of the pin controller node and is a
33 "pin configuration node".
37 A pin group node specifies the desired pin mux and/or pin configuration for an
125 // pin configuration node
156 // other pin configuration nodes
160 In the example above, "dev_a_active" is a pin configuration node with a number
Dnvidia,tegra124-xusb-padctl.txt31 the pinctrl-bindings.txt document. Typically a single, static configuration is
39 words, if a subnode that lists a function but no pin configuration parameters
40 implies no information about any pin configuration parameters. Similarly, a
/linux-4.1.27/Documentation/arm/Samsung/
DGPIO.txt29 PIN configuration
32 Pin configuration is specific to the Samsung architecture, with each SoC
33 registering the necessary information for the core gpio configuration
37 driver or machine to change gpio configuration.
DOverview.txt35 s5pc110_defconfig - S5PC110 specific default configuration
36 s5pv210_defconfig - S5PV210 specific default configuration
/linux-4.1.27/drivers/staging/speakup/
DKconfig49 or m to build it as a module. See the configuration
58 or m to build it as a module. See the configuration
66 or m to build it as a module. See the configuration
74 build it as a module. See the configuration help on the
82 or m to build it as a module. See the configuration
91 or m to build it as a module. See the configuration
101 configuration help on the Speakup choice above for more
112 a module. See the configuration help on the Speakup
135 configuration help on the Speakup choice above for more
146 configuration help on the Speakup choice above for more
[all …]
/linux-4.1.27/Documentation/arm/
DNetwinder24 0x0203 RWA010 configuration read
27 0x0279 RWA010 configuration index
32 0x0370 - 0x0371 W83977F configuration registers
40 0x0a79 RWA010 configuration write
DCCN.txt13 description of available events and configuration options
18 directory provides configuration templates for all documented
/linux-4.1.27/net/xfrm/
DKconfig2 # XFRM configuration
14 tristate "Transformation user configuration interface"
18 Support for Transformation(XFRM) user configuration interface
39 instance, in a Mobile IPv6 environment with IPsec configuration
79 environment with IPsec configuration where mobile nodes
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-class-net-grcan7 Hardware configuration of physical interface 0. This file reads
8 and writes the "Enable 0" bit of the configuration register.
19 Hardware configuration of physical interface 1. This file reads
20 and writes the "Enable 1" bit of the configuration register.
Dconfigfs-usb-gadget38 The attributes of a configuration:
40 bmAttributes - configuration characteristics
48 strings for this configuration.
56 configuration - configuration description
Dsysfs-platform-eeepc-laptop31 Change CPU clock configuration.
32 On the Eee PC 1000H there are three available clock configuration:
37 Available configuration are listed in available_cpufv file.
Dsysfs-class-cxl84 AFU configuration records (eg. /sys/class/cxl/afu0.0/cr0):
86 An AFU may optionally export one or more PCIe like configuration records, known
87 as AFU configuration records, which will show up here (if present).
94 configuration record.
101 configuration record.
108 configuration record.
114 This binary file provides raw access to the AFU configuration
116 or extended configuration space defined by the PCIe
Dsysfs-platform-asus-wmi6 Change CPU clock configuration (write-only).
7 There are three available clock configuration:
Dsysfs-class-regulator257 implementing suspend voltage configuration constraints.
268 implementing suspend voltage configuration constraints.
279 implementing suspend voltage configuration constraints.
290 configuration constraints.
300 for regulators implementing suspend mode configuration
312 configuration constraints.
322 configuration constraints.
335 suspend configuration constraints.
348 suspend configuration constraints.
Dsysfs-firmware-gsmi41 entire firmware configuration to be reset to
43 a reboot is required for the configuration to be
/linux-4.1.27/arch/mips/sibyte/swarm/
Dsetup.c46 #error invalid SiByte board configuration
56 #error invalid SiByte board configuration
134 #error invalid SiByte board configuration in plat_mem_setup()
/linux-4.1.27/drivers/char/mwave/
DREADME19 thinkpad configuration utility then this parameter allows the
24 thinkpad configuration utility then this parameter allows the
29 thinkpad configuration utility then this parameter allows the
34 thinkpad configuration utility then this parameter allows the
/linux-4.1.27/Documentation/devicetree/bindings/phy/
Dphy-miphy28lp.txt9 - st,syscfg : Should be a phandle of the system configuration register group
26 filled in "reg". It can also contain the offset of the system configuration
29 - st,syscfg : Offset of the parent configuration register.
104 Device nodes should specify the configuration required in their "phys"
106 specifying which configuration to use, as described in phy-bindings.txt.
115 Macro definitions for the supported miphy configuration can be found in:
/linux-4.1.27/Documentation/sound/oss/
DAudioExcelDSP1612 The Audio Excel configuration, is now done with the standard Linux setup.
20 If you want to change the configuration of the sound board, be sure to
21 check off all the configuration items before re-configure it.
44 A configuration file in /etc/modprobe.d/ directory will have lines like this:
54 the sound card. Installation dependencies must be written in configuration
63 With the above configuration, loading ad1848 or opl3 modules, will
83 4) <ctrl>-<alt>-<del> and boot Linux. This will maintain the DOS configuration
DPAS1627 The sound driver configuration dialog
30 Sound configuration starts by making some yes/no questions. Be careful
34 configuration may also be made modular by answering m to configuration
37 Note also that all questions may not be asked. The configuration program
63 The following configuration options are relevant to configuring the PAS16:
69 about your sound card and its configuration down (I/O port,
140 configuration options:
153 The io address of 0x388 is default configuration on the PAS16. The
155 configuration enables PAS16, 8-bit Soundblaster and OPL3
DSoundPro43 As with PnP cards, some configuration is required. There are two ways
47 configuration of installed PnP devices in a BIOS menu, which should
55 configuration):
69 in your isapnp configuration file, and that there is no conflict with
/linux-4.1.27/Documentation/video4linux/
Domap3isp.txt79 (When using parallel interface one must pay account to correct configuration
103 does not fall under the standard IOCTLs --- gamma tables and configuration of
141 The update field in the structures tells whether to update the configuration
148 configuration data for the function.
183 The associated configuration pointer for the function may not be NULL when
184 enabling the function. When disabling a function the configuration pointer is
191 The statistics subdevs do offer more dynamic configuration options than the
224 module's data output depends on the requested configuration. Although the
229 module or request the necessary buffer size during the first configuration
232 The internal buffer size allocation considers the requested configuration's
[all …]
Dfimc.txt27 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
104 In typical use case there could be a following capture pipeline configuration:
108 configuration flow must be from left to right, and the video node is
110 When we don't use sub-device user space API the whole configuration of all
113 the sub-devices (format, crop), to avoid resetting the subdevs' configuration
114 when the last configuration steps at the video node is performed.
/linux-4.1.27/Documentation/
Dhsi.txt66 - set RX configuration
69 - get RX configuration
72 - set TX configuration
75 - get TX configuration
/linux-4.1.27/Documentation/devicetree/bindings/pci/
Ddesignware-pcie.txt5 - reg: Should contain the configuration address space.
6 - reg-names: Must be "config" for the PCIe configuration space.
7 (The old way of getting the configuration address space from "ranges"
Dsamsung,exynos5440-pcie.txt28 ranges = <0x00000800 0 0x40000000 0x40000000 0 0x00001000 /* configuration space */
48 ranges = <0x00000800 0 0x60000000 0x60000000 0 0x00001000 /* configuration space */
Dpci-rcar-gen2.txt13 second is for the bridge configuration and control registers.
26 Example SoC configuration:
Dxgene-pci.txt10 "csr": controller configuration registers.
11 "cfg": pcie configuration space registers.
/linux-4.1.27/Documentation/power/regulator/
Ddesign.txt10 - Errors in regulator configuration can have very serious consequences
12 - It is not possible to automatically determine the power configuration
25 requirement to do any runtime configuration of their power beyond
/linux-4.1.27/Documentation/usb/
Dgadget_configfs.txt27 and which functions each configuration will provide.
102 <number> is the configuration's number, e.g.:
110 Each configuration also needs its strings, so a subdirectory must be created
115 Then the configuration string can be specified:
117 $ echo <configuration> > configs/c.1/strings/0x409/configuration
119 Some attributes can also be set for a configuration, e.g.:
150 is specifying which function is available in which configuration (the same
183 ./configs/c.1/strings/0x409/configuration
226 where <config name>.<number> specify the configuration and <function> is
227 a symlink to a function being removed from the configuration, e.g.:
[all …]
Dgadget_multi.txt9 In it's standard configuration it provides a single USB configuration
17 Please note that if you use non-standard configuration (that is enable
33 This is also true for two configuration set-up with RNDIS
34 configuration being the first one. Linux host will use the second
35 configuration with CDC ECM which should work better under Linux.
53 configuration so a dual RNDIS and CDC ECM gadget won't work unless you
Dfunctionfs.txt4 unique behaviour. It may be added to an USB configuration only after
8 the configuration).
26 numbers and changing of the configuration (which means that
28 configuration changes to (say) endpoint 2)). "ep0" is used
Dproc_usb_info.txt57 configuration of the device. Multi-byte fields in the device descriptor
58 are converted to host endianness by the kernel. The configuration
59 descriptors are in bus endian format! The configuration descriptor
60 are wTotalLength bytes apart. If a device returns less configuration
101 C = Configuration descriptor info. (* = active configuration)
213 | |__ "*" indicates the active configuration (others are " ")
217 rather differently. For example, a bus-powered configuration
219 one device configuration can be active at a time; most devices
220 have only one configuration.
222 Each configuration consists of one or more interfaces. Each
/linux-4.1.27/Documentation/devicetree/bindings/arm/freescale/
Dfsl,vf610-mscm-cpucfg.txt4 block of registers which contains CPU configuration information.
8 - reg: the register range of the MSCM CPU configuration registers
/linux-4.1.27/net/netlabel/
DKconfig2 # NetLabel configuration
13 for configuration tools and additional documentation.
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dwm8903.txt26 - gpio-cfg : A list of GPIO configuration register values. The list must
27 be 5 entries long. If absent, no configuration of these registers is
29 configuration will not be modified.
Dadi,ssm2602.txt3 SSM2602 support both I2C and SPI as the configuration interface,
5 SSM2603 and SSM2604 only support I2C as the configuration interface.
Dimx-audmux.txt11 An initial configuration can be setup using child nodes.
18 - fsl,port-config : List of configuration options for the specific port.
Dwm8962.txt19 - gpio-cfg : A list of GPIO configuration register values. The list must
20 be 6 entries long. If absent, no configuration of these registers is
Dcs35l32.txt27 - cirrus,sdout-datacfg : Data configuration for dual CS35L32 applications only.
28 Determines the data packed in a two-CS35L32 configuration.
/linux-4.1.27/Documentation/blockdev/
Dmflash.txt5 2. Reserved area configuration
26 2. Reserved area configuration
29 Note that boot loader's size of reserved area and kernel configuration value
34 configuration file is all. Here is some pseudo example.
DREADME.DAC96039 Please include with the bug report the complete configuration messages reported
42 hardware configuration. Driver bugs are actually quite rare; if you encounter
44 Technical Support as the problem is related to the hardware configuration
48 regarding installation and configuration of the controllers. This document
63 online configuration management capabilities. Except for initial configuration
272 installation and subsequent configuration of additional storage. The BIOS
277 configuration and status monitoring is then to avoid system downtime when disk
278 drives fail and must be replaced. Mylex's online monitoring and configuration
284 The primary interfaces for controller configuration and status monitoring are
343 special file to initiate a configuration operation, and the results of the
[all …]
/linux-4.1.27/arch/arm/boot/dts/
Dtegra124-nyan-blaze-emc.dtsi95 nvidia,emc-configuration = <
263 nvidia,emc-configuration = <
431 nvidia,emc-configuration = <
599 nvidia,emc-configuration = <
767 nvidia,emc-configuration = <
935 nvidia,emc-configuration = <
1103 nvidia,emc-configuration = <
1271 nvidia,emc-configuration = <
1439 nvidia,emc-configuration = <
1607 nvidia,emc-configuration = <
[all …]
Dtegra124-jetson-tk1-emc.dtsi106 nvidia,emc-configuration = <
274 nvidia,emc-configuration = <
442 nvidia,emc-configuration = <
610 nvidia,emc-configuration = <
778 nvidia,emc-configuration = <
946 nvidia,emc-configuration = <
1114 nvidia,emc-configuration = <
1282 nvidia,emc-configuration = <
1450 nvidia,emc-configuration = <
1618 nvidia,emc-configuration = <
[all …]
Dtegra124-nyan-big-emc.dtsi95 nvidia,emc-configuration = <
263 nvidia,emc-configuration = <
431 nvidia,emc-configuration = <
599 nvidia,emc-configuration = <
767 nvidia,emc-configuration = <
935 nvidia,emc-configuration = <
1103 nvidia,emc-configuration = <
1271 nvidia,emc-configuration = <
1439 nvidia,emc-configuration = <
1607 nvidia,emc-configuration = <
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/net/
Dfixed-link.txt27 - b: duplex configuration: 0 for half duplex, 1 for full duplex
29 - d: pause configuration: 0 for no pause, 1 for pause
30 - e: asymmetric pause configuration: 0 for no asymmetric pause, 1 for
Dsh_eth.txt23 - pinctrl-0: phandle, referring to a default pin configuration node.
28 - pinctrl-names: pin configuration state name ("default").
/linux-4.1.27/drivers/usb/gadget/legacy/
DKconfig21 Gadget Zero is a two-configuration device. It either sinks and
37 this device, and arrange to select an appropriate configuration.
134 a second device configuration, supporting RNDIS to talk to such
180 programs implement a single-configuration USB device, including
208 bool "Include configuration with CDC ECM (Ethernet)"
214 Include a configuration with CDC ECM function (Ethernet) and the
218 bool "Include configuration with RNDIS (Ethernet)"
223 Include a configuration with RNDIS function (Ethernet) and the Filesystem.
226 bool "Include 'pure' configuration"
229 Include a configuration with the Function Filesystem alone with
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-dma.txt33 configuration.. Navigator cloud global address needs to be programmed
46 - Tx DMA channel configuration register region (txchan).
47 - Rx DMA channel configuration register region (rxchan).
48 - Tx DMA channel Scheduler configuration register region (txsched).
49 - Rx DMA flow configuration register region (rxflow).
/linux-4.1.27/Documentation/networking/
Dframerelay.txt11 The configuration script will ask you how many DLCIs you need, as well as
26 This program makes use of a configuration file (which dlcicfg can also read)
28 any board specific configuration. The Sangoma module of fradcfg loads the
30 an initial configuration.
Dcs89x0.txt71 such, the configuration procedures differ somewhat between the two types of
147 Utility if you want to change the adapter's configuration in EEPROM.
150 configuration parameters on the command-line to override the EEPROM's settings
151 or for interface configuration when an EEPROM is not used. (CS8920-based
157 installing a CS8900-based adapter and the default configuration is acceptable.)
175 You should only change the default configuration settings if conflicts with
176 another adapter exists. To change the adapter's configuration, run the
207 with the 'modprobe' command. Many of the adapter's configuration parameters can
210 configuration when an EEPROM is not used.
218 configuration options are available on the command line:
[all …]
Ddl2k.txt51 7. Run "netconfig" or "netconf" to create configuration script ifcfg-eth0
130 Note that this is meaningful only if the system can find a configuration
141 to see the current network configuration.
158 2. Locate the boot module configuration file, most commonly in the
167 3. Locate the network configuration scripts, normally the
168 /etc/sysconfig/network-scripts directory, and create a configuration
170 4. Note that for most Linux distributions, Red Hat included, a configuration
247 Here is a sample of a simple configuration script:
Di40e.txt32 The driver is enabled via the standard kernel configuration system,
59 The driver utilizes the ethtool interface for driver configuration and
68 DCB configuration is not currently supported.
Dipv6.txt6 /etc/modules.d/*.conf configuration files, or in a distro-specific
7 configuration file.
Dltpc.txt9 configuration dialog. You can also compile it as a module.
28 them as options in a configuration file in /etc/modprobe.d/ directory:
41 The appropriate netatalk configuration depends on whether you are
117 the configuration of the network.
Dbonding.txt142 /etc/modrobe.d/*.conf configuration files, or in a distro-specific
143 configuration file (some of which are detailed in the next section).
582 Most switches will require some type of configuration
976 SuSE SLES 9's networking configuration system does support
977 bonding, however, at this writing, the YaST system configuration
983 yast2 sysconfig configuration utility. The goal is for to create an
987 name of the configuration file for each device will be of the form:
995 created, it is necessary to edit the configuration files for the slave
1015 it's time to create the configuration file for the bonding device
1019 network configuration system will correctly start multiple instances
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/mfd/
Dtwl4030-power.txt15 3530 that needs a special configuration for warm reset to work.
17 When using ti,twl4030-power-idle, the TI recommended configuration
21 configuration is used with the external oscillator being shut
Das3722.txt34 phrase "pin configuration node".
54 configuration for a list of pins. This configuration can
56 various pin configuration parameters, such as pull-up,
/linux-4.1.27/Documentation/spi/
D00-INDEX6 - AVR Butterfly SPI driver overview and pin configuration.
8 - Basic EP93xx SPI driver configuration.
Dpxa2xx10 - Per slave device (chip) configuration.
21 "platform device". The master configuration is passed to the driver via a table
44 Below is a sample configuration using the PXA255 NSSP.
90 Each slave device attached to the PXA must provide slave specific configuration
93 will uses the configuration whenever the driver communicates with the slave
147 "spi_board_info.controller_data" field. Below is a sample configuration using
Dep93xx_spi11 Sample configuration
14 Typically driver configuration is done in platform board files (the files under
/linux-4.1.27/net/decnet/
DKconfig2 # DECnet configuration
21 in configuration at run time.
36 filtering". The first two are required to allow configuration via
/linux-4.1.27/drivers/net/ethernet/davicom/
DKconfig2 # Davicom device configuration
20 This configuration forces the DM9000 to use the NSR's LinkStatus
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/
Ddcsr.txt99 configuration block.
128 configuration block.
165 configuration block.
190 configuration block.
210 the DPAA Debug Controller. This controller controls debug configuration
227 configuration block.
255 configuration block.
286 configuration block.
315 configuration block.
345 configuration block.
[all …]
Dguts.txt4 enabling, power-on-reset configuration monitoring, general-purpose
5 I/O signal configuration, alternate function selection for multiplexed
Dsrio-rmu.txt22 length of the SRIO configuration registers for message units
53 length of the SRIO configuration registers for message units
83 length of the SRIO configuration registers for message units
113 length of the SRIO configuration registers for message units
Dmpic.txt53 configuration registers to a sane state-- masked or
164 * this corresponds to interrupt source configuration
167 * The interrupt source configuration registers begin
174 * The interrupt source configuration registers begin
/linux-4.1.27/Documentation/x86/x86_64/
Duefi.txt19 - Build the kernel with the following configuration.
22 If EFI runtime services are expected, the following configuration should
28 elilo bootloader with x86_64 support, elilo configuration file,
/linux-4.1.27/drivers/net/ethernet/qlogic/
DKconfig2 # QLogic network device configuration
43 This configuration parameter enables Single Root Input Output
53 This configuration parameter enables DCB support in QLE83XX
74 This configuration parameter can be used to read the
/linux-4.1.27/Documentation/misc-devices/
Dmax687521 At reset, the MAX6875 reads the configuration EEPROM into its configuration
63 The configuration registers are at addresses 0x00 - 0x45.
76 The configuration EEPROM is at addresses 0x8000 - 0x8045.
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-bus-usb98 bConfigurationValue of the *active* configuration for the
100 active configuration (unconfigure the device). Writing
101 another value will change the active configuration.
104 configuration with a value equal to 0. Writing 0 to
106 configuration, rather then unconfigure the device.
124 descriptors for each configuration of the device.
/linux-4.1.27/Documentation/arm/sti/
Doverview.txt13 configuration
16 A generic configuration is provided for both STiH415/416, and can be used as the
/linux-4.1.27/Documentation/devicetree/bindings/arm/msm/
Dqcom,saw2.txt11 SAW2 revisions differ in the register offset and configuration data. Also, the
12 same revision of the SAW in different SoCs may have different configuration
16 configuration and initialization data. The compatible string is used to
/linux-4.1.27/Documentation/serial/
Dn_gsm.txt29 struct termios configuration;
48 /* get n_gsm configuration */
56 /* set the new configuration */
64 each modem has its configuration and some DLC have dedicated functions,
Dmoxa-smartio16 3.4 Module driver configuration
17 3.5 Static driver configuration for Linux kernel 2.4.x and 2.6.x.
18 3.6 Custom configuration
103 3.4 Module driver configuration
104 3.5 Static driver configuration for Linux kernel 2.4.x, 2.6.x.
105 3.6 Custom configuration
194 3.4 Module driver configuration
263 However, it's better to have a boot time configuration to
264 eliminate manual operation. Boot time configuration can be
299 3.5 Static driver configuration for Linux kernel 2.4.x and 2.6.x
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/extcon/
Dextcon-rt8973a.txt7 speed USB operation. Also, RT8973A support 'auto-configuration' mode.
8 If auto-configuration mode is enabled, RT8973A would control internal h/w patch
/linux-4.1.27/Documentation/devicetree/bindings/clock/
Dti,cdce706.txt15 configuration. Use clk_in0 and clk_in1 in case of independent
16 single-ended LVCMOS inputs configuration.
Dsilabs,si5351.txt33 output is not set, the eeprom configuration is not overwritten.
81 * overwrite clkout0 configuration with:
98 * overwrite clkout1 configuration with:
113 * overwrite clkout2 configuration with:
/linux-4.1.27/Documentation/devicetree/bindings/mmc/
Dsdhci-st.txt22 - pinctrl-0: Phandle referencing pin configuration of the sd/emmc controller.
62 /* Example stih416e eMMC configuration */
76 /* Example SD stih407 family configuration */
93 /* Example eMMC stih407 family configuration */
/linux-4.1.27/net/can/
DKconfig2 # Controller Area Network (CAN) network layer core configuration
44 tristate "CAN Gateway/Router (with netlink configuration)"
52 by the netlink configuration interface known e.g. from iptables.
/linux-4.1.27/drivers/net/usb/
Dkaweth.c247 struct kaweth_ethernet_configuration configuration; member
311 (void *)&kaweth->configuration, in kaweth_read_configuration()
312 sizeof(kaweth->configuration), in kaweth_read_configuration()
1108 dev_info(dev, "Statistics collection: %x\n", kaweth->configuration.statistics_mask); in kaweth_probe()
1109 …dev_info(dev, "Multicast filter limit: %x\n", kaweth->configuration.max_multicast_filters & ((1 <<… in kaweth_probe()
1110 dev_info(dev, "MTU: %d\n", le16_to_cpu(kaweth->configuration.segment_size)); in kaweth_probe()
1111 dev_info(dev, "Read MAC address %pM\n", kaweth->configuration.hw_addr); in kaweth_probe()
1113 if(!memcmp(&kaweth->configuration.hw_addr, in kaweth_probe()
1168 memcpy(netdev->dev_addr, &kaweth->configuration.hw_addr, in kaweth_probe()
1169 sizeof(kaweth->configuration.hw_addr)); in kaweth_probe()
[all …]
/linux-4.1.27/drivers/pinctrl/
DKconfig17 bool "Support pin configuration controllers" if COMPILE_TEST
45 AS3722 device supports the configuration of GPIO pins for different
47 open drain configuration for the GPIO pins of AS3722 devices. It also
200 Palmas device supports the configuration of pins for different
202 open drain configuration for the Palmas series devices like
/linux-4.1.27/Documentation/devicetree/bindings/media/i2c/
Dtvp514x.txt17 - hsync-active: HSYNC Polarity configuration for endpoint.
19 - vsync-active: VSYNC Polarity configuration for endpoint.
Dtvp7002.txt10 - hsync-active: HSYNC Polarity configuration for the bus. Default value when
13 - vsync-active: VSYNC Polarity configuration for the bus. Default value when
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dfsl.txt101 SCFG is the supplemental configuration unit, that provides SoC specific
102 configuration and status registers for the chip. Such as getting PEX port
115 DCFG is the device configuration unit, that provides general purpose
116 configuration and status for the device. Such as setting the secondary
Dspear-misc.txt1 SPEAr Misc configuration
Dccn.txt10 (16MB) of the configuration registers block
Drtsm-dcscb.txt5 functionality for controlling clocks, resets and configuration pins in
/linux-4.1.27/Documentation/isdn/
DREADME.gigaset100 configuration file like /etc/modprobe.d/gigaset.conf for these.
131 If cmd==1, the device is set to adapter configuration mode where commands
137 Note that there is no ioctl command for leaving adapter configuration
139 configuration mode, write the command ATO to the device.
156 If the driver is compiled with CAPI support (kernel configuration option
180 applications only. Most distributions provide some configuration utility
202 You can use some configuration tool of your distribution to configure this
204 configuration files and chat scripts in the gigaset-VERSION/ppp directory
214 to an appropriate module configuration file, like
239 to an appropriate module configuration file, like
[all …]
/linux-4.1.27/Documentation/hwmon/
Dadt746236 configuration data is only read once per minute.
45 determining an optimal configuration for the automatic PWM control.
48 information from the configuration registers.
Dadm127562 configuration. On ADM1075, vout1 reports the voltage on
77 configuration, either curr1_lcrit or curr1_crit is
81 configuration, either curr1_lcrit or curr1_crit is
Dvexpress23 configuration and control. Theses microcontrollers can also monitor the
29 The configuration devices are _not_ memory mapped and must be accessed
Dsmsc47b39785 To program the configuration registers, the following sequence must be followed:
95 In configuration mode, the INDEX PORT is located at the CONFIG PORT address and
98 The desired configuration registers are accessed in two steps:
103 b. Write the address of the desired configuration register within the
/linux-4.1.27/Documentation/arm/pxa/
Dmfp.txt54 2. Alternate function configuration is removed from this GPIO controller,
86 because pin configuration definitions may conflict in these file (i.e.
90 (in addition to handle MFP configuration differences, they also handle
204 2. processor-neutral bit definitions for a possible MFP configuration
226 for implementation of the pin configuration to take effect for the actual
236 * a possible MFP configuration is represented by a 32-bit integer
247 * MFP_CFG_DEFAULT - default MFP configuration value, with
278 Register settings on PXA3xx for a pin configuration is actually very
283 The conversion from a generic pin configuration to the actual register
/linux-4.1.27/Documentation/devicetree/bindings/dma/
Datmel-dma.txt27 3. Parameters for the at91 DMA configuration register which are device
31 - bit 11-8: FIFO configuration. 0 for half FIFO, 1 for ALAP, 2 for ASAP.
Datmel-xdma.txt12 - The 1st cell specifies the channel configuration register:
34 2. Channel configuration register. Configurable fields are:
/linux-4.1.27/drivers/misc/sgi-xp/
Dxp_uv.c113 #error not a supported configuration in xp_expand_memprotect_uv()
143 #error not a supported configuration in xp_restrict_memprotect_uv()
/linux-4.1.27/Documentation/devicetree/bindings/hsi/
Dclient-devices.txt5 Required HSI configuration properties:
18 Optional HSI configuration properties:
/linux-4.1.27/arch/m32r/kernel/
Dtime.c102 #error no chip configuration in m32r_gettimeoffset()
196 #error no chip configuration in time_init()
/linux-4.1.27/Documentation/rapidio/
Drapidio.txt113 RapidIO subsystem configuration options allow users to build enumeration and
119 Depending on selected enumeration/discovery build configuration, there are
159 on RapidIO subsystem build configuration:
172 - from modprobe configuration file using configuration command "options",
174 configuration file is provided in the section below.
186 to access the configuration space of devices.
197 enumeration/discovery RapidIO configuration selection. To enable automatic
201 This configuration requires synchronized start of all RapidIO endpoints that
212 Depending on RapidIO network size and configuration this automatic
263 endpoint if access to its configuration registers is required. If a switch (or
[all …]
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DGPIO.txt11 There are a number of conditions attached to the configuration
89 of GPIO pins, and the configuration values for them. This
109 The following function allows the configuration of a given pin to
123 Reading the current configuration
126 The current configuration of a pin can be read by using standard
/linux-4.1.27/Documentation/phy/
Dsamsung-usb2.txt39 directory. Each SoC's configuration is stored in an instance of the
50 array that contains the configuration for each phy. The has_mode_switch
56 For example the configuration for Exynos 4210 is following:
70 The exynos4210_phys configuration array is as follows:
/linux-4.1.27/drivers/dca/
DKconfig2 # DCA server configuration
/linux-4.1.27/arch/powerpc/platforms/52xx/
DKconfig17 - CDM configuration (clocking) is setup correctly by firmware,
20 - PCI is supported if enabled in the kernel configuration
/linux-4.1.27/drivers/net/ethernet/mellanox/mlx5/core/
DKconfig2 # Mellanox driver configuration
/linux-4.1.27/drivers/pnp/pnpacpi/
DKconfig2 # Plug and Play ACPI configuration
/linux-4.1.27/arch/cris/arch-v32/mach-a3/
DKconfig37 hex "PIO CE0 configuration"
41 hex "PIO CE1 configuration"
45 hex "PIO CE2 configuration"
/linux-4.1.27/drivers/bus/
DKconfig75 Driver needed for the MBus configuration on Marvell EBU SoCs
108 bool "Versatile Express configuration bus"
114 Platform configuration infrastructure for the ARM Ltd.
/linux-4.1.27/drivers/mtd/devices/
Dst_spi_fsm.c268 uint32_t configuration; member
901 if ((fsm->configuration & CFG_S25FL_CHECK_ERROR_FLAGS) && in stfsm_wait_busy()
1184 fsm->configuration = (CFG_READ_TOGGLE_32BIT_ADDR | in stfsm_mx25_config()
1261 fsm->configuration = (CFG_WRITE_TOGGLE_32BIT_ADDR | in stfsm_n25q_config()
1475 fsm->configuration |= CFG_S25FL_CHECK_ERROR_FLAGS; in stfsm_s25fl_config()
1534 if (fsm->configuration & CFG_READ_TOGGLE_32BIT_ADDR) in stfsm_read()
1573 if (fsm->configuration & CFG_READ_TOGGLE_32BIT_ADDR) in stfsm_read()
1598 if (fsm->configuration & CFG_WRITE_TOGGLE_32BIT_ADDR) in stfsm_write()
1660 if (ret && fsm->configuration & CFG_S25FL_CHECK_ERROR_FLAGS) in stfsm_write()
1664 if (fsm->configuration & CFG_WRITE_TOGGLE_32BIT_ADDR) in stfsm_write()
[all …]
/linux-4.1.27/drivers/staging/unisys/visorutil/
DKconfig2 # Unisys timskmod configuration
/linux-4.1.27/drivers/staging/unisys/virtpci/
DKconfig2 # Unisys virtpci configuration
/linux-4.1.27/drivers/staging/unisys/visorchannel/
DKconfig2 # Unisys visorchannel configuration
/linux-4.1.27/drivers/staging/unisys/uislib/
DKconfig2 # Unisys uislib configuration
/linux-4.1.27/drivers/net/ethernet/cisco/enic/
DKconfig2 # Cisco device configuration
/linux-4.1.27/drivers/staging/unisys/visorchipset/
DKconfig2 # Unisys visorchipset configuration
/linux-4.1.27/scripts/kconfig/
D.gitignore15 # configuration programs
/linux-4.1.27/Documentation/s390/
D3270.txt40 running the configuration script (config3270.sh, in this directory).
43 configuration script every time you change the console's address (perhaps
45 you should rerun the configuration script every time your set of 3270s,
47 one another. ReIPL as soon as possible after running the configuration
51 configuration file under /etc/modprobe.d/. If you are working on a VM
104 correctly to the configuration requests of the next step. If
108 5. Run the 3270 configuration script config3270. It is
123 configuration has changed and you're reusing config3270, you
125 Change 3270 configuration
/linux-4.1.27/drivers/block/mtip32xx/
DKconfig2 # mtip32xx device driver configuration
/linux-4.1.27/drivers/i2c/algos/
DKconfig2 # I2C algorithm drivers configuration
/linux-4.1.27/drivers/staging/unisys/virthba/
DKconfig2 # Unisys virthba configuration
/linux-4.1.27/drivers/rapidio/devices/
DKconfig2 # RapidIO master port configuration
/linux-4.1.27/
DKconfig2 # For a description of the syntax of this configuration file,
/linux-4.1.27/drivers/gpu/drm/amd/amdkfd/
DKconfig2 # Heterogenous system architecture configuration
/linux-4.1.27/Documentation/devicetree/bindings/video/
Datmel,lcdc.txt55 - atmel,dmacon: dma controller configuration
56 - atmel,lcdcon2: lcd controller configuration
/linux-4.1.27/Documentation/sound/alsa/soc/
Dplatform.txt61 2) Digital audio interface configuration
63 4) SYSCLK configuration
/linux-4.1.27/Documentation/devicetree/bindings/c6x/
Ddscr.txt9 more configuration registers often protected by a lock register where one or
11 configuration register for writes. These configuration register may be used to
13 sources (internal or pin), etc. In some cases, a configuration register is
/linux-4.1.27/drivers/net/wimax/
DKconfig2 # WiMAX LAN device drivers configuration
/linux-4.1.27/arch/m32r/include/asm/
Ds1d13806.h101 #error no platform configuration
Dptrace.h30 #error unknown isa configuration
/linux-4.1.27/drivers/net/ethernet/aeroflex/
DKconfig2 # Aeroflex Gaisler network device configuration
/linux-4.1.27/Documentation/devicetree/bindings/arm/tegra/
Dnvidia,tegra20-emc.txt12 irrespective of ram-code configuration.
43 Embedded Memory Controller configuration table
57 * The slightly more complex one is when more than one memory configuration
/linux-4.1.27/drivers/scsi/ufs/
DKconfig2 # Kernel configuration file for the UFS Host Controller
80 UFS host on QCOM needs some vendor specific configuration before
81 accessing the hardware which includes PHY configuration and vendor
/linux-4.1.27/scripts/kconfig/lxdialog/
DBIG.FAT.WARNING3 kernel configuration script. Please do not bother Savio Lam with
/linux-4.1.27/drivers/media/usb/siano/
DKconfig2 # Siano Mobile Silicon Digital TV device configuration
/linux-4.1.27/Documentation/devicetree/bindings/iommu/
Darm,smmu.txt48 SMMU configuration registers. In this case non-secure
50 SMMU configuration.
/linux-4.1.27/drivers/pnp/isapnp/
DKconfig2 # ISA Plug and Play configuration
/linux-4.1.27/drivers/net/ethernet/icplus/
DKconfig2 # IC Plus device configuration
/linux-4.1.27/drivers/amba/
DKconfig10 Adds AHB configuration functionality for NVIDIA Tegra SoCs,
/linux-4.1.27/arch/x86/boot/
Dmtools.conf.in2 # mtools configuration file for "make (b)zdisk"
/linux-4.1.27/drivers/vme/
DKconfig2 # VME configuration.
/linux-4.1.27/drivers/net/ethernet/octeon/
DKconfig2 # Cavium network device configuration
/linux-4.1.27/Documentation/devicetree/bindings/virtio/
Dmmio.txt8 - reg: control registers base address and size including configuration space
/linux-4.1.27/drivers/media/mmc/siano/
DKconfig2 # Siano Mobile Silicon Digital TV device configuration
/linux-4.1.27/drivers/hsi/
DKconfig2 # HSI driver configuration
/linux-4.1.27/drivers/misc/eeprom/
DKconfig88 bool "DigsyMTC display configuration EEPROMs device"
91 This option enables access to display configuration EEPROMs
94 EEPROM allowing to read/write the configuration data or to
/linux-4.1.27/drivers/usb/mon/
DKconfig2 # USB Monitor configuration
/linux-4.1.27/drivers/net/ethernet/renesas/
DKconfig2 # Renesas device configuration
/linux-4.1.27/arch/m32r/lib/
Ddelay.c111 #error unknown isa configuration in __const_udelay()
/linux-4.1.27/Documentation/misc-devices/mei/
Dmei.txt68 configuration, the driver by default allows only a privileged
163 2) Intel AMT Remote configuration using a Local Agent
167 configuration process may involve an ISV-developed remote configuration
175 An open source Intel AMT configuration utility, implementing a local agent
/linux-4.1.27/drivers/dma/hsu/
DKconfig1 # DMA engine configuration for hsu
/linux-4.1.27/drivers/staging/media/bcm2048/
DKconfig2 # Multimedia Video device configuration
/linux-4.1.27/Documentation/kbuild/
Dkconfig-language.txt4 The configuration database is a collection of configuration options
28 them. A single configuration option is defined like this:
134 used to help visually separate configuration logic from help within
144 looking for the default configuration (which is used when the main
252 The configuration file describes a series of menu entries, where every
307 configuration process and is also echoed to the output files. The only
334 This reads the specified configuration file. This file is always parsed.
341 to use it. It should be placed at the top of the configuration, before any
/linux-4.1.27/drivers/usb/core/
Dmessage.c1693 int usb_set_configuration(struct usb_device *dev, int configuration) in usb_set_configuration() argument
1701 if (dev->authorized == 0 || configuration == -1) in usb_set_configuration()
1702 configuration = 0; in usb_set_configuration()
1706 configuration) { in usb_set_configuration()
1712 if ((!cp && configuration != 0)) in usb_set_configuration()
1720 if (cp && configuration == 0) in usb_set_configuration()
1754 configuration, -i); in usb_set_configuration()
1838 configuration, alt->desc.bInterfaceNumber); in usb_set_configuration()
1844 USB_REQ_SET_CONFIGURATION, 0, configuration, 0, in usb_set_configuration()
1892 dev_name(&intf->dev), configuration, in usb_set_configuration()
/linux-4.1.27/drivers/pps/generators/
DKconfig2 # PPS generators configuration
/linux-4.1.27/Documentation/arm/SA1100/
DItsy21 configuration parameters in the monitor as follows:
35 setup is assembly outl's, and the kernel is a configuration item specific to
/linux-4.1.27/drivers/net/ethernet/wiznet/
DKconfig2 # WIZnet devices configuration
69 in runtime from board/platform resources configuration.
/linux-4.1.27/Documentation/devicetree/bindings/soc/qcom/
Dqcom,gsbi.txt5 configuration settings. The mode setting will govern the input/output mode of
14 - qcom,mode : indicates MUX value for configuration of the serial interface.
/linux-4.1.27/drivers/hwtracing/coresight/
DKconfig2 # Coresight configuration
28 Depending on its configuration the device can act as a link (embedded
/linux-4.1.27/Documentation/devicetree/bindings/fpga/
Daltera-socfpga-fpga-mgr.txt7 - The second index is for writing FPGA configuration data.
/linux-4.1.27/drivers/staging/unisys/
DKconfig2 # Unisys SPAR driver configuration
/linux-4.1.27/drivers/net/ethernet/brocade/bna/
DKconfig2 # QLogic BR-series network device configuration
/linux-4.1.27/drivers/thermal/samsung/
DKconfig8 This driver uses the Exynos core thermal APIs and TMU configuration
/linux-4.1.27/net/decnet/netfilter/
DKconfig2 # DECnet netfilter configuration
/linux-4.1.27/drivers/net/ethernet/tile/
DKconfig2 # Tilera network device configuration
/linux-4.1.27/virt/kvm/
DKconfig1 # KVM common configuration items and defaults
/linux-4.1.27/drivers/mmc/core/
DKconfig2 # MMC core configuration
/linux-4.1.27/drivers/staging/iio/gyro/
DKconfig2 # IIO Digital Gyroscope Sensor drivers configuration
/linux-4.1.27/fs/configfs/
DKconfig2 tristate "Userspace-driven configuration filesystem"
/linux-4.1.27/drivers/hsi/controllers/
DKconfig2 # HSI controllers configuration

123456