Home
last modified time | relevance | path

Searched full:parameters (Results 1 – 25 of 694) sorted by relevance

12345678910>>...28

/Documentation/driver-api/dmaengine/
Ddmatest.rst38 % echo 2000 > /sys/module/dmatest/parameters/timeout
39 % echo 1 > /sys/module/dmatest/parameters/iterations
40 % echo dma0chan0 > /sys/module/dmatest/parameters/channel
41 % echo 1 > /sys/module/dmatest/parameters/run
50 % echo 2000 > /sys/module/dmatest/parameters/timeout
51 % echo 1 > /sys/module/dmatest/parameters/iterations
52 % echo dma0chan0 > /sys/module/dmatest/parameters/channel
53 % echo dma0chan1 > /sys/module/dmatest/parameters/channel
54 % echo dma0chan2 > /sys/module/dmatest/parameters/channel
55 % echo 1 > /sys/module/dmatest/parameters/run
[all …]
/Documentation/sound/designs/
Dtracepoints.rst13 and for processing of PCM hardware parameters. These tracepoints are available
24 Tracepoints for processing of PCM hardware parameters
33 substream. In this procedure, PCM hardware parameters are decided by
35 the PCM substream keeps the parameters.
37 The parameters are described in :c:type:`struct snd_pcm_hw_params`. This
38 structure includes several types of parameters. Applications set preferable
39 value to these parameters, then execute ioctl(2) with SNDRV_PCM_IOCTL_HW_REFINE
41 set of parameters. The latter is used for an actual decision of the parameters.
47 convenient parameters or change their behaviour.
77 SNDRV_PCM_IOCTL_HW_PARAMS, this mask is ignored and all of parameters
[all …]
/Documentation/admin-guide/
Dkernel-parameters.rst3 The kernel's command-line parameters
6 The following is a consolidated list of the kernel parameters as
12 The kernel parses parameters from the kernel command line up to "``--``";
14 parameter gets passed to init: parameters with '=' go into init's
18 Module parameters can be specified in two ways: via the kernel command
24 Parameters for modules which are built into the kernel need to be
26 kernel command line (/proc/cmdline) and collects module parameters
45 Some kernel parameters take a list of CPUs as a value, e.g. isolcpus,
74 "modinfo -p ${modulename}" shows a current list of all parameters of a loadable
76 reveal their parameters in /sys/module/${modulename}/parameters/. Some of these
[all …]
/Documentation/media/uapi/dvb/
Ddvb-frontend-parameters.rst13 frontend parameters
16 The kind of parameters passed to the frontend device for tuning depend
20 per-system parameters. However, as newer delivery systems required more
22 size would break the existing applications. So, those parameters were
25 ioctl's. The new API is flexible enough to add new parameters to
33 All kinds of parameters are combined as a union in the
61 QPSK parameters
78 QAM parameters
95 VSB parameters
110 OFDM parameters
Dfrontend-property-satellite-systems.rst22 The following parameters are valid for DVB-S:
47 Future implementations might add those two missing parameters:
59 In addition to all parameters valid for DVB-S, DVB-S2 supports the
60 following parameters:
81 In addition to all parameters valid for DVB-S, turbo code supports the
82 following parameters:
92 The following parameters are valid for ISDB-S:
/Documentation/scsi/
Dscsi-parameters.txt1 SCSI Kernel Parameters
4 See Documentation/admin-guide/kernel-parameters.rst 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}".
103 st= [HW,SCSI] SCSI tape parameters (buffers, etc.)
/Documentation/firmware-guide/acpi/
Dmethod-tracing.rst30 /sys/module/acpi/parameters/debug_layer) and per-type level (known as
31 debug level, configured via /sys/module/acpi/parameters/debug_level).
46 # cd /sys/module/acpi/parameters
54 # cd /sys/module/acpi/parameters
58 # echo "method" > /sys/module/acpi/parameters/trace_state
63 # cd /sys/module/acpi/parameters
67 # echo "method-once" > /sys/module/acpi/parameters/trace_state
112 # cd /sys/module/acpi/parameters
120 # cd /sys/module/acpi/parameters
129 # cd /sys/module/acpi/parameters
[all …]
Ddebug.rst23 debug_layer and debug_level files in /sys/module/acpi/parameters/ to control
35 to /sys/module/acpi/parameters/debug_layer.
38 include/acpi/acpi_drivers.h. Reading /sys/module/acpi/parameters/debug_layer
83 to /sys/module/acpi/parameters/debug_level.
86 /sys/module/acpi/parameters/debug_level shows the supported mask values,
147 # echo 0x4 > /sys/module/acpi/parameters/debug_level
151 # cat /sys/module/acpi/parameters/debug_layer
/Documentation/ABI/testing/
Dsysfs-driver-ufs19 device descriptor parameters. The full information about
27 device descriptor parameters. The full information about
35 the UFS device descriptor parameters. The full information
43 This is one of the UFS device descriptor parameters.
52 the UFS device descriptor parameters. The full information
60 This is one of the UFS device descriptor parameters.
70 parameters. The full information about the descriptor could
80 parameters. The full information about the descriptor could
89 the UFS device descriptor parameters. The full information
97 the UFS device descriptor parameters. The full information
[all …]
Dsysfs-driver-xen-blkback1 What: /sys/module/xen_blkback/parameters/max_buffer_pages
9 What: /sys/module/xen_blkback/parameters/max_persistent_grants
19 What: /sys/module/xen_blkback/parameters/persistent_grant_unused_seconds
/Documentation/virt/kvm/devices/
Dvm.txt16 Parameters: none
22 Parameters: none
30 Parameters: in attr->addr the address for the new limit of guest memory
59 Parameters: address of buffer to store the machine related cpu data
82 Parameters: address of buffer to store/set the processor related cpu
99 Parameters: address of a buffer to load the feature list from.
110 Parameters: address of a buffer to store/load the feature list from.
148 Parameters: address of a buffer to load the subfunction blocks from.
169 Parameters: address of a buffer to store/load the subfunction blocks from.
183 Parameters: address of a buffer in user space to store the data (u8) to
[all …]
/Documentation/ia64/
Derr_inject.rst44 # 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 …]
/Documentation/i2c/
Dold-module-parameters.rst6 <linux/i2c.h> which created standard module parameters to let the user
8 parameters were known as "probe" (to let the driver probe for an extra
13 binding model, it became clear that these per-module parameters were no
18 Below is a mapping from the old module parameters to the new interface.
23 Old method (module parameters)::
36 Old method (module parameters)::
/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.
/Documentation/media/uapi/v4l/
Dpixfmt-meta-intel-ipu3.rst48 The struct :c:type:`ipu3_uapi_4a_config` saves all configurable parameters.
66 Pipeline parameters
69 The pipeline parameters are passed to the "ipu3-imgu [01] parameters" metadata
73 Both 3A statistics and pipeline parameters described here are closely tied to
85 /* Accelerator cluster parameters */
88 /* ISP vector address space parameters */
93 /* ISP data memory (DMEM) parameters */
Dvidioc-g-fmt.rst50 To query the current parameters applications set the ``type`` field of a
63 To change the current format parameters applications initialize the
66 :ref:`devices`. Good practice is to query the current parameters
67 first, and to modify only those parameters not suitable for the
70 checks and adjusts the parameters against hardware abilities. Drivers
73 parameters acceptable for both the application and driver. On success
76 the current format parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Very simple,
78 default parameters. However all V4L2 devices exchanging data with the
88 parameters, to learn about hardware limitations, without disabling I/O
129 - Raw VBI capture or output parameters. This is discussed in more
[all …]
Dstreaming-par.rst13 Streaming Parameters
16 Streaming parameters are intended to optimize the video capture process
32 To get and set the streaming parameters applications call the
36 contains a union holding separate parameters for input and output
Ddev-output.rst57 The output is determined by cropping and image format parameters. The
63 As usual these parameters are *not* reset at :ref:`open() <func-open>`
68 Cropping initialization at minimum requires to reset the parameters to
80 To request different parameters applications set the ``type`` field of a
86 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
99 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
Ddev-capture.rst60 format parameters. The former select an area of the video picture to
65 As usual these parameters are *not* reset at :ref:`open() <func-open>`
70 Cropping initialization at minimum requires to reset the parameters to
83 To request different parameters applications set the ``type`` field of a
89 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
102 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
Dvidioc-g-crop.rst69 image parameters. :ref:`VIDIOC_S_CROP <VIDIOC_G_CROP>` is a write-only ioctl, it does not
70 return the actual parameters. To query them applications must call
72 parameters are unsuitable the application may modify the cropping or
73 image parameters and repeat the cycle until satisfactory parameters have
76 When cropping is not supported then no parameters are changed and
/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 …]
Ddevlink-params.txt1 Devlink configuration parameters
3 Following is the list of configuration parameters via devlink interface.
5 parameters.
17 Following is the list of parameters:
/Documentation/virt/kvm/
Dapi.txt107 Parameters: what parameters are accepted by the ioctl.
118 Parameters: none
134 Parameters: machine type identifier (KVM_VM_*)
186 Parameters: struct kvm_msr_list (in/out)
221 Parameters: extension identifier (KVM_CAP_*)
239 Parameters: none
252 Parameters: struct kvm_memory_region (in)
263 Parameters: vcpu id (apic id on x86)
309 Parameters: struct kvm_dirty_log (in/out)
341 Parameters: struct kvm_memory_alias (in)
[all …]
/Documentation/admin-guide/device-mapper/
Ddm-flakey.rst17 Table parameters
25 Mandatory parameters:
37 Optional feature parameters:
39 If no feature parameters are present, during the periods of
/Documentation/virtual/
Dguest-halt-polling.txt26 Module Parameters
29 The haltpoll governor has 5 tunable module parameters:
69 The module parameters can be set from the debugfs files in:
71 /sys/module/haltpoll/parameters/

12345678910>>...28