Home
last modified time | relevance | path

Searched refs:parameters (Results 1 – 200 of 664) sorted by relevance

1234

/linux-4.4.14/drivers/clk/
Dclk-xgene.c400 struct xgene_dev_parameters *parameters, spinlock_t *lock) in xgene_register_clk() argument
422 apmclk->param = *parameters; in xgene_register_clk()
447 struct xgene_dev_parameters parameters; in xgene_devclk_init() local
455 parameters.csr_reg = NULL; in xgene_devclk_init()
456 parameters.divider_reg = NULL; in xgene_devclk_init()
475 parameters.divider_reg = map_res; in xgene_devclk_init()
477 parameters.csr_reg = map_res; in xgene_devclk_init()
479 if (of_property_read_u32(np, "csr-offset", &parameters.reg_csr_offset)) in xgene_devclk_init()
480 parameters.reg_csr_offset = 0; in xgene_devclk_init()
481 if (of_property_read_u32(np, "csr-mask", &parameters.reg_csr_mask)) in xgene_devclk_init()
[all …]
/linux-4.4.14/Documentation/sound/oss/
Doss-parameters.txt4 See Documentation/kernel-parameters.txt for general information on
5 specifying module parameters.
8 "modinfo -p ${modulename}" shows a current list of all parameters of a loadable
10 reveal their parameters in /sys/module/${modulename}/parameters/. Some of these
11 parameters may be changed at runtime by the command
12 "echo -n ${value} > /sys/module/${modulename}/parameters/${parm}".
DAudioExcelDSP1618 setup. If the parameters are different, correct it.
23 Module parameters
25 To use this driver as a module, you must configure some module parameters, to
26 set up I/O addresses, IRQ lines and DMA channels. Some parameters are
27 mandatory while some others are optional. Here a list of parameters you can
78 you want, with the parameters of your audio card,
DSoundPro26 parameters for ad1848. Please let me know if it happens to you, so I can
49 Since in this latter case you cannot use module parameters, you will
76 to the ad1848 parameters, email me the syslog results and I'll do
DALS34 and "mpu401") using the module parameters. When configuring an ALS-007, be
47 passing appropriate values using the "io" and "irq" parameters.
/linux-4.4.14/Documentation/ia64/
Derr_inject.txt44 # err_type_info, err_struct_info: PAL parameters.
751 parameters_t parameters[MAX_TASK_NUM]={};
785 parameters[num].cpu=cpu;
786 parameters[num].loop=loop;
787 parameters[num].interval= interval>MIN_INTERVAL
789 parameters[num].err_type_info=err_type_info_conf;
790 parameters[num].err_struct_info=err_struct_info_conf;
791 memcpy(parameters[num++].err_data_buffer,
799 parameters[0].cpu=line_para.cpu;
800 parameters[0].loop=line_para.loop;
[all …]
/linux-4.4.14/Documentation/dmaengine/
Ddmatest.txt23 % echo dma0chan0 > /sys/module/dmatest/parameters/channel
24 % echo 2000 > /sys/module/dmatest/parameters/timeout
25 % echo 1 > /sys/module/dmatest/parameters/iterations
26 % echo 1 > /sys/module/dmatest/parameters/run
43 % cat /sys/module/dmatest/parameters/run
48 /sys/module/dmatest/parameters/wait waits for any running test to complete
58 % cat /sys/module/dmatest/parameters/wait
63 The module parameters that is supplied to the kernel command line will be used
65 re-run with the same or different parameters. For the details see the above
68 In both cases the module parameters are used as the actual values for the test
[all …]
Dclient.txt15 2. Set slave and controller specific parameters
48 2. Set slave and controller specific parameters
56 If some DMA controllers have more parameters to be sent then they
59 parameters, if required.
/linux-4.4.14/Documentation/isdn/
DREADME.audio32 where xx is a two-character code and v are alphanumerical parameters.
40 AT+VIP Reset all audio parameters.
52 AT+VSD=x,y Set silence-detection parameters.
53 Possible parameters:
58 AT+VSD=? Report possible parameters.
59 AT+VSD? Show current parameters.
61 AT+VDD=x,y Set DTMF-detection parameters.
63 Possible parameters:
69 AT+VDD=? Report possible parameters.
70 AT+VDD? Show current parameters.
[all …]
DINTERFACE.CAPI189 The Data and Data64 parameters are not used for processing. The Data64
199 accessible form. It contains members for all possible CAPI 2.0 parameters,
201 parameters, with the following exceptions:
212 Only those parameters appearing in the message type currently being processed
215 Members are named after the CAPI 2.0 standard names of the parameters they
219 u8 for CAPI parameters of type 'byte'
221 u16 for CAPI parameters of type 'word'
223 u32 for CAPI parameters of type 'dword'
225 _cstruct for CAPI parameters of type 'struct'
231 _cmstruct alternative representation for CAPI parameters of type 'struct'
[all …]
DINTERFACE.fax29 parameters and use ISDN_STAT_FAXIND.
45 Local faxmachine's parameters, set by +FDIS, +FDCS, +FLID, ...
56 Remote faxmachine's parameters. To be set by HL-driver.
DREADME.act200058 Defaults used, when no parameters given at all:
76 appending its parameters to the modprobe resp. insmod commandline.
81 where b, p, i and idstring have the same meanings as the parameters
/linux-4.4.14/Documentation/sound/alsa/
Dalsa-parameters.txt4 See Documentation/kernel-parameters.txt for general information on
5 specifying module parameters.
8 "modinfo -p ${modulename}" shows a current list of all parameters of a loadable
10 reveal their parameters in /sys/module/${modulename}/parameters/. Some of these
11 parameters may be changed at runtime by the command
12 "echo -n ${value} > /sys/module/${modulename}/parameters/${parm}".
Dpowersave.txt27 /sys/modules/snd_ac97_codec/parameters/power_save (usually as root):
29 # echo 10 > /sys/modules/snd_ac97_codec/parameters/power_save
/linux-4.4.14/Documentation/acpi/
Dmethod-tracing.txt22 /sys/module/acpi/parameters/debug_layer) and per-type level (known as
23 debug level, configured via /sys/module/acpi/parameters/debug_level).
36 # cd /sys/module/acpi/parameters
42 # cd /sys/module/acpi/parameters
46 # echo "method" > /sys/module/acpi/parameters/trace_state
49 # cd /sys/module/acpi/parameters
53 # echo "method-once" > /sys/module/acpi/parameters/trace_state
92 # cd /sys/module/acpi/parameters
98 # cd /sys/module/acpi/parameters
105 # cd /sys/module/acpi/parameters
[all …]
Ddebug.txt20 debug_layer and debug_level files in /sys/module/acpi/parameters/ to control
32 to /sys/module/acpi/parameters/debug_layer.
35 include/acpi/acpi_drivers.h. Reading /sys/module/acpi/parameters/debug_layer
80 to /sys/module/acpi/parameters/debug_level.
83 /sys/module/acpi/parameters/debug_level shows the supported mask values,
144 # echo 0x4 > /sys/module/acpi/parameters/debug_level
148 # cat /sys/module/acpi/parameters/debug_layer
/linux-4.4.14/Documentation/i2c/
Dold-module-parameters5 <linux/i2c.h> which created standard module parameters to let the user
7 parameters were known as "probe" (to let the driver probe for an extra
12 binding model, it became clear that these per-module parameters were no
17 Below is a mapping from the old module parameters to the new interface.
22 Old method (module parameters):
33 Old method (module parameters):
/linux-4.4.14/Documentation/scsi/
Dscsi-parameters.txt4 See Documentation/kernel-parameters.txt for general information on
5 specifying module parameters.
8 "modinfo -p ${modulename}" shows a current list of all parameters of a loadable
10 reveal their parameters in /sys/module/${modulename}/parameters/. Some of these
11 parameters may be changed at runtime by the command
12 "echo -n ${value} > /sys/module/${modulename}/parameters/${parm}".
113 st= [HW,SCSI] SCSI tape parameters (buffers, etc.)
Ddc395x.txt23 Both can be overridden by command line parameters (module or kernel
24 parameters).
26 The following parameters are available:
87 For the built in driver the parameters should be prefixed with
D53c700.txt68 parameters that matter to you (see below), plumb the NCR_700_intr
70 template and the new parameters as arguments. You should also call
72 address into the `base' pointer of the host parameters.
95 The following are a list of the user settable parameters:
Dg_NCR5380.txt39 When NCR53c400 support is compiled in, BIOS parameters will be returned by
44 When included as a module, parameters can be passed on the insmod/modprobe
Dtmscsim.txt40 module parameters (chapter 5) are ignored! However, you can change settings
77 The patches will update the kernel startup code to allow boot parameters to
197 You type the names of the parameters and the params following it.
218 select the device to which the following parameters apply. Note that it
255 5. Configuration via boot/module parameters
266 by using kernel or module parameters. See lilo(8) or modprobe(1) manual
269 settings of the DC390 with cmd line parameters. This has changed since
275 parameters is limited.
283 Each of the parameters is a number, containing the described information:
364 * Changing the parameters of multi-lun by the tmscsim/? interface will
Dst.txt11 to any specific tape drive. The tape parameters can be specified with
14 1. Each user can specify the tape parameters he/she wants to use
17 in a multiuser environment the next user finds the tape parameters in
21 parameters, like block size and density using the MTSETDRVBUFFER ioctl.
22 These parameters can be programmed to come into effect either when a
35 The user can override the parameters defined by the system
48 over some of the buffering parameters not directly accessible to the
51 parameters are reset when a new tape is loaded).
54 for the same set of parameters.
323 If the driver is compiled into the kernel, the same parameters can be
[all …]
D00-INDEX91 scsi-parameters.txt
92 - List of SCSI-parameters to pass to the kernel at module load-time.
Dsym53c8xx_2.txt30 9. Configuration parameters
299 echo "<verb> <parameters>" >/proc/scsi/sym53c8xx/0
396 9. Configuration parameters
399 possible to change some default driver configuration parameters.
406 Configuration parameters:
430 parameters to modprobe, as described in Documentation/kernel-parameters.txt
463 (See 'Configuration parameters')
534 0x02 ignore NVRAM "Synchronous negotiation" parameters for all devices
551 As a result of the new module parameters, this is no longer available.
689 serial NVRAM is used by Symbios and Tekram to hold set up parameters for the
[all …]
/linux-4.4.14/Documentation/fmc/
Dfmc-trivial.txt8 The module implements the generic FMC parameters, so it can program a
9 different gateware file in each card. The whole list of parameters it
14 Generic parameters. See mezzanine.txt
Dparameters.txt4 The core driver receives two module parameters, meant to help debugging
5 client modules. Both parameters can be modified by writing to
6 /sys/module/fmc/parameters/, because they are used when client drivers
D00-INDEX16 parameters.txt
17 - The module parameters
Dmezzanine.txt78 Most of the FMC drivers need the same set of kernel parameters. This
79 package includes support to implement common parameters by means of
82 The parameters are carrier-specific, in that they rely on the busid
88 This is the list of parameters that are common to several modules to
115 parameters to load different binaries to the cards, after looking up
122 Please note that not all sub-modules support all of those parameters.
/linux-4.4.14/drivers/acpi/acpica/
Dnsxfeval.c259 info->parameters = ACPI_ALLOCATE_ZEROED(((acpi_size) info-> in ACPI_EXPORT_SYMBOL()
262 if (!info->parameters) { in ACPI_EXPORT_SYMBOL()
274 parameters[i]); in ACPI_EXPORT_SYMBOL()
280 info->parameters[info->param_count] = NULL; in ACPI_EXPORT_SYMBOL()
325 info->parameters = ACPI_ALLOCATE_ZEROED(((acpi_size) in ACPI_EXPORT_SYMBOL()
330 if (!info->parameters) { in ACPI_EXPORT_SYMBOL()
341 &info->parameters[i]); in ACPI_EXPORT_SYMBOL()
347 info->parameters[info->param_count] = NULL; in ACPI_EXPORT_SYMBOL()
452 if (info->parameters) { in ACPI_EXPORT_SYMBOL()
456 acpi_ut_delete_internal_object_list(info->parameters); in ACPI_EXPORT_SYMBOL()
Dpsxface.c272 if (info->parameters) { in acpi_ps_update_parameter_list()
276 for (i = 0; info->parameters[i]; i++) { in acpi_ps_update_parameter_list()
281 parameters[i], in acpi_ps_update_parameter_list()
Dnseval.c146 if (info->parameters) { in acpi_ns_evaluate()
147 while (info->parameters[info->param_count]) { in acpi_ns_evaluate()
Dnsinit.c179 info.evaluate_info->parameters = NULL; in acpi_ns_initialize_devices()
572 info->parameters = NULL; in acpi_ns_init_one_device()
/linux-4.4.14/tools/testing/selftests/firmware/
Dfw_filesystem.sh21 OLD_FWPATH=$(cat /sys/module/firmware_class/parameters/path)
31 echo -n "$OLD_PATH" >/sys/module/firmware_class/parameters/path
44 echo -n "$FWPATH" >/sys/module/firmware_class/parameters/path
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-module15 /sys/module/MODULENAME/parameters
17 individual parameters of the module that are able to be
19 documentation as to the contents of these parameters and
26 stability of the different parameters.
/linux-4.4.14/Documentation/networking/
Dnetconsole.txt52 parameters for the multiple agents separated by semicolons and the
84 parameters reconfigured at runtime from a configfs-based userspace interface.
85 [ Note that the parameters of netconsole targets that were specified/created
102 "1" to the "enabled" attribute (usually after setting parameters accordingly)
109 The interface exposes these parameters of a netconsole target to userspace:
121 The "enabled" attribute is also used to control whether the parameters of
122 a target can be updated or not -- you can modify the parameters of only
125 To update a target's parameters:
131 echo cb:a9:87:65:43:21 > remote_mac # update more parameters
177 from the config parameters passed to netconsole.
[all …]
Ds2io.txt8 - 4. Command line parameters
61 4. Command line parameters
100 a. By default, the driver respects BIOS settings for PCI bus parameters.
101 However, you may want to experiment with PCI bus parameters
121 a. By default, the driver respects BIOS settings for PCI bus parameters.
134 recommended as safe parameters.
Dipv6.txt2 Options for the ipv6 module are supplied as parameters at load time.
9 The available ipv6 module parameters are listed below. If a parameter
12 The parameters are as follows:
Dray_cs.txt22 David Hinds pcmcia package. All the command line parameters are
25 This will change after the method of sorting out parameters for all
27 with nondefault parameters, they can be edited in
62 different parameters, contact the network administrator for the
64 Add the parameters below between the empty quotes.
Dz8530drv.txt38 2. Setup of hardware, MODEM and KISS parameters with sccinit
66 To setup all parameters you must run /sbin/sccinit from one
69 and sets the hardware, MODEM and KISS parameters. A sample file is
74 1.2.1 configuration of hardware parameters
77 The hardware setup section defines the following parameters for each
220 If you only know the parameters for the PE1CHL driver for DOS,
222 Its parameters are exactly the same as the ones you use with
282 sections IS important. The MODEM parameters are set with the first
286 (or insmod). You can change all parameters but "mode" and "clock"
311 ax25-utils and the AX.25-HOWTO to learn how to set the parameters of
[all …]
Dltpc.txt13 this reason, you should be prepared to supply these parameters
22 where the parameters (in order) are the port address, IRQ, and DMA
26 If you load the driver as a module, you can pass the parameters "io=",
110 this, either compile the driver as a module, or pass the parameters
Dnetlink_mmap.txt35 Ring setup is done using setsockopt() to provide the ring parameters to the
69 fixed size dependent on the parameters used for ring setup.
85 The ring parameters used for setting up the ring are defined as follows:
102 Some parameters are constrained, specifically:
221 /* Configure ring parameters */
239 This example assumes some ring parameters of the ring setup are available.
302 This example assumes some ring parameters of the ring setup are available.
Dmac80211-injection.txt15 Despite many radiotap parameters being currently defined, most only make sense
34 Here is an example valid radiotap header defining some parameters
Dvxge.txt9 3) Configurable driver parameters
67 3) Configurable driver parameters:
Dde4x5.txt157 appears in the list before its parameters. The list of parameters ends
159 following parameters are allowed:
163 sub-parameters:
166 Case sensitivity is important for the sub-parameters. They *must* be
DREADME.ipw220026 1.2. Module parameters
56 software driver are designed to carefully control parameters that affect
58 parameters include, without limitation, RF power, spectrum usage,
136 as module parameters. The most common way to specify a module parameter
156 matching the channel and network name parameters provided.
192 % iwpriv $IFNAME method parameters
241 parameters through this mechanism.
383 When configuring the mode of the adapter, all run-time configured parameters
Dcxacru.txt26 Write parameters in hexadecimal format <index>=<value>,
29 Up to 7 parameters at a time will be sent and the modem will restart
Dxfrm_sync.txt79 2) TLVS reflect the different parameters:
98 3) Default configurations for the parameters:
107 we also provide default threshold values for these different parameters
134 any of the values or threshold parameters can be updated by passing the
Dsmc9.txt26 optional parameters:
Ddl2k.txt116 Please reference the list of the command line parameters supported by
162 options dl2k <optional parameters>
166 previous section for the list of optional parameters.
179 parameter. Below is a list of the command line parameters supported by the
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dqcom,apq8064-pinctrl.txt12 second cell is used for optional parameters.
25 parameters, such as pull-up, drive strength, etc.
30 Each subnode only affects those parameters that are explicitly listed. In
32 parameters implies no information about any pin configuration parameters.
Dqcom,msm8660-pinctrl.txt12 second cell is used for optional parameters.
25 parameters, such as pull-up, drive strength, etc.
30 Each subnode only affects those parameters that are explicitly listed. In
32 parameters implies no information about any pin configuration parameters.
Dqcom,ipq8064-pinctrl.txt12 second cell is used for optional parameters.
25 parameters, such as pull-up, drive strength, etc.
30 Each subnode only affects those parameters that are explicitly listed. In
32 parameters implies no information about any pin configuration parameters.
Dqcom,msm8974-pinctrl.txt12 second cell is used for optional parameters.
25 parameters, such as pull-up, drive strength, etc.
30 Each subnode only affects those parameters that are explicitly listed. In
32 parameters implies no information about any pin configuration parameters.
Dlantiq,pinctrl-falcon.txt15 mux function to select on those group(s), and two pin configuration parameters:
21 Each subnode only affects those parameters that are explicitly listed. In
23 parameters implies no information about any pin configuration parameters.
Dpinctrl-palmas.txt19 those pin(s), and various pin configuration parameters, such as pull-up,
25 Each subnode only affects those parameters that are explicitly listed. In
27 parameters implies no information about any pin configuration parameters.
Dlantiq,pinctrl-xway.txt15 mux function to select on those group(s), and two pin configuration parameters:
21 Each subnode only affects those parameters that are explicitly listed. In
23 parameters implies no information about any pin configuration parameters.
Dimg,tz1090-pdc-pinctrl.txt16 parameters, such as pull-up, drive strength, etc.
21 Each subnode only affects those parameters that are explicitly listed. In
23 parameters implies no information about any pin configuration parameters.
Dnvidia,tegra124-xusb-padctl.txt34 Each subnode describes groups of lanes along with parameters and pads that
38 Each subnode only applies the parameters that are explicitly listed. In other
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
Dqcom,msm8960-pinctrl.txt54 parameters, such as pull-up, drive strength, etc.
62 Each subnode only affects those parameters that are explicitly listed. In
64 parameters implies no information about any pin configuration parameters.
Dqcom,apq8084-pinctrl.txt54 parameters, such as pull-up, drive strength, etc.
62 Each subnode only affects those parameters that are explicitly listed. In
64 parameters implies no information about any pin configuration parameters.
Dqcom,msm8916-pinctrl.txt54 parameters, such as pull-up, drive strength, etc.
62 Each subnode only affects those parameters that are explicitly listed. In
64 parameters implies no information about any pin configuration parameters.
Dqcom,pmic-mpp.txt54 parameters, as listed below.
61 Each subnode only affects those parameters that are explicitly listed. In
63 parameters implies no information about any pin configuration parameters.
Dqcom,pmic-gpio.txt53 parameters, as listed below.
61 Each subnode only affects those parameters that are explicitly listed. In
63 parameters implies no information about any pin configuration parameters.
Drenesas,pfc-pinctrl.txt44 function to select on those pin(s) and pin configuration parameters (such as
48 or grouped in child subnodes. Both pin muxing and configuration parameters can
73 The pin configuration parameters use the generic pinconf bindings defined in
74 pinctrl-bindings.txt in this directory. The supported parameters are
Dpinctrl-vt8500.txt14 second cell is used to specify optional parameters.
25 configuration. Each subnode only affects those parameters that are explicitly
Dnvidia,tegra20-pinmux.txt16 parameters, such as pull-up, tristate, drive strength, etc.
21 Each subnode only affects those parameters that are explicitly listed. In
23 parameters implies no information about any pin configuration parameters.
Dnvidia,tegra210-pinmux.txt17 parameters, such as pull-up, tristate, drive strength, etc.
22 Each subnode only affects those parameters that are explicitly listed. In
24 parameters implies no information about any pin configuration parameters.
Dbrcm,bcm2835-gpio.txt11 second cell is used to specify optional parameters:
34 configuration. Each subnode only affects those parameters that are explicitly
Dimg,tz1090-pinctrl.txt16 parameters, such as pull-up, drive strength, etc.
21 Each subnode only affects those parameters that are explicitly listed. In
23 parameters implies no information about any pin configuration parameters.
/linux-4.4.14/Documentation/device-mapper/
Ddm-flakey.txt16 Table parameters
21 Mandatory parameters:
28 Optional feature parameters:
29 If no feature parameters are present, during the periods of
Ddm-crypt.txt7 For a more detailed description of supported parameters see:
49 Number of optional parameters. If there are no optional parameters,
53 Example of optional parameters section:
Dverity.txt67 Number of optional parameters. If there are no optional parameters,
71 Example of optional parameters section:
135 Alternatively, the header can be omitted and the dmsetup parameters can
143 The full specification of kernel parameters and on-disk metadata format
Ddelay.txt10 With separate write parameters, the first set is only used for reads.
Ddm-raid.txt11 The target is named "raid" and it accepts the following parameters:
42 <#raid_params>: The number of parameters that follow.
45 Mandatory parameters:
50 followed by optional parameters (in any order):
151 The optional parameters are always printed in the order listed
Ddm-queue-length.txt8 Table parameters for each path: [<repeat_count>]
/linux-4.4.14/Documentation/hwmon/
Dmax665050 Module parameters
54 simply load your module without parameters. It won't touch the configuration
56 different settings, you can set the following parameters:
63 understand the meaning of these parameters before you attempt to change them.
Dwm835018 monitor a range of system operating parameters, including the voltages
Damc682192 Module parameters
99 different settings, you can set the following parameters:
Dwm831x18 monitor a range of system operating parameters, including the voltages
/linux-4.4.14/samples/pktgen/
DREADME.rst11 by shell source'ing. Namely "functions.sh" and "parameters.sh".
13 Common parameters
15 The parameters.sh file support easy and consistant parameter parsing
Dpktgen_sample01_simple.sh14 source ${basedir}/parameters.sh
Dpktgen_bench_xmit_mode_netif_receive.sh34 source ${basedir}/parameters.sh
Dpktgen_sample03_burst_single_flow.sh26 source ${basedir}/parameters.sh
Dpktgen_sample02_multiqueue.sh14 source ${basedir}/parameters.sh
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-class-net-grcan12 /sys/module/grcan/parameters/enable0.
24 /sys/module/grcan/parameters/enable1.
35 /sys/module/grcan/parameters/select.
Dsysfs-driver-xen-blkback1 What: /sys/module/xen_blkback/parameters/max_buffer_pages
9 What: /sys/module/xen_blkback/parameters/max_persistent_grants
Dconfigfs-usb-gadget-ffs9 All parameters are set through FunctionFS.
Dsysfs-driver-xen-blkfront1 What: /sys/module/xen_blkfront/parameters/max
Dsysfs-kernel-boot_params6 It is used to export the kernel boot parameters of an x86
Dsysfs-class-led26 scheduler is chosen. Trigger specific parameters can appear in
/linux-4.4.14/arch/arm/boot/dts/
Dorion5x-rd88f5182-nas.dts50 /* Read parameters */
57 /* Write parameters */
72 /* Read parameters */
79 /* Write parameters */
Darmada-xp-openblocks-ax3-4.dts75 /* Device Bus parameters are required */
77 /* Read parameters */
86 /* Write parameters */
Darmada-xp-db.dts85 /* Device Bus parameters are required */
87 /* Read parameters */
96 /* Write parameters */
Dorion5x-lacie-ethernet-disk-mini-v2.dts70 /* Read parameters */
77 /* Write parameters */
Darmada-xp-gp.dts104 /* Device Bus parameters are required */
106 /* Read parameters */
115 /* Write parameters */
/linux-4.4.14/drivers/block/drbd/
DKconfig51 /sys/module/drbd/parameters/
69 echo 16 > /sys/module/drbd/parameters/enable_faults
70 echo 1 > /sys/module/drbd/parameters/fault_devs
71 echo 5 > /sys/module/drbd/parameters/fault_rate
/linux-4.4.14/Documentation/input/
Diforce-protocol.txt86 08-09 Address of periodicity or magnitude parameters
87 0a-0b Address of attack and fade parameters, or ffff if none.
89 08-09 Address of interactive parameters for X-axis, or ffff if not applicable
90 0a-0b Address of interactive parameters for Y-axis, or ffff if not applicable
95 ** Time based parameters **
100 00-01 Address where to store the parameters
121 ** Interactive parameters **
227 Each device has a certain amount of memory to store parameters of effects.
229 is the amount of memory apparently needed for every set of parameters:
Dntrig.txt10 and utility functions accessible with sysfs and module parameters.
20 devices. Adjusting parameters with sysfs will override the load time values,
23 The following parameters are used to configure filters to reduce noise:
59 to logical sizes is used to adjust the size based filter parameters.
102 set to 0 for both parameters, effectively turning off that filter.
105 don't work for you, please play with the parameters. If you do find other
Dbcm5974.txt49 echo -n 9 > /sys/module/bcm5974/parameters/debug
53 echo -n 0 > /sys/module/bcm5974/parameters/debug
/linux-4.4.14/crypto/asymmetric_keys/
Dmscode.asn115 parameters ANY
27 parameters ANY OPTIONAL
Dpkcs7.asn137 parameters ANY OPTIONAL
120 parameters ANY OPTIONAL
Dx509.asn125 parameters ANY OPTIONAL
/linux-4.4.14/Documentation/usb/
Dmass-storage.txt27 * Module parameters
30 module parameters:
139 parameters defined by the composite framework (they are common to
177 Other then those, as usual, the values of module parameters can be
178 read from /sys/module/g_mass_storage/parameters/* files.
188 module parameters may be missing, or the parameters may have
211 1. In FSG the “removable” and “cdrom” module parameters set the flag
218 parameters are handled in MSG by the composite layer's parameters
223 “protocol” and “buflen” FSG's module parameters are not
Diuu_phoenix.txt24 A few parameters can be used at load time
25 To use parameters, just unload the module if it is
34 The parameters are:
/linux-4.4.14/Documentation/video4linux/cx2341x/
Dfw-calling.txt35 1 I Driver has finished setting the parameters.
45 There are 16 parameters/results 32-bit fields. The driver populates these fields
46 with values for all the parameters required by the call. The driver overwrites
56 in the command enumerator, the timeout value and any required parameters. The
/linux-4.4.14/Documentation/fb/
Dtridentfb.txt17 of parameters below).
32 The parameters for tridentfb are concatenated with a ':' as in this example.
36 The second level parameters that tridentfb understands are:
66 Using insane values for the above parameters will probably result in driver
Dintelfb.txt79 The binary parameters can be unset with a "no" prefix, example "noaccel".
110 The module parameters are essentially similar to the kernel
111 parameters. The main difference is that you need to include a Boolean value
Dintel810.txt43 calculate required video mode parameters.
195 vsync1 and vsync2 parameters. These parameters will be taken from the EDID
200 The module parameters are essentially similar to the kernel
201 parameters. The main difference is that you need to include a Boolean value
Defifb.txt20 You have to add the following kernel parameters in your elilo.conf:
/linux-4.4.14/Documentation/devicetree/bindings/display/panel/
Ddisplay-timing.txt19 - hfront-porch, hback-porch, hsync-len: horizontal display timing parameters
21 vfront-porch, vback-porch, vsync-len: vertical display timing parameters in
49 The parameters are defined as:
/linux-4.4.14/drivers/virtio/
DKconfig76 or module parameters. Be aware that using incorrect parameters (base
78 See Documentation/kernel-parameters.txt for details.
/linux-4.4.14/Documentation/video4linux/
Dsi476x.txt19 useful for EoL testing/RF performance estimation, parameters that have
20 very little to do with V4L2 subsystem. Such parameters are exposed via
82 This file contains information about parameters pertaining to
110 This file contains information about parameters pertaining to
185 This file contains information about parameters pertaining to
Dmeye.txt84 for accessing the Motion Eye extended parameters (camera sharpness,
92 Get and set the extended parameters of the motion eye camera.
93 The user should always query the current parameters with
96 parameters are described by the meye_params structure.
/linux-4.4.14/Documentation/devicetree/bindings/lpddr2/
Dlpddr2-timings.txt1 * AC timing parameters of LPDDR2(JESD209-2) memories for a given speed-bin
10 The following properties represent AC timing parameters from the memory
Dlpddr2.txt20 timing parameters of the DDR device in terms of number of clock cycles.
36 "lpddr2-timings" provides AC timing parameters of the device for
/linux-4.4.14/Documentation/arm/
DSetup1 Kernel initialisation parameters on ARM Linux
8 This structure is used to pass initialisation parameters from the
13 There are a lot of parameters listed in there, and they are described
129 Kernel command line parameters. Details can be found elsewhere.
D00-INDEX18 - Kernel initialization parameters on ARM Linux
/linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/
Dmvebu-devbus.txt29 using the timing parameters set by the
35 Read parameters:
83 Write parameters:
138 /* Device Bus parameters are required */
140 /* Read parameters */
149 /* Write parameters */
Dingenic,jz4780-nemc.txt39 for all optional parameters will be configured for all banks. If any optional
40 parameters are omitted, they will be left unchanged from whatever they are
/linux-4.4.14/drivers/char/
Dnwbutton.c26 static void button_sequence_finished (unsigned long parameters);
130 static void button_sequence_finished (unsigned long parameters) in button_sequence_finished() argument
Dnwbutton.h27 static void button_sequence_finished (unsigned long parameters);
/linux-4.4.14/Documentation/devicetree/bindings/thermal/
Dst-thermal.txt3 Required parameters:
22 Optional parameters:
/linux-4.4.14/Documentation/leds/
Dleds-class.txt19 parameters and work on a per LED basis. The timer trigger is an example.
29 parameters can appear in /sys/class/leds/<device> once a given trigger is
69 if it is called with *delay_on==0 && *delay_off==0 parameters. In this
71 delay_off parameters to the leds subsystem.
/linux-4.4.14/net/atm/
Dmpoa_caches.c120 entry->retry_time = client->parameters.mpc_p4; in in_cache_add_entry()
142 if (entry->count > mpc->parameters.mpc_p1) { in cache_hit()
161 if (entry->count > mpc->parameters.mpc_p1 && in cache_hit()
265 client->parameters.mpc_p6) { in check_resolving_entries()
276 if (entry->retry_time > client->parameters.mpc_p5) { in check_resolving_entries()
278 entry->retry_time = client->parameters.mpc_p4; in check_resolving_entries()
Dmpc.h33 struct mpc_parameters parameters; /* parameters for this client */ member
Dmpc.c292 mpc->parameters.mpc_p1 = MPC_P1; in alloc_mpc()
293 mpc->parameters.mpc_p2 = MPC_P2; in alloc_mpc()
294 memset(mpc->parameters.mpc_p3, 0, sizeof(mpc->parameters.mpc_p3)); in alloc_mpc()
295 mpc->parameters.mpc_p4 = MPC_P4; in alloc_mpc()
296 mpc->parameters.mpc_p5 = MPC_P5; in alloc_mpc()
297 mpc->parameters.mpc_p6 = MPC_P6; in alloc_mpc()
964 mpc->parameters = mesg->content.params; in msg_from_mpoad()
1429 mpc->parameters.mpc_p4 * HZ) { in mpc_cache_check()
1434 mpc->parameters.mpc_p5 * HZ) { in mpc_cache_check()
/linux-4.4.14/Documentation/devicetree/bindings/
Dxilinx.txt10 Each IP-core has a set of parameters which the FPGA designer can use to
12 extract the device parameters relevant to device drivers and copy them
17 The new approach is to export the parameters into the device tree and
19 parameters which used to be exported as #defines will now become
40 (parameter#): C_* parameters from system.mhs. The C_ prefix is
81 interrupts = <1 0>; // got this from the opb_intc parameters
128 // If this device had extra parameters, then they would
/linux-4.4.14/drivers/usb/misc/sisusbvga/
DKconfig30 the first and last consoles (starting at 1) as driver parameters.
41 If the driver is compiled into the kernel image, the parameters
/linux-4.4.14/fs/jbd2/
DKconfig32 with "echo N > /sys/module/jbd2/parameters/jbd2_debug", where N is a
35 "echo 0 > /sys/module/jbd2/parameters/jbd2_debug".
/linux-4.4.14/Documentation/
Dramoops.txt46 2. Setting the parameters
48 Setting the ramoops parameters can be done in 2 different manners:
49 1. Use the module parameters (which have the names of the variables described
57 2. Use a platform device and set the platform data. The parameters can then
DSubmitChecklist69 17: All new kernel boot parameters are documented in
70 Documentation/kernel-parameters.txt.
72 18: All new module parameters are documented with MODULE_PARM_DESC()
Dbad_memory.txt34 Syntax to exclude a memory area (see kernel-parameters.txt for details):
/linux-4.4.14/drivers/net/wireless/mwifiex/
DREADME56 bssid and the security related parameters can be specified while joining/creating
63 The command will be used to get the connection status. The command will return parameters
173 where the parameters are,
190 where the parameters are,
199 different configuration parameters.
205 where the parameters are,
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dtwl6040.txt29 - vibra { }: Configuration section for vibra parameters containing the following
58 /* Vibra driver, motor resistance parameters */
/linux-4.4.14/Documentation/watchdog/
Dwdt.txt24 pass IO address and IRQ boot parameters. E.g.:
27 Other "wdt" driver parameters are:
/linux-4.4.14/drivers/amba/
DKconfig12 parameters (priority, prefetch size).
/linux-4.4.14/Documentation/devicetree/bindings/rng/
Dst,rng.txt4 Required parameters:
/linux-4.4.14/drivers/auxdisplay/
DKconfig56 using the module parameters.
71 value using the module parameters.
120 value using the module parameters.
/linux-4.4.14/Documentation/arm/OMAP/
Domap_pm11 Drivers need to express PM parameters which:
13 - support the range of power management parameters present in the TI SRF;
19 - specify PM parameters in terms of fundamental units, such as
96 The PM parameters can be overwritten by calling the function again
/linux-4.4.14/drivers/staging/goldfish/
DREADME8 - Remove excess checking of parameters in calls
/linux-4.4.14/Documentation/arm/SA1100/
DItsy21 configuration parameters in the monitor as follows:
34 not easily. The monitor parameters are easily changed, the params program
/linux-4.4.14/arch/cris/arch-v32/mach-fs/
Ddram_init.S21 ;; WARNING! The registers r8 and r9 are used as parameters carrying
64 ; Set timing parameters (refresh off to avoid Guinness TR 83)
/linux-4.4.14/net/irda/
DMakefile13 discovery.o parameters.o irnetlink.o irmod.o
Dirttp.c1189 int parameters; in irttp_connect_confirm() local
1222 parameters = skb->data[0] & 0x80; in irttp_connect_confirm()
1227 if (parameters) { in irttp_connect_confirm()
1273 int parameters; in irttp_connect_indication() local
1299 parameters = skb->data[0] & 0x80; in irttp_connect_indication()
1304 if (parameters) { in irttp_connect_indication()
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dpl061-gpio.txt6 second cell is used to specify optional parameters:
Dgpio-zevio.txt7 second cell is used to specify optional parameters (currently unused).
Dfujitsu,mb86s70-gpio.txt10 second cell is used to specify optional parameters:
Dzx296702-gpio.txt6 second cell is used to specify optional parameters:
Dgpio_atmel.txt8 the second cell is used to specify optional parameters (currently
Dgpio_lpc32xx.txt16 3) optional parameters:
Dgpio-sx150x.txt17 second cell is used to specify optional parameters:
Dgpio-nmk.txt9 The second cell is used to specify optional parameters:
Dgpio-adnp.txt9 second cell is used to specify optional parameters:
Dgpio-zynq.txt8 parameters (unused)
Dnvidia,tegra20-gpio.txt10 second cell is used to specify optional parameters:
Dgpio-mm-lantiq.txt14 the second cell is used to specify optional parameters (currently
Dgpio-ath79.txt11 second cell is used to specify optional parameters.
Dabilis,tb10x-gpio.txt8 second cell is used to specify optional parameters:
Dgpio-twl4030.txt8 - second cell is used to specify optional parameters (unused)
Dgpio-omap.txt11 - second cell is used to specify optional parameters (unused)
Dgpio-davinci.txt13 - second cell is used to specify optional parameters (unused)
/linux-4.4.14/Documentation/infiniband/
Dipoib.txt68 use ethtool to set interrupt mitigation parameters and thus reduce
77 turned on by setting the module parameters debug_level and
78 mcast_debug_level to 1. These parameters can be controlled at
/linux-4.4.14/Documentation/x86/x86_64/
D00-INDEX12 - Configurable sysfs parameters for the x86-64 machine check code.
/linux-4.4.14/Documentation/devicetree/bindings/serial/
Darm_sbsa_uart.txt3 in the PL011 driver. It's baudrate and other communication parameters
Dnxp,lpc1850-uart.txt18 parameters from 8250.txt also apply but are optional.
/linux-4.4.14/Documentation/block/
Dnull_blk.txt23 II. Module parameters applicable for all instances:
66 III: Multi-queue specific parameters
/linux-4.4.14/tools/testing/selftests/rcutorture/doc/
DTINY_RCU.txt11 combinations of these parameters.
/linux-4.4.14/tools/testing/selftests/pstore/
Dcommon_tests77 backend=`cat /sys/module/pstore/parameters/backend`
/linux-4.4.14/Documentation/ioctl/
Dioctl-decoding.txt8 31-30 00 - no parameters: uses _IO macro
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dalc5632.txt14 second cell is used to specify optional parameters (currently unused).
Dwm8903.txt14 second cell is used to specify optional parameters (currently unused).
/linux-4.4.14/Documentation/i2c/busses/
Di2c-diolan-u2c23 Module parameters
Di2c-parport-light13 Module parameters:
/linux-4.4.14/arch/cris/arch-v10/lib/
Ddram_init.S18 ;; WARNING! The registers r8 and r9 are used as parameters carrying
83 ; Set timing parameters. Starts master clock
/linux-4.4.14/Documentation/scheduler/
Dsched-deadline.txt46 SCHED_DEADLINE uses three parameters, named "runtime", "period", and
71 "deadline", and "period" parameters;
74 a "remaining runtime". These two parameters are initially set to 0;
159 multiple real-time tasks, the parameters of the i-th task are indicated
269 SCHED_DEADLINE scheduling parameters described in Section 2 (runtime,
270 deadline and period) and the real-time task parameters (WCET, D, P)
364 desired bandwidth. In other words, this means that interface parameters are
367 parameters, so that CPU bandwidth is allocated to SCHED_DEADLINE tasks
483 start multiple threads with specific parameters. rt-app supports
485 parameters (e.g., niceness, priority, runtime/deadline/period). rt-app
[all …]
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DNAND.txt12 code, so the driver enforces its own OOB layout and ECC parameters
/linux-4.4.14/drivers/firmware/
Ddcdbas.h101 } __attribute__ ((packed)) parameters; member
/linux-4.4.14/Documentation/s390/
D00-INDEX10 - common I/O layer command line parameters, procfs and debugfs entries
DDASD12 parameters are to be given in hexadecimal notation without a leading
14 If you supply kernel parameters the different instances are processed
/linux-4.4.14/drivers/net/wireless/libertas/
DREADME50 to stdout. The length and offset parameters allow dumping cer-
84 card. These commands take two parameters that specify the offset
85 location and the value that is to be written. This parameters must
230 Note: Host sleep parameters should be configured using
/linux-4.4.14/arch/arm/mach-omap2/
Dsleep34xx.S104 adr r3, api_params @ r3 points to parameters
441 add r3, r3, r0 @ r3 points to dummy parameters
457 ldr r3, [r4, #0xBC] @ r3 points to parameters
472 adds r3, r3, #8 @ r3 points to parameters
/linux-4.4.14/Documentation/serial/
Dserial-rs485.txt29 parameters in the platform data and in ioctls.
31 The device tree can also provide RS485 boot time parameters (see [2]
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dnvidia,tegra124-dfll.txt37 Required properties for the control loop parameters:
45 Optional properties for the control loop parameters:
Dti,cdce925.txt22 spectrum clocking parameters for a board.
Dhi6220-clock.txt28 the driver need use the sram to pass parameters for frequency change.
/linux-4.4.14/Documentation/devicetree/bindings/power_supply/
Dlp8727_charger.txt12 AC and USB charging parameters
/linux-4.4.14/sound/usb/line6/
DKconfig12 * Reading/writing individual parameters
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dnand.txt19 The interpretation of these parameters is implementation-defined, so not all
/linux-4.4.14/Documentation/netlabel/
Ddraft-ietf-cipso-ipsecurity-01.txt430 The configuration parameters defined below are required for all CIPSO hosts,
447 parameters are required for CIPSO implementations:
454 PORT_LABEL_MAX parameters for the associated interfaces.
472 parameters for the associated interfaces.
507 This list represents the minimal set of configuration parameters required
516 The labels represented by the PORT_LABEL_MAX and PORT_LABEL_MIN parameters
518 want to have the range parameters expressed in CIPSO format so that incoming
532 systems then multiple port range parameters would be needed, one set for
544 support the parameters described above. These limited implementations are
574 and HOST configuration parameters defined in section 3.
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/display/msm/
Dgpu.txt19 - NOTE: downstream android driver defines additional parameters to
/linux-4.4.14/Documentation/devicetree/bindings/pwm/
Dpwm-st.txt4 Required parameters:
/linux-4.4.14/Documentation/devicetree/bindings/hwmon/
Dg762.txt23 Additional information on operational parameters for the device is available
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dsunxi-mmc.txt20 - for cd, bus-width and additional generic mmc parameters
/linux-4.4.14/Documentation/blockdev/
Dnbd.txt23 A) NBD parameters
/linux-4.4.14/Documentation/vm/
Dzswap.txt35 echo 1 > /sys/module/zswap/parameters/enabled
61 echo zbud > /sys/module/zswap/parameters/zpool
93 echo lzo > /sys/module/zswap/parameters/compressor
/linux-4.4.14/Documentation/mips/
DAU1xxx_IDE.README49 timing parameters for PIO mode 0/1/2/3/4
50 timing parameters for MWDMA 0/1/2
/linux-4.4.14/Documentation/filesystems/nfs/
Dnfsroot.txt42 This can be established using the following kernel command line parameters:
187 kernel command line parameters, including `nfsroot=', are ignored.
246 When using LILO all the necessary command line parameters may be
259 specification: kernel <kernel> <parameters>
284 "kernel <relative-path-below /tftpboot>". The nfsroot parameters
/linux-4.4.14/drivers/lightnvm/
DKconfig25 /sys/module/lnvm/parameters/configure_debug
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/
Dgpio.txt14 second cell is used to specify optional parameters (currently unused).

1234