Home
last modified time | relevance | path

Searched +full:multi +full:- +full:instance (Results 1 – 25 of 600) sorted by relevance

12345678910>>...24

/kernel/linux/linux-5.10/include/linux/
Dcpuhotplug.h1 /* SPDX-License-Identifier: GPL-2.0 */
8 * CPU-up CPU-down
15 * BRINGUP_CPU->AP_OFFLINE BRINGUP_CPU <- AP_IDLE_DEAD (idle thread/play_dead)
17 * v (IRQ-off) ,---------------^
19 * | TEARDOWN_CPU <- AP_ONLINE_IDLE
26 CPUHP_INVALID = -1,
215 * cpuhp_setup_state - Setup hotplug state callbacks with calling the callbacks
242 * cpuhp_setup_state_nocalls - Setup hotplug state callbacks without calling the
271 * cpuhp_setup_state_multi - Add callbacks for multi state
277 * Sets the internal multi_instance flag and prepares a state to work as a multi
[all …]
/kernel/linux/linux-6.6/include/linux/
Dcpuhotplug.h1 /* SPDX-License-Identifier: GPL-2.0 */
8 * CPU-up CPU-down
15 * BRINGUP_CPU->AP_OFFLINE BRINGUP_CPU <- AP_IDLE_DEAD (idle thread/play_dead)
17 * v (IRQ-off) ,---------------^
19 * | TEARDOWN_CPU <- AP_ONLINE_IDLE
30 * CPU_ONLINE - 1 down to CPUHP_OFFLINE.
54 * See Documentation/core-api/cpu_hotplug.rst for further information and
58 CPUHP_INVALID = -1,
273 * cpuhp_setup_state - Setup hotplug state callbacks with calling the @startup
292 * cpuhp_setup_state_cpuslocked - Setup hotplug state callbacks with calling
[all …]
/kernel/linux/linux-6.6/Documentation/core-api/
Dcpu_hotplug.rst26 A more novel use of CPU-hotplug support is its use today in suspend resume
27 support for SMP. Dual-core and HT support makes even a laptop run SMP kernels
81 from the map depending on the event is hot-add/hot-remove. There are currently
86 be read-only for most use. When setting up per-cpu resources almost always use
100 $ ls -lh /sys/devices/system/cpu
102 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu0
103 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu1
104 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu2
105 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu3
106 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu4
[all …]
/kernel/linux/linux-6.6/drivers/firmware/arm_scmi/
Dprotocols.h1 /* SPDX-License-Identifier: GPL-2.0 */
39 * struct scmi_msg_resp_prot_version - Response for a message
56 * struct scmi_msg - Message(Tx/Rx) structure
67 * struct scmi_msg_hdr - Message(Tx/Rx) header
89 * struct scmi_xfer - Structure representing a message flow
94 * @rx: Receive message, the buffer should be pre-allocated to store
95 * message. If request-ACK protocol is used, we can reuse the same
108 * though the timed-out transaction will anyway cause the command
109 * request to be reported as failed by time-out, the underlying xfer
115 * - SCMI_XFER_SENT_OK -> SCMI_XFER_RESP_OK [ -> SCMI_XFER_DRESP_OK ]
[all …]
/kernel/linux/linux-6.6/Documentation/arch/s390/
Dpci.rst1 .. SPDX-License-Identifier: GPL-2.0
8 - Pierre Morel
17 -----------------------
28 ---------------
36 - /sys/kernel/debug/s390dbf/pci_msg/sprintf
56 - /sys/bus/pci/slots/XXXXXXXX/power
64 - function_id
67 - function_handle
68 Low-level identifier used for a configured PCI function.
71 - pchid
[all …]
/kernel/linux/linux-6.6/include/linux/surface_aggregator/
Dcontroller.h1 /* SPDX-License-Identifier: GPL-2.0+ */
9 * Copyright (C) 2019-2021 Maximilian Luz <luzmaximilian@gmail.com>
22 /* -- Main data types and definitions --------------------------------------- */
25 * enum ssam_event_flags - Flags for enabling/disabling SAM events
33 * struct ssam_event - SAM event sent from the EC to the host.
37 * @instance_id: Instance ID of the event source.
51 * enum ssam_request_flags - Flags for SAM requests.
70 * struct ssam_request - SAM request description.
74 * @instance_id: Instance ID of the request's target.
94 * struct ssam_response - Response buffer for SAM request.
[all …]
/kernel/linux/linux-5.10/Documentation/block/
Dblk-mq.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Multi-Queue Block IO Queueing Mechanism (blk-mq)
7 The Multi-Queue Block IO Queueing Mechanism is an API to enable fast storage
16 ----------
26 However, with the development of Solid State Drives and Non-Volatile Memories
30 in those devices' design, the multi-queue mechanism was introduced.
36 to different CPUs) wanted to perform block IO. Instead of this, the blk-mq API
42 ---------
45 for instance), blk-mq takes action: it will store and manage IO requests to
49 blk-mq has two group of queues: software staging queues and hardware dispatch
[all …]
/kernel/linux/linux-6.6/Documentation/block/
Dblk-mq.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Multi-Queue Block IO Queueing Mechanism (blk-mq)
7 The Multi-Queue Block IO Queueing Mechanism is an API to enable fast storage
16 ----------
26 However, with the development of Solid State Drives and Non-Volatile Memories
30 in those devices' design, the multi-queue mechanism was introduced.
36 to different CPUs) wanted to perform block IO. Instead of this, the blk-mq API
42 ---------
45 for instance), blk-mq takes action: it will store and manage IO requests to
49 blk-mq has two group of queues: software staging queues and hardware dispatch
[all …]
/kernel/linux/linux-5.10/drivers/net/wireless/broadcom/brcm80211/brcmfmac/
Dfeature.h1 // SPDX-License-Identifier: ISC
12 * MCHAN: multi-channel for concurrent P2P.
14 * WOWL: Wake-On-WLAN.
15 * P2P: peer-to-peer
89 * brcmf_feat_attach() - determine features and quirks.
91 * @drvr: driver instance.
96 * brcmf_feat_debugfs_create() - create debugfs entries.
98 * @drvr: driver instance.
103 * brcmf_feat_is_enabled() - query feature.
105 * @ifp: interface instance.
[all …]
/kernel/linux/linux-6.6/drivers/net/wireless/broadcom/brcm80211/brcmfmac/
Dfeature.h1 // SPDX-License-Identifier: ISC
12 * MCHAN: multi-channel for concurrent P2P.
14 * WOWL: Wake-On-WLAN.
15 * P2P: peer-to-peer
95 * brcmf_feat_attach() - determine features and quirks.
97 * @drvr: driver instance.
102 * brcmf_feat_debugfs_create() - create debugfs entries.
104 * @drvr: driver instance.
109 * brcmf_feat_is_enabled() - query feature.
111 * @ifp: interface instance.
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-dma.txt8 CRYPTO Engines etc has its own instance of dma hardware. QMSS has also
13 ------------------
15 ------------------
17 |-> DMA instance #0
19 |-> DMA instance #1
23 |-> DMA instance #n
27 - compatible: Should be "ti,keystone-navigator-dma"
28 - clocks: phandle to dma instances clocks. The clock handles can be as
31 - ti,navigator-cloud-address: Should contain base address for the multi-core
40 DMA instance properties:
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-dma.txt8 CRYPTO Engines etc has its own instance of dma hardware. QMSS has also
13 ------------------
15 ------------------
17 |-> DMA instance #0
19 |-> DMA instance #1
23 |-> DMA instance #n
27 - compatible: Should be "ti,keystone-navigator-dma"
28 - clocks: phandle to dma instances clocks. The clock handles can be as
31 - ti,navigator-cloud-address: Should contain base address for the multi-core
40 DMA instance properties:
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/thermal/
Dexynos-thermal.txt5 - compatible : One of the following:
6 "samsung,exynos3250-tmu"
7 "samsung,exynos4412-tmu"
8 "samsung,exynos4210-tmu"
9 "samsung,exynos5250-tmu"
10 "samsung,exynos5260-tmu"
11 "samsung,exynos5420-tmu" for TMU channel 0, 1 on Exynos5420
12 "samsung,exynos5420-tmu-ext-triminfo" for TMU channels 2, 3 and 4
14 "samsung,exynos5433-tmu"
15 "samsung,exynos7-tmu"
[all …]
/kernel/linux/linux-5.10/Documentation/core-api/
Dcpu_hotplug.rst25 A more novel use of CPU-hotplug support is its use today in suspend resume
26 support for SMP. Dual-core and HT support makes even a laptop run SMP kernels
80 from the map depending on the event is hot-add/hot-remove. There are currently
85 be read-only for most use. When setting up per-cpu resources almost always use
98 $ ls -lh /sys/devices/system/cpu
100 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu0
101 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu1
102 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu2
103 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu3
104 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu4
[all …]
/kernel/linux/linux-5.10/include/linux/platform_data/
Dasoc-ti-mcbsp.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * Defines for Multi-Channel Buffered Serial Port
26 /* McBSP platform and instance specific features */
/kernel/linux/linux-6.6/include/linux/platform_data/
Dasoc-ti-mcbsp.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * Defines for Multi-Channel Buffered Serial Port
26 /* McBSP platform and instance specific features */
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/thermal/
Dsamsung,exynos-thermal.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/thermal/samsung,exynos-thermal.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
13 For multi-instance tmu each instance should have an alias correctly numbered
19 - samsung,exynos3250-tmu
20 - samsung,exynos4412-tmu
21 - samsung,exynos4210-tmu
22 - samsung,exynos5250-tmu
[all …]
/kernel/linux/linux-6.6/drivers/hwtracing/coresight/
Dcoresight-config.h1 /* SPDX-License-Identifier: GPL-2.0 */
13 /* CoreSight Configuration Management - component and system wide configuration */
28 * system configuration - used by config data and devices.
33 /* flags defining device instance matching - used in config match desc data. */
34 #define CS_CFG_MATCH_INST_ANY 0x80000000 /* any instance of a class */
40 * See PMU_FORMAT_ATTR(preset, "config:0-3") in coresight-etm-perf.c
69 * @mask32: 32 bit mask when using 32 bit value to access device register - if mask type.
89 * Device feature descriptor - combination of registers and parameters to
117 * Configuration descriptor - describes selectable system configuration.
123 * all the features in use - this value is @nr_total_params.
[all …]
/kernel/linux/linux-6.6/arch/arm/mach-pxa/
Dmfp-pxa3xx.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * linux/arch/arm/mach-pxa/mfp.c
5 * PXA3xx Multi-Function Pin Support
9 * 2007-08-21: eric miao <eric.miao@marvell.com>
19 #include "mfp-pxa3xx.h"
20 #include "pxa3xx-regs.h"
26 * entering - for instance, we might not want to place MFP pins in
27 * a pull-down mode if they're an active low chip select, and we're
42 * NOTE: the last 3 bits DxS are write-1-to-clear so carefully in pxa3xx_mfp_resume()
/kernel/linux/linux-5.10/Documentation/admin-guide/media/
Dfimc.rst1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
17 drivers/media/platform/exynos4-is directory.
20 --------------
22 S5PC100 (mem-to-mem only), S5PV210, Exynos4210
25 ------------------
27 - camera parallel interface capture (ITU-R.BT601/565);
28 - camera serial interface capture (MIPI-CSI2);
29 - memory-to-memory processing (color space conversion, scaling, mirror
31 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/media/
Dfimc.rst1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
17 drivers/media/platform/samsung/exynos4-is directory.
20 --------------
22 S5PC100 (mem-to-mem only), S5PV210, Exynos4210
25 ------------------
27 - camera parallel interface capture (ITU-R.BT601/565);
28 - camera serial interface capture (MIPI-CSI2);
29 - memory-to-memory processing (color space conversion, scaling, mirror
31 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
[all …]
/kernel/linux/linux-5.10/arch/arm/mach-pxa/
Dmfp-pxa3xx.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * linux/arch/arm/mach-pxa/mfp.c
5 * PXA3xx Multi-Function Pin Support
9 * 2007-08-21: eric miao <eric.miao@marvell.com>
20 #include "mfp-pxa3xx.h"
21 #include <mach/pxa3xx-regs.h>
27 * entering - for instance, we might not want to place MFP pins in
28 * a pull-down mode if they're an active low chip select, and we're
43 * NOTE: the last 3 bits DxS are write-1-to-clear so carefully in pxa3xx_mfp_resume()
/kernel/linux/linux-5.10/Documentation/networking/
Dscaling.rst1 .. SPDX-License-Identifier: GPL-2.0
13 multi-processor systems.
17 - RSS: Receive Side Scaling
18 - RPS: Receive Packet Steering
19 - RFS: Receive Flow Steering
20 - Accelerated Receive Flow Steering
21 - XPS: Transmit Packet Steering
28 (multi-queue). On reception, a NIC can send different packets to different
33 generally known as “Receive-side Scaling” (RSS). The goal of RSS and
35 Multi-queue distribution can also be used for traffic prioritization, but
[all …]
/kernel/linux/linux-6.6/Documentation/networking/
Dscaling.rst1 .. SPDX-License-Identifier: GPL-2.0
13 multi-processor systems.
17 - RSS: Receive Side Scaling
18 - RPS: Receive Packet Steering
19 - RFS: Receive Flow Steering
20 - Accelerated Receive Flow Steering
21 - XPS: Transmit Packet Steering
28 (multi-queue). On reception, a NIC can send different packets to different
33 generally known as “Receive-side Scaling” (RSS). The goal of RSS and
35 Multi-queue distribution can also be used for traffic prioritization, but
[all …]
/kernel/linux/linux-6.6/drivers/phy/mediatek/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
6 tristate "MediaTek PCIe-PHY Driver"
12 This driver create the basic PHY instance and provides initialize
17 tristate "MediaTek T-PHY Driver"
23 Say 'Y' here to add support for MediaTek T-PHY driver,
25 SATA, and meanwhile supports two version T-PHY which have
26 different banks layout, the T-PHY with shared banks between
27 multi-ports is first version, otherwise is second version,
31 tristate "MediaTek UFS M-PHY driver"
36 Support for UFS M-PHY on MediaTek chipsets.
[all …]

12345678910>>...24