Home
last modified time | relevance | path

Searched +full:configuration +full:- +full:dependent (Results 1 – 25 of 905) sorted by relevance

12345678910>>...37

/kernel/linux/linux-6.6/Documentation/admin-guide/pm/
Dsuspend-flows.rst1 .. SPDX-License-Identifier: GPL-2.0
12 At least one global system-wide transition needs to be carried out for the
14 :doc:`sleep states <sleep-states>`. Hibernation requires more than one
16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
27 significant differences between the :ref:`suspend-to-idle <s2idle>` code flows
28 and the code flows related to the :ref:`suspend-to-RAM <s2ram>` and
31 The :ref:`suspend-to-RAM <s2ram>` and :ref:`standby <standby>` sleep states
33 boils down to the platform-specific actions carried out by the suspend and
37 *platform-dependent suspend* states in what follows.
42 Suspend-to-idle Suspend Code Flow
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/pm/
Dsuspend-flows.rst1 .. SPDX-License-Identifier: GPL-2.0
12 At least one global system-wide transition needs to be carried out for the
14 :doc:`sleep states <sleep-states>`. Hibernation requires more than one
16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
27 significant differences between the :ref:`suspend-to-idle <s2idle>` code flows
28 and the code flows related to the :ref:`suspend-to-RAM <s2ram>` and
31 The :ref:`suspend-to-RAM <s2ram>` and :ref:`standby <standby>` sleep states
33 boils down to the platform-specific actions carried out by the suspend and
37 *platform-dependent suspend* states in what follows.
42 Suspend-to-idle Suspend Code Flow
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/pci/
Dsnps,dw-pcie-common.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
23 Interface - DBI. In accordance with the reference manual the register
24 configuration space belongs to the Configuration-Dependent Module (CDM)
25 and is split up into several sub-parts Standard PCIe configuration
26 space, Port Logic Registers (PL), Shadow Config-space Registers,
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dcputopology.rst13 dependent.
19 architecture and platform dependent.
25 architecture and platform dependent.
31 architecture and platform dependent.
37 architecture and platform dependent.
46 human-readable list of CPUs within the same core.
56 human-readable list of CPUs sharing the same physical_package_id.
65 human-readable list of CPUs within the same die.
74 human-readable list of cpuX's hardware threads within the same
84 human-readable list of cpuX's hardware threads within the same
[all …]
/kernel/linux/linux-6.6/drivers/staging/media/deprecated/atmel/
Datmel-isc.h1 /* SPDX-License-Identifier: GPL-2.0 */
5 * Copyright (C) 2016-2019 Microchip Technology, Inc.
13 #include <linux/clk-provider.h>
16 #include <media/v4l2-ctrls.h>
17 #include <media/v4l2-device.h>
18 #include <media/videobuf2-dma-contig.h>
57 * struct isc_format - ISC media bus format information
97 * struct fmt_config - ISC format configuration and internal pipeline
98 This structure represents the internal configuration
102 configuration.
[all …]
/kernel/linux/linux-6.6/drivers/media/platform/microchip/
Dmicrochip-isc.h1 /* SPDX-License-Identifier: GPL-2.0 */
5 * Copyright (C) 2016-2019 Microchip Technology, Inc.
13 #include <linux/clk-provider.h>
16 #include <media/v4l2-ctrls.h>
17 #include <media/v4l2-device.h>
18 #include <media/videobuf2-dma-contig.h>
57 * struct isc_format - ISC media bus format information
98 * struct fmt_config - ISC format configuration and internal pipeline
99 This structure represents the internal configuration
103 configuration.
[all …]
/kernel/linux/linux-5.10/arch/parisc/include/uapi/asm/
Dpdc.h1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
14 #define PDC_BAD_PROC -1 /* Called non-existent procedure*/
15 #define PDC_BAD_OPTION -2 /* Called with non-existent option */
16 #define PDC_ERROR -3 /* Call could not complete without an error */
17 #define PDC_NE_MOD -5 /* Module not found */
18 #define PDC_NE_CELL_MOD -7 /* Cell module not found */
19 #define PDC_NE_BOOTDEV -9 /* Cannot locate a console device or boot device */
20 #define PDC_INVALID_ARG -10 /* Called with an invalid argument */
21 #define PDC_BUS_POW_WARN -12 /* Call could not complete in allowed power budget */
22 #define PDC_NOT_NARROW -17 /* Narrow mode not supported */
[all …]
/kernel/linux/linux-6.6/arch/parisc/include/uapi/asm/
Dpdc.h1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
14 #define PDC_BAD_PROC -1 /* Called non-existent procedure*/
15 #define PDC_BAD_OPTION -2 /* Called with non-existent option */
16 #define PDC_ERROR -3 /* Call could not complete without an error */
17 #define PDC_NE_MOD -5 /* Module not found */
18 #define PDC_NE_CELL_MOD -7 /* Cell module not found */
19 #define PDC_NE_BOOTDEV -9 /* Cannot locate a console device or boot device */
20 #define PDC_INVALID_ARG -10 /* Called with an invalid argument */
21 #define PDC_BUS_POW_WARN -12 /* Call could not complete in allowed power budget */
22 #define PDC_NOT_NARROW -17 /* Narrow mode not supported */
[all …]
/kernel/linux/linux-6.6/drivers/thermal/st/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # STMicroelectronics thermal drivers configuration
23 configuration is fully dependent of MACH_STM32MP157.
/kernel/linux/linux-5.10/drivers/thermal/st/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # STMicroelectronics thermal drivers configuration
27 configuration is fully dependent of MACH_STM32MP157.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/pci/
Ddesignware-pcie.txt4 - compatible:
5 "snps,dw-pcie" for RC mode;
6 "snps,dw-pcie-ep" for EP mode;
7 - reg: For designware cores version < 4.80 contains the configuration
9 the configuration and ATU address space
10 - reg-names: Must be "config" for the PCIe configuration space and "atu" for
12 (The old way of getting the configuration address space from "ranges"
15 - #address-cells: set to <3>
16 - #size-cells: set to <2>
17 - device_type: set to "pci"
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/dma/
Datmel-dma.txt4 - compatible: Should be "atmel,<chip>-dma".
5 - reg: Should contain DMA registers location and length.
6 - interrupts: Should contain DMA interrupt.
7 - #dma-cells: Must be <2>, used to represent the number of integer cells in
13 compatible = "atmel,at91sam9g45-dma";
16 #dma-cells = <2>;
20 described in the dma.txt file, using a three-cell specifier for each channel:
27 3. Parameters for the at91 DMA configuration register which are device
28 dependent:
29 - bit 7-0: peripheral identifier for the hardware handshaking interface. The
[all …]
Dst,stm32-dma.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/st,stm32-dma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The STM32 DMA is a general-purpose direct memory access controller capable of
13 described in the dma.txt file, using a four-cell specifier for each
17 3. A 32bit mask specifying the DMA channel configuration which are device
18 dependent:
19 -bit 9: Peripheral Increment Address
22 -bit 10: Memory Increment Address
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/dma/
Datmel-dma.txt4 - compatible: Should be "atmel,<chip>-dma".
5 - reg: Should contain DMA registers location and length.
6 - interrupts: Should contain DMA interrupt.
7 - #dma-cells: Must be <2>, used to represent the number of integer cells in
13 compatible = "atmel,at91sam9g45-dma";
16 #dma-cells = <2>;
20 described in the dma.txt file, using a three-cell specifier for each channel:
27 3. Parameters for the at91 DMA configuration register which are device
28 dependent:
29 - bit 7-0: peripheral identifier for the hardware handshaking interface. The
[all …]
/kernel/linux/linux-5.10/Documentation/infiniband/
Dopa_vnic.rst2 Intel Omni-Path (OPA) Virtual Network Interface Controller (VNIC)
5 Intel Omni-Path (OPA) Virtual Network Interface Controller (VNIC) feature
6 supports Ethernet functionality over Omni-Path fabric by encapsulating
11 The patterns of exchanges of Omni-Path encapsulated Ethernet packets
12 involves one or more virtual Ethernet switches overlaid on the Omni-Path
13 fabric topology. A subset of HFI nodes on the Omni-Path fabric are
17 header generation and processing. In the simplest configuration all HFI
20 an independent Ethernet network. The configuration is performed by an
26 +-------------------+
30 +-------------------+
[all …]
/kernel/linux/linux-6.6/Documentation/infiniband/
Dopa_vnic.rst2 Intel Omni-Path (OPA) Virtual Network Interface Controller (VNIC)
5 Intel Omni-Path (OPA) Virtual Network Interface Controller (VNIC) feature
6 supports Ethernet functionality over Omni-Path fabric by encapsulating
11 The patterns of exchanges of Omni-Path encapsulated Ethernet packets
12 involves one or more virtual Ethernet switches overlaid on the Omni-Path
13 fabric topology. A subset of HFI nodes on the Omni-Path fabric are
17 header generation and processing. In the simplest configuration all HFI
20 an independent Ethernet network. The configuration is performed by an
26 +-------------------+
30 +-------------------+
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/kdump/
Dkdump.rst2 Documentation for Kdump - The kexec-based Crash Dumping Solution
11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
14 the reboot and is accessible to the dump-capture kernel.
24 the dump-capture kernel. This ensures that ongoing Direct Memory Access
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
26 The kexec -p command loads the dump-capture kernel into this reserved
31 region just before rebooting into the dump-capture kernel.
45 passed to the dump-capture kernel through the elfcorehdr= boot
50 With the dump-capture kernel, you can access the memory image through
51 /proc/vmcore. This exports the dump as an ELF-format file that you can
[all …]
/kernel/linux/linux-5.10/drivers/staging/most/dim2/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
3 # MediaLB configuration
12 This device driver is platform dependent and needs an additional
/kernel/linux/linux-6.6/drivers/staging/most/dim2/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
3 # MediaLB configuration
12 This device driver is platform dependent and needs an additional
/kernel/linux/linux-6.6/include/acpi/platform/
Daclinux.h1 /* SPDX-License-Identifier: BSD-3-Clause OR GPL-2.0 */
4 * Name: aclinux.h - OS specific defines, etc. for Linux
6 * Copyright (C) 2000 - 2023, Intel Corp.
23 /* Common (in-kernel/user-space) ACPICA configuration */
34 /* Kernel specific ACPICA configuration */
105 /* Host-dependent types and defines for in-kernel ACPICA */
131 * Overrides for in-kernel ACPICA
190 /* Define/disable kernel-specific declarators */
199 /* Host-dependent types and defines for user-space ACPICA */
/kernel/linux/linux-5.10/include/acpi/platform/
Daclinux.h1 /* SPDX-License-Identifier: BSD-3-Clause OR GPL-2.0 */
4 * Name: aclinux.h - OS specific defines, etc. for Linux
6 * Copyright (C) 2000 - 2020, Intel Corp.
23 /* Common (in-kernel/user-space) ACPICA configuration */
34 /* Kernel specific ACPICA configuration */
105 /* Host-dependent types and defines for in-kernel ACPICA */
126 * Overrides for in-kernel ACPICA
181 /* Define/disable kernel-specific declarators */
190 /* Host-dependent types and defines for user-space ACPICA */
/kernel/linux/linux-6.6/Documentation/admin-guide/kdump/
Dkdump.rst2 Documentation for Kdump - The kexec-based Crash Dumping Solution
11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
14 the reboot and is accessible to the dump-capture kernel.
24 the dump-capture kernel. This ensures that ongoing Direct Memory Access
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
26 The kexec -p command loads the dump-capture kernel into this reserved
47 passed to the dump-capture kernel through the elfcorehdr= boot
51 With the dump-capture kernel, you can access the memory image through
52 /proc/vmcore. This exports the dump as an ELF-format file that you can
55 options, e.g with '-d 31' it will only write out kernel data. Further,
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/
Dsolomon,ssd1307fb.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Maxime Ripard <mripard@kernel.org>
11 - Javier Martinez Canillas <javierm@redhat.com>
17 - enum:
18 - solomon,ssd1305fb-i2c
19 - solomon,ssd1306fb-i2c
20 - solomon,ssd1307fb-i2c
21 - solomon,ssd1309fb-i2c
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/mmc/
Daspeed,sdhci.yaml1 # SPDX-License-Identifier: GPL-2.0-or-later
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Andrew Jeffery <andrew@aj.id.au>
12 - Ryan Chen <ryanchen.aspeed@gmail.com>
19 The two slots are supported by a common configuration area. As the SDHCIs for
20 the slots are dependent on the common configuration area, they are described
26 - aspeed,ast2400-sd-controller
27 - aspeed,ast2500-sd-controller
28 - aspeed,ast2600-sd-controller
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mmc/
Daspeed,sdhci.yaml1 # SPDX-License-Identifier: GPL-2.0-or-later
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Andrew Jeffery <andrew@aj.id.au>
12 - Ryan Chen <ryanchen.aspeed@gmail.com>
19 The two slots are supported by a common configuration area. As the SDHCIs for
20 the slots are dependent on the common configuration area, they are described
26 - aspeed,ast2400-sd-controller
27 - aspeed,ast2500-sd-controller
28 - aspeed,ast2600-sd-controller
[all …]

12345678910>>...37