Searched full:parameters (Results 1 – 25 of 5966) sorted by relevance
12345678910>>...239
| /kernel/linux/linux-5.10/drivers/hid/ |
| D | hid-uclogic-params.c | 110 * uclogic_params_pen (tablet interface's pen input parameters). 113 * @pen: Pen input parameters to cleanup. Cannot be NULL. 123 * input and retrieve its parameters from the device, using v1 protocol. 125 * @pen: Pointer to the pen parameters to initialize (to be 127 * case of error, or if parameters are not found. Cannot be NULL. 128 * @pfound: Location for a flag which is set to true if the parameters 132 * parameters from. Cannot be NULL. 148 /* Pen report descriptor template parameters */ in uclogic_params_pen_init_v1() 159 * Read string descriptor containing pen input parameters. in uclogic_params_pen_init_v1() 167 "string descriptor with pen parameters not found, assuming not compatible\n"); in uclogic_params_pen_init_v1() [all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/drivers/scsi/qedi/ |
| D | qedi_fw_iscsi.h | 36 * @param task_params - Pointer to task parameters struct 37 * @param conn_params - Connection Parameters 38 * @param cmd_params - command specific parameters 39 * @param cmd_pdu_header - PDU Header Parameters 41 * @param dif_task_params - Pointer to DIF parameters struct 54 * @param task_params - Pointer to task parameters struct 55 * @param login_req_pdu_header - PDU Header Parameters 67 * @param task_params - Pointer to task parameters struct 68 * @param nop_out_pdu_header - PDU Header Parameters 80 * @param task_params - Pointer to task parameters struct [all …]
|
| /kernel/linux/linux-5.10/drivers/scsi/qedi/ |
| D | qedi_fw_iscsi.h | 33 * @param task_params - Pointer to task parameters struct 34 * @param conn_params - Connection Parameters 35 * @param cmd_params - command specific parameters 36 * @param cmd_pdu_header - PDU Header Parameters 38 * @param dif_task_params - Pointer to DIF parameters struct 51 * @param task_params - Pointer to task parameters struct 52 * @param login_req_pdu_header - PDU Header Parameters 64 * @param task_params - Pointer to task parameters struct 65 * @param nop_out_pdu_header - PDU Header Parameters 77 * @param task_params - Pointer to task parameters struct [all …]
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/isp/kernels/xnr/xnr_3.0/ |
| D | ia_css_xnr3_types.h | 20 * CSS-API header file for Extra Noise Reduction (XNR) parameters. 24 * \brief Scale of the XNR sigma parameters. 30 * \brief Scale of the XNR coring parameters. 42 * \brief XNR3 Sigma Parameters. 43 * \details Sigma parameters define the strength of the XNR filter. 46 * sigma parameters are fixed-point values between 0.0 and 1.0, scaled with 59 * \brief XNR3 Coring Parameters 60 * \details Coring parameters define the "coring" strength, which is a soft 63 * All coring parameters are fixed-point values between 0.0 and 1.0, scaled 74 * \brief XNR3 Blending Parameters [all …]
|
| /kernel/linux/linux-4.19/include/xen/interface/ |
| D | event_channel.h | 28 /* IN parameters */ 30 /* OUT parameters */ 45 /* IN parameters. */ 48 /* OUT parameters. */ 62 /* IN parameters. */ 65 /* OUT parameters. */ 77 /* IN parameters. */ 81 /* OUT parameters. */ 94 /* OUT parameters. */ 105 /* IN parameters. */ [all …]
|
| /kernel/linux/linux-5.10/include/xen/interface/ |
| D | event_channel.h | 28 /* IN parameters */ 30 /* OUT parameters */ 45 /* IN parameters. */ 48 /* OUT parameters. */ 62 /* IN parameters. */ 65 /* OUT parameters. */ 77 /* IN parameters. */ 81 /* OUT parameters. */ 94 /* OUT parameters. */ 105 /* IN parameters. */ [all …]
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/isp/kernels/hdr/ |
| D | ia_css_hdr_types.h | 24 * \brief HDR Irradiance Parameters 25 * \detail Currently HDR parameters are used only for testing purposes 45 * \brief HDR Deghosting Parameters 46 * \detail Currently HDR parameters are used only for testing purposes 53 * \brief HDR Exclusion Parameters 54 * \detail Currently HDR parameters are used only for testing purposes 62 * \details Struct with all parameters for HDR that can be seet from 63 * the CSS API. Currenly, only test parameters are defined. 66 struct ia_css_hdr_irradiance_params irradiance; /** HDR irradiance parameters */ 67 struct ia_css_hdr_deghost_params deghost; /** HDR deghosting parameters */ [all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/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 :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 …]
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 19 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 …]
|
| /kernel/linux/linux-4.19/Documentation/ia64/ |
| D | err_inject.txt | 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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/Documentation/acpi/ |
| D | method-tracing.txt | 22 /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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/Documentation/virtual/kvm/devices/ |
| D | vm.txt | 16 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. 147 Parameters: address of a buffer to load the subfunction blocks from. 168 Parameters: address of a buffer to store/load the subfunction blocks from. 182 Parameters: address of a buffer in user space to store the data (u8) to [all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 19 device descriptor parameters. The full information about 28 device descriptor parameters. The full information about 37 the UFS device descriptor parameters. The full information 46 This is one of the UFS device descriptor parameters. 56 the UFS device descriptor parameters. The full information 65 This is one of the UFS device descriptor parameters. 76 parameters. The full information about the descriptor could 87 parameters. The full information about the descriptor could 97 the UFS device descriptor parameters. The full information 106 the UFS device descriptor parameters. The full information [all …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/fs/pstore/ |
| D | Kconfig | 217 NOTE that, both Kconfig and module parameters can configure 218 pstore/blk, but module parameters have priority over Kconfig. 228 NOTE that, both Kconfig and module parameters can configure 229 pstore/blk, but module parameters have priority over Kconfig. 240 NOTE that, both Kconfig and module parameters can configure 241 pstore/blk, but module parameters have priority over Kconfig. 252 NOTE that, both Kconfig and module parameters can configure 253 pstore/blk, but module parameters have priority over Kconfig. 264 NOTE that, both Kconfig and module parameters can configure 265 pstore/blk, but module parameters have priority over Kconfig. [all …]
|
| /kernel/linux/linux-5.10/drivers/media/platform/omap3isp/ |
| D | isppreview.h | 59 * @busy: Bitmask of busy parameters (being updated or used) 60 * @update: Bitmask of the parameters to be updated 68 * @wbal: White Balance parameters. 69 * @blkadj: Black adjustment parameters. 70 * @rgb2rgb: RGB blending parameters. 71 * @csc: Color space conversion (RGB to YCbCr) parameters. 73 * @yclimit: YC limits parameters. 112 * @params.params : Active and shadow parameters sets 113 * @params.active: Bitmask of parameters active in set 0 114 * @params.lock: Parameters lock, protects params.active and params.shadow
|
| /kernel/linux/linux-4.19/Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 34 % echo dma0chan0 > /sys/module/dmatest/parameters/channel 35 % echo 2000 > /sys/module/dmatest/parameters/timeout 36 % echo 1 > /sys/module/dmatest/parameters/iterations 37 % echo 1 > /sys/module/dmatest/parameters/run 56 % cat /sys/module/dmatest/parameters/run 61 /sys/module/dmatest/parameters/wait waits for any running test to complete 74 % cat /sys/module/dmatest/parameters/wait 80 The module parameters that is supplied to the kernel command line will be used 82 re-run with the same or different parameters. For the details see the above 85 In both cases the module parameters are used as the actual values for the test [all …]
|
12345678910>>...239