/Linux-v5.15/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 …]
|
/Linux-v5.15/drivers/clk/ |
D | clk-xgene.c | 626 struct xgene_dev_parameters *parameters, spinlock_t *lock) in xgene_register_clk() argument 646 apmclk->param = *parameters; in xgene_register_clk() 671 struct xgene_dev_parameters parameters; in xgene_devclk_init() local 679 parameters.csr_reg = NULL; in xgene_devclk_init() 680 parameters.divider_reg = NULL; in xgene_devclk_init() 697 parameters.divider_reg = map_res; in xgene_devclk_init() 699 parameters.csr_reg = map_res; in xgene_devclk_init() 701 if (of_property_read_u32(np, "csr-offset", ¶meters.reg_csr_offset)) in xgene_devclk_init() 702 parameters.reg_csr_offset = 0; in xgene_devclk_init() 703 if (of_property_read_u32(np, "csr-mask", ¶meters.reg_csr_mask)) in xgene_devclk_init() [all …]
|
/Linux-v5.15/drivers/mtd/nand/raw/ |
D | nand_macronix.c | 43 if (!chip->parameters.supports_set_get_features || in macronix_nand_setup_read_retry() 45 chip->parameters.set_feature_list)) in macronix_nand_setup_read_retry() 93 struct nand_parameters *p = &chip->parameters; in macronix_nand_onfi_init() 168 if (!chip->parameters.supports_set_get_features) in macronix_nand_fix_broken_get_timings() 172 chip->parameters.model); in macronix_nand_fix_broken_get_timings() 176 bitmap_clear(chip->parameters.get_feature_list, in macronix_nand_fix_broken_get_timings() 178 bitmap_clear(chip->parameters.set_feature_list, in macronix_nand_fix_broken_get_timings() 225 bitmap_set(chip->parameters.get_feature_list, in macronix_nand_block_protection_support() 237 bitmap_clear(chip->parameters.get_feature_list, in macronix_nand_block_protection_support() 242 bitmap_set(chip->parameters.set_feature_list, in macronix_nand_block_protection_support() [all …]
|
D | nand_onfi.c | 239 chip->parameters.model = kstrdup(p->model, GFP_KERNEL); in nand_onfi_detect() 240 if (!chip->parameters.model) { in nand_onfi_detect() 300 chip->parameters.supports_set_get_features = true; in nand_onfi_detect() 301 bitmap_set(chip->parameters.get_feature_list, in nand_onfi_detect() 303 bitmap_set(chip->parameters.set_feature_list, in nand_onfi_detect() 324 chip->parameters.onfi = onfi; in nand_onfi_detect() 332 kfree(chip->parameters.model); in nand_onfi_detect()
|
/Linux-v5.15/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 …]
|
/Linux-v5.15/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:
|
/Linux-v5.15/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 | 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.
|
/Linux-v5.15/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 …]
|
/Linux-v5.15/Documentation/scsi/ |
D | scsi-parameters.rst | 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}``. 104 st= [HW,SCSI] SCSI tape parameters (buffers, etc.)
|
/Linux-v5.15/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 | 22 debug_layer and debug_level files in /sys/module/acpi/parameters/ to control 34 to /sys/module/acpi/parameters/debug_layer. 38 Reading /sys/module/acpi/parameters/debug_layer shows the supported mask values:: 68 to /sys/module/acpi/parameters/debug_level. 71 /sys/module/acpi/parameters/debug_level shows the supported mask values, 128 # echo 0x4 > /sys/module/acpi/parameters/debug_level 132 # cat /sys/module/acpi/parameters/debug_layer
|
/Linux-v5.15/drivers/scsi/smartpqi/ |
D | smartpqi_sas_transport.c | 462 struct bmic_csmi_smp_passthru *parameters; in pqi_build_csmi_smp_passthru_buffer() local 479 put_unaligned_le32(sizeof(smp_buf->parameters), &ioctl_header->length); in pqi_build_csmi_smp_passthru_buffer() 481 parameters = &smp_buf->parameters; in pqi_build_csmi_smp_passthru_buffer() 482 parameters->phy_identifier = rphy->identify.phy_identifier; in pqi_build_csmi_smp_passthru_buffer() 483 parameters->port_identifier = 0; in pqi_build_csmi_smp_passthru_buffer() 484 parameters->connection_rate = 0; in pqi_build_csmi_smp_passthru_buffer() 486 ¶meters->destination_sas_address); in pqi_build_csmi_smp_passthru_buffer() 491 put_unaligned_le32(req_size, ¶meters->request_length); in pqi_build_csmi_smp_passthru_buffer() 492 put_unaligned_le32(resp_size, ¶meters->response_length); in pqi_build_csmi_smp_passthru_buffer() 495 job->reply_payload.sg_cnt, ¶meters->request, in pqi_build_csmi_smp_passthru_buffer() [all …]
|
/Linux-v5.15/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 implemented 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 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, 86 "modinfo -p ${modulename}" shows a current list of all parameters of a loadable 88 reveal their parameters in /sys/module/${modulename}/parameters/. Some of these 89 parameters may be changed at runtime by the command [all …]
|
/Linux-v5.15/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 24 Below is a mapping from the old module parameters to the new interface. 29 Old method (module parameters):: 42 Old method (module parameters)::
|
/Linux-v5.15/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, 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 | netdevsim.rst | 13 .. list-table:: Generic parameters implemented 21 parameters. 23 .. list-table:: Driver-specific parameters implemented 70 Rate nodes and it's parameters are exposed in ``netdevsim`` debugfs in RO mode. 78 Same parameters are exposed for leaf objects in corresponding ports directories.
|
/Linux-v5.15/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
|
/Linux-v5.15/drivers/acpi/acpica/ |
D | nsxfeval.c | 247 info->parameters = ACPI_ALLOCATE_ZEROED(((acpi_size)info-> in ACPI_EXPORT_SYMBOL() 250 if (!info->parameters) { in ACPI_EXPORT_SYMBOL() 262 parameters[i]); in ACPI_EXPORT_SYMBOL() 268 info->parameters[info->param_count] = NULL; in ACPI_EXPORT_SYMBOL() 312 info->parameters = ACPI_ALLOCATE_ZEROED(((acpi_size) in ACPI_EXPORT_SYMBOL() 317 if (!info->parameters) { in ACPI_EXPORT_SYMBOL() 328 &info->parameters[i]); in ACPI_EXPORT_SYMBOL() 334 info->parameters[info->param_count] = NULL; in ACPI_EXPORT_SYMBOL() 439 if (info->parameters) { in ACPI_EXPORT_SYMBOL() 443 acpi_ut_delete_internal_object_list(info->parameters); in ACPI_EXPORT_SYMBOL()
|
/Linux-v5.15/fs/pstore/ |
D | Kconfig | 213 NOTE that, both Kconfig and module parameters can configure 214 pstore/blk, but module parameters have priority over Kconfig. 224 NOTE that, both Kconfig and module parameters can configure 225 pstore/blk, but module parameters have priority over Kconfig. 236 NOTE that, both Kconfig and module parameters can configure 237 pstore/blk, but module parameters have priority over Kconfig. 248 NOTE that, both Kconfig and module parameters can configure 249 pstore/blk, but module parameters have priority over Kconfig. 260 NOTE that, both Kconfig and module parameters can configure 261 pstore/blk, but module parameters have priority over Kconfig. [all …]
|
/Linux-v5.15/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.
|
/Linux-v5.15/Documentation/networking/ |
D | netconsole.rst | 61 parameters for the multiple agents separated by semicolons and the 98 parameters reconfigured at runtime from a configfs-based userspace interface. 99 [ Note that the parameters of netconsole targets that were specified/created 116 "1" to the "enabled" attribute (usually after setting parameters accordingly) 123 The interface exposes these parameters of a netconsole target to userspace: 137 The "enabled" attribute is also used to control whether the parameters of 138 a target can be updated or not -- you can modify the parameters of only 141 To update a target's parameters:: 147 echo cb:a9:87:65:43:21 > remote_mac # update more parameters 197 from the config parameters passed to netconsole. [all …]
|