| /openbmc/linux/Documentation/isdn/ |
| H A D | interface_capi.rst | 201 The Data and Data64 parameters are not used for processing. The Data64
212 accessible form. It contains members for all possible CAPI 2.0 parameters,
214 parameters, with the following exceptions:
225 Only those parameters appearing in the message type currently being processed
228 Members are named after the CAPI 2.0 standard names of the parameters they
233 u8 for CAPI parameters of type 'byte'
235 u16 for CAPI parameters of type 'word'
237 u32 for CAPI parameters of type 'dword'
239 _cstruct for CAPI parameters of type 'struct'
245 _cmstruct alternative representation for CAPI parameters of type 'struct'
[all …]
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | si476x.rst | 25 useful for EoL testing/RF performance estimation, parameters that have
26 very little to do with V4L2 subsystem. Such parameters are exposed via
81 This file contains information about parameters pertaining to
106 This file contains information about parameters pertaining to
158 This file contains information about parameters pertaining to
|
| /openbmc/linux/scripts/kconfig/tests/preprocess/variable/ |
| H A D | Kconfig | 48 # If some arguments are optional, it is useful to pass fewer parameters.
52 # Unreferenced parameters are just ignored.
|
| /openbmc/linux/Documentation/userspace-api/media/dvb/ |
| H A D | dmx-set-pes-filter.rst | 29 Pointer to structure containing filter parameters.
34 This ioctl call sets up a PES filter according to the parameters
|
| /openbmc/openbmc/poky/meta/recipes-extended/hdparm/ |
| H A D | hdparm_9.65.bb | 1 SUMMARY = "Utility for viewing/manipulating IDE disk drive/driver parameters"
4 and manipulating various IDE drive and driver parameters."
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/ |
| H A D | NewDump.interface.yaml | 14 Create a dump entry based on the parameters.
15 parameters:
|
| /openbmc/linux/Documentation/driver-api/firmware/ |
| H A D | fw_search_path.rst | 23 * /sys/module/firmware_class/parameters/path
29 echo -n /path/to/script > /sys/module/firmware_class/parameters/path
|
| /openbmc/linux/Documentation/arch/arm/ |
| H A D | setup.rst | 2 Kernel initialisation parameters on ARM Linux
9 This structure is used to pass initialisation parameters from the
14 There are a lot of parameters listed in there, and they are described
108 Kernel command line parameters. Details can be found elsewhere.
|
| /openbmc/linux/Documentation/devicetree/bindings/memory-controllers/ |
| H A D | mvebu-devbus.txt | 29 using the timing parameters set by the
35 Read parameters:
83 Write parameters:
137 /* Device Bus parameters are required */
139 /* Read parameters */
148 /* Write parameters */
|
| /openbmc/linux/Documentation/devicetree/bindings/ |
| H A D | xilinx.txt | 10 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
|
| /openbmc/linux/Documentation/input/devices/ |
| H A D | ntrig.rst | 14 and utility functions accessible with sysfs and module parameters.
24 devices. Adjusting parameters with sysfs will override the load time values,
27 The following parameters are used to configure filters to reduce noise:
70 to logical sizes is used to adjust the size based filter parameters.
113 set to 0 for both parameters, effectively turning off that filter.
116 don't work for you, please play with the parameters. If you do find other
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-g-fbuf.rst | 13 VIDIOC_G_FBUF - VIDIOC_S_FBUF - Get or set frame buffer overlay parameters
39 to get and set the framebuffer parameters for a
55 To get the current parameters applications call the :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>`
60 To set the parameters for a *Video Output Overlay*, applications must
63 implemented on the TV card all other parameters are determined by the
66 framebuffer parameters as :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>` does, or it returns an error
69 To set the parameters for a *Video Capture Overlay*
72 the overlay and returns the framebuffer parameters as :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>`
328 negotiate the parameters for a destructive overlay.
331 The :ref:`VIDIOC_S_FBUF <VIDIOC_G_FBUF>` parameters are unsuitable.
|
| /openbmc/linux/samples/pktgen/ |
| H A D | README.rst | 11 by shell source'ing. Namely "functions.sh" and "parameters.sh".
13 Common parameters
15 The parameters.sh file support easy and consistant parameter parsing
|
| /openbmc/openbmc-test-automation/extended/ |
| H A D | obmc_boot_test_resource.robot | 12 # Initialize program parameters variables.
13 # Create parm_list containing all of our program parameters. This is used by
52 # The reason boot_pass and boot_fail are parameters is that it is possible to
|
| /openbmc/linux/drivers/usb/dwc3/ |
| H A D | debug.h | 284 event->parameters, in dwc3_ep_event_string()
292 event->parameters, in dwc3_ep_event_string()
320 event->parameters); in dwc3_ep_event_string()
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Telemetry/ |
| H A D | ReportManager.interface.yaml | 12 parameters:
51 Array of metric parameters, which are stored in a way specified
63 /xyz/openbmc_project/Telemetry/Reports/{parameters[Id]}.
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | ti,da850-pupd.txt | 20 The pin configuration parameters use the generic pinconf bindings defined in
21 pinctrl-bindings.txt in this directory. The supported parameters are
|
| H A D | pinctrl-palmas.txt | 19 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.
|
| /openbmc/linux/Documentation/translations/zh_CN/admin-guide/mm/damon/ |
| H A D | reclaim.rst | 48 适当的值写入 ``/sys/module/damon_reclaim/parameters/<parameter>`` 文件。
217 # cd /sys/module/damon_reclaim/parameters
|
| H A D | lru_sort.rst | 51 参数，或者在 ``/sys/modules/damon_lru_sort/parameters/<parameter>`` 写入正确的
255 # cd /sys/modules/damon_lru_sort/parameters
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/BIOSConfig/ |
| H A D | README.md | 6 parameters remotely via BMC at any Host state. Modifications to the parameters
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ |
| H A D | IPMI.interface.yaml | 22 parameters:
56 parameters:
98 parameters:
127 parameters:
|
| /openbmc/linux/drivers/net/wireless/marvell/mwifiex/ |
| H A D | README | 57 bssid and the security related parameters can be specified while joining/creating
64 The command will be used to get the connection status. The command will return parameters
174 where the parameters are,
195 where the parameters are,
214 where the parameters are,
223 different configuration parameters.
229 where the parameters are,
266 different configuration parameters.
|
| /openbmc/linux/Documentation/admin-guide/mm/damon/ |
| H A D | lru_sort.rst | 42 Its default parameters for hotness/coldness thresholds and CPU quota limit are
43 conservatively chosen. That is, the module under its default parameters could
55 DAMON_LRU_SORT utilizes module parameters. That is, you can put
57 proper values to ``/sys/module/damon_lru_sort/parameters/<parameter>`` files.
74 Make DAMON_LRU_SORT reads the input parameters again, except ``enabled``.
76 Input parameters that updated while DAMON_LRU_SORT is running are not applied
79 parameter is set as ``N``. If invalid parameters are found while the
286 # cd /sys/module/damon_lru_sort/parameters
|
| /openbmc/u-boot/doc/device-tree-bindings/memory-controllers/ |
| H A D | st,stm32-fmc.txt | 9 - st,sdram-control : parameters for sdram configuration, in this order:
28 parameters as MACROS.
|