| /Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 38 % 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/ |
| D | tracepoints.rst | 13 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 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/ |
| D | kernel-parameters.rst | 3 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/userspace-api/media/dvb/ |
| D | dvb-frontend-parameters.rst | 6 frontend parameters
9 The kind of parameters passed to the frontend device for tuning depend
13 per-system parameters. However, as newer delivery systems required more
15 size would break the existing applications. So, those parameters were
18 ioctl's. The new API is flexible enough to add new parameters to
26 All kinds of parameters are combined as a union in the
54 QPSK parameters
71 QAM parameters
88 VSB parameters
103 OFDM parameters
|
| D | frontend-property-satellite-systems.rst | 15 The following parameters are valid for DVB-S:
40 Future implementations might add those two missing parameters:
52 In addition to all parameters valid for DVB-S, DVB-S2 supports the
53 following parameters:
74 In addition to all parameters valid for DVB-S, turbo code supports the
75 following parameters:
85 The following parameters are valid for ISDB-S:
|
| /Documentation/networking/devlink/ |
| D | devlink-params.rst | 7 ``devlink`` provides capability for a driver to expose device parameters for low
12 This document describes a number of generic parameters that are supported
14 parameters. Each driver must document the specific parameters they support,
20 Parameters may be set in different configuration modes.
40 In order for ``driverinit`` parameters to take effect, the driver must
46 Generic configuration parameters
48 The following is a list of generic configuration parameters that drivers may
49 add. Use of generic parameters is preferred over each driver creating their
52 .. list-table:: List of generic parameters
|
| D | mlx4.rst | 10 Parameters chapter
13 .. list-table:: Generic parameters implemented
25 parameters.
27 .. list-table:: Driver-specific parameters implemented
|
| D | qed.rst | 10 Parameters subtitle
13 The ``qed`` driver implements the following driver-specific parameters.
15 .. list-table:: Driver-specific parameters implemented
|
| D | mlx5.rst | 10 Parameters chapter
13 .. list-table:: Generic parameters implemented
21 parameters.
23 .. list-table:: Driver-specific parameters implemented
|
| D | bnxt.rst | 10 Parameters chapter
13 .. list-table:: Generic parameters implemented
27 parameters.
29 .. list-table:: Driver-specific parameters implemented
|
| D | ti-cpsw-switch.rst | 10 Parameters subtitle
14 parameters.
16 .. list-table:: Driver-specific parameters implemented
|
| D | mv88e6xxx.rst | 10 Parameters subtitle
13 The ``mv88e6xxx`` driver implements the following driver-specific parameters.
15 .. list-table:: Driver-specific parameters implemented
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-meta-intel-ipu3.rst | 25 The struct :c:type:`ipu3_uapi_4a_config` saves all configurable parameters.
43 Pipeline parameters
46 The pipeline parameters are passed to the "ipu3-imgu [01] parameters" metadata
50 Both 3A statistics and pipeline parameters described here are closely tied to
62 /* Accelerator cluster parameters */
65 /* ISP vector address space parameters */
70 /* ISP data memory (DMEM) parameters */
|
| D | vidioc-g-fmt.rst | 45 To query the current parameters applications set the ``type`` field of a
58 To change the current format parameters applications initialize the
61 :ref:`devices`. Good practice is to query the current parameters
62 first, and to modify only those parameters not suitable for the
65 checks and adjusts the parameters against hardware abilities. Drivers
68 parameters acceptable for both the application and driver. On success
71 the current format parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Very simple,
73 default parameters. However all V4L2 devices exchanging data with the
83 parameters, to learn about hardware limitations, without disabling I/O
118 - Raw VBI capture or output parameters. This is discussed in more
[all …]
|
| D | streaming-par.rst | 7 Streaming Parameters
10 Streaming parameters are intended to optimize the video capture process
26 To get and set the streaming parameters applications call the
30 contains a union holding separate parameters for input and output
|
| D | dev-output.rst | 48 The output is determined by cropping and image format parameters. The
54 As usual these parameters are *not* reset at :c:func:`open()`
59 Cropping initialization at minimum requires to reset the parameters to
71 To request different parameters applications set the ``type`` field of a
77 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
90 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
|
| D | dev-capture.rst | 51 format parameters. The former select an area of the video picture to
56 As usual these parameters are *not* reset at :c:func:`open()`
61 Cropping initialization at minimum requires to reset the parameters to
74 To request different parameters applications set the ``type`` field of a
80 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
93 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
|
| /Documentation/scsi/ |
| D | scsi-parameters.rst | 4 SCSI Kernel Parameters
7 See Documentation/admin-guide/kernel-parameters.rst for general information on
8 specifying module parameters.
11 ``modinfo -p ${modulename}`` shows a current list of all parameters of a loadable
13 reveal their parameters in /sys/module/${modulename}/parameters/. Some of these
14 parameters may be changed at runtime by the command
15 ``echo -n ${value} > /sys/module/${modulename}/parameters/${parm}``.
107 st= [HW,SCSI] SCSI tape parameters (buffers, etc.)
|
| /Documentation/firmware-guide/acpi/ |
| D | method-tracing.rst | 30 /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 …]
|
| D | debug.rst | 23 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/ |
| D | sysfs-driver-xen-blkback | 1 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
29 What: /sys/module/xen_blkback/parameters/buffer_squeeze_duration_ms
39 What: /sys/module/xen_blkback/parameters/feature_persistent
|
| /Documentation/ia64/ |
| D | err_inject.rst | 44 # 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/ |
| D | old-module-parameters.rst | 11 <linux/i2c.h> which created standard module parameters to let the user
13 parameters were known as ``probe`` (to let the driver probe for an extra
18 binding model, it became clear that these per-module parameters were no
23 Below is a mapping from the old module parameters to the new interface.
28 Old method (module parameters)::
41 Old method (module parameters)::
|
| /Documentation/virt/kvm/devices/ |
| D | vm.rst | 23 :Parameters: none
31 :Parameters: none
41 :Parameters: in attr->addr the address for the new limit of guest memory
73 :Parameters: address of buffer to store the machine related cpu data
97 :Parameters: address of buffer to store/set the processor related cpu
119 :Parameters: address of a buffer to load the feature list from.
132 :Parameters: address of a buffer to store/load the feature list from.
175 :Parameters: address of a buffer to load the subfunction blocks from.
198 :Parameters: address of a buffer to store/load the subfunction blocks from.
215 :Parameters: address of a buffer in user space to store the data (u8) to
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-module | 15 /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.
|