| /linux/drivers/gpu/drm/i915/display/ |
| H A D | intel_dp_link_caps.c | 29 * DisplayPort link configurations for a DP encoder and its attached
31 * configurations and constrain them by filtering, disabling, or
49 * Iterating and restricting link configurations
53 * configurations`` during modeset configuration selection or link
61 * The configurations exposed via the iterators can be additionally
68 * usable configurations.
77 * configurations at or below the failed parameters.
81 * disabled configurations, as described above.
90 * ``Supported configurations`` are all configurations defined by the
93 * ``Disabled configurations`` are ``Supported configurations`` disabled
[all …]
|
| /linux/Documentation/trace/coresight/ |
| H A D | coresight-config.rst | 14 programming of the CoreSight system with pre-defined configurations that
20 be defined and enabled as named configurations.
73 Configurations section in Basic Concepts
133 Viewing Configurations and Features
136 The set of configurations and features that are currently loaded into the
148 configurations features
153 $ cd configurations/
209 Using Configurations in perf
212 The configurations loaded into the CoreSight configuration management are
240 When configurations are selected in this way, then the trace sink used is
[all …]
|
| /linux/Documentation/driver-api/cxl/platform/ |
| H A D | example-configs.rst | 3 Example Platform Configurations
10 example-configurations/one-dev-per-hb.rst
11 example-configurations/multi-dev-per-hb.rst
12 example-configurations/hb-interleave.rst
13 example-configurations/flexible.rst
|
| /linux/Documentation/usb/ |
| H A D | gadget_configfs.rst | 18 A gadget is seen by its host as a set of configurations, each of which contains
24 Creating a gadget means deciding what configurations there will be
103 2. Creating the configurations
106 Each gadget will consist of a number of configurations, their corresponding
155 4. Associating the functions with their configurations
159 configurations specified and a number of functions available. What remains
161 function can be used in multiple configurations). This is achieved with
178 configurations and functions.
236 Remove functions from configurations::
249 Remove strings directories in configurations::
[all …]
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | snps,dwc-qos-ethernet.txt | 10 configurations.
29 In some configurations (e.g. GMII/RGMII), this clock also drives the PHY TX
30 path. In other configurations, other clocks (such as tx_125, rmii) may
34 In some configurations (e.g. GMII/RGMII), this clock is derived from the
35 PHY's RX clock output. In other configurations, other clocks (such as
47 The master bus interface clock. Only required in configurations that use a
59 Note: Support for additional IP configurations may require adding the
62 Configurations exist where multiple similar clocks are used at once, e.g. all
67 This will allow easy support for configurations that support multiple PHY
|
| /linux/Documentation/networking/pse-pd/ |
| H A D | pse-pi.rst | 29 transmission. Unlike the configurations detailed in the PSE PI for standard
41 Ethernet cables. It details two main configurations for power delivery, known
58 1G/2G/5G/10GBaseT network. Alternative B includes two configurations with
65 The following table outlines the pin configurations for both Alternative A and
161 for either MDI or MDI-X configurations, albeit supporting one variation at a
186 More advanced PSE PI configurations may include integrated or external
188 compatibility with both MDI and MDI-X configurations.
190 More complex PSE PI configurations may include additional components, to support
210 Device Tree Configuration: Describing PSE PI Configurations
215 descriptions of both simple and complex PSE PI configurations to illustrate
[all …]
|
| /linux/Documentation/arch/xtensa/ |
| H A D | booting.rst | 11 - For configurations without MMU, with region protection or with MPU the
13 - For configurations with region translarion MMU or with MMUv3 and CONFIG_MMU=n
16 - For configurations with MMUv2 the address must be a virtual address in the
18 - For configurations with MMUv3 and CONFIG_MMU=y the address may be either a
|
| /linux/Documentation/admin-guide/ |
| H A D | pstore-blk.rst | 20 divides all configurations into two parts, configurations for user and
21 configurations for driver.
23 Configurations for user determine how pstore/blk works, such as pmsg_size,
27 Configurations for driver are all about block device and non-block device,
30 Configurations for user
33 All of these configurations support both Kconfig and module parameters, but
40 The detail of each configurations may be of interest to you.
154 Configurations for driver
|
| /linux/Documentation/driver-api/cxl/linux/ |
| H A D | cxl-driver.rst | 64 we'll explore more configurations in-depth in example configurations below.
249 configurations present in the CFMWS field of the :doc:`CEDT
427 :caption: Regions are created based on root decoder configurations. Endpoint decoders
472 at runtime - if the platform supports such configurations.
538 configurations to describe the same physical capacity, with the intent to allow
602 configurations, the :code:`interleave_granularity` of a decoder is equal to
619 Linux does not support unbalanced interleave configurations. As a result, all
622 Example Configurations
627 example-configurations/single-device.rst
628 example-configurations/hb-interleave.rst
[all …]
|
| /linux/Documentation/arch/arm/pxa/ |
| H A D | mfp.rst | 16 out of the GPIO controller. In addition to pin-mux configurations, the MFP
95 NOTE: PXA300 and PXA310 are almost identical in pin configurations (with
99 2. prepare an array for the initial pin configurations, e.g.::
123 a) once the pin configurations are passed to pxa{2xx,3xx}_mfp_config(),
127 b) when there is only one possible pin configurations for a component,
195 configurations, these definitions are processor and platform independent, and
211 configurations
215 for PXA2xx specific definitions and PXA25x/PXA27x common pin configurations
264 Examples of pin configurations are::
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | igbvf.rst | 13 - Additional Configurations
29 Configurations later in this document.
41 Additional Features and Configurations
|
| H A D | fm10k.rst | 13 - Additional Configurations
57 Additional Features and Configurations
95 other protocols besides TCP. It's also safe to use with configurations that
103 Retrieves the receive network flow classification configurations.
|
| /linux/tools/power/cpupower/man/ |
| H A D | cpupower-set.1 | 3 cpupower\-set \- Set processor power related kernel or hardware configurations
10 \fBcpupower set \fP sets kernel configurations or directly accesses hardware
14 are applied on all cores. How to modify single core configurations is
|
| H A D | cpupower-info.1 | 3 cpupower\-info \- Shows processor power related kernel or hardware configurations
9 \fBcpupower info \fP shows kernel configurations or processor hardware
|
| /linux/Documentation/devicetree/bindings/display/bridge/ |
| H A D | fsl,imx93-mipi-dsi.yaml | 14 Designware MIPI DPHY embedded in Freescale i.MX93 SoC. Some configurations
45 configurations from LCDIF display controller to the MIPI DSI host
46 controller and MIPI DPHY PLL related configurations through PLL SoC
|
| /linux/drivers/crypto/ccree/ |
| H A D | cc_aead.h | 71 /* buffer for internal ccm configurations */
76 /* buffer for internal gcm configurations */
78 /* buffer for internal gcm configurations */
|
| /linux/drivers/cxl/ |
| H A D | Kconfig | 126 control the EDAC memory features configurations of CXL memory
139 control the scrub feature configurations of CXL memory expander
157 control the ECS feature configurations of CXL memory expander
175 configurations of CXL memory expander devices.
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-magnetometer-hmc5843 | 6 Current configuration and available configurations
10 normal Normal measurement configurations (default)
|
| /linux/include/sound/ |
| H A D | wm8996.h | 19 * ReTune Mobile configurations are specified with a label, sample
22 * Configurations are expected to be generated using the ReTune Mobile
|
| /linux/arch/arm/mach-omap2/ |
| H A D | opp2430_data.c | 10 * The OMAP2 processor can be run at several discrete 'PRCM configurations'.
11 * These configurations are characterized by voltage and speed for clocks.
15 * setting. All configurations can be described by a DPLL setting and a ratio.
|
| H A D | opp2420_data.c | 10 * The OMAP2 processor can be run at several discrete 'PRCM configurations'.
11 * These configurations are characterized by voltage and speed for clocks.
15 * setting. All configurations can be described by a DPLL setting and a ratio.
|
| /linux/drivers/dma/ti/ |
| H A D | k3-psil-priv.h | 19 * @src: Array of source PSI-L thread configurations
21 * @dst: Array of destination PSI-L thread configurations
|
| /linux/Documentation/mhi/ |
| H A D | mhi.rst | 32 MHI control registers: Access to MHI configurations registers
55 Channel context array: All channel configurations are organized in channel
61 Event context array: All event configurations are organized in the event context
67 Command context array: All command configurations are organized in command
|
| /linux/include/linux/mfd/ |
| H A D | rohm-bd718x7.h | 29 /* Common voltage configurations */
39 /* BD71837 specific voltage configurations */
46 /* BD71847 specific voltage configurations */
|
| /linux/drivers/net/wireless/marvell/mwifiex/ |
| H A D | README | 33 The configurations can be done either using the 'iw' user space
67 …Apart from the iw utility all standard configurations using the 'iwconfig' utility are also suppor…
71 The debugfs interface can be used for configurations and for getting
73 The section below explains the configurations that can be
|