/linux-6.14.4/include/linux/firmware/intel/ |
D | stratix10-smc.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 3 * Copyright (C) 2017-2018, Intel Corporation 9 #include <linux/arm-smccc.h> 13 * This file defines the Secure Monitor Call (SMC) message protocol used for 19 * An ARM SMC instruction takes a function identifier and up to 6 64-bit 20 * register values as arguments, and can return up to 4 64-bit register 31 * STD call starts a operation which can be preempted by a non-secure 35 * a0..a7 is used as register names in the descriptions below, on arm32 81 * Sync call used by service driver at EL1 to request the FPGA in EL3 to 88 * a2-7: not used. [all …]
|
/linux-6.14.4/drivers/net/ipa/ |
D | ipa_reg.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 3 /* Copyright (c) 2012-2018, The Linux Foundation. All rights reserved. 4 * Copyright (C) 2018-2024 Linaro Ltd. 18 * IPA registers are located within the "ipa-reg" address space defined by 35 * (for parameterized registers) a non-zero stride value. Not all versions 44 * used to access register fields; both take an ipa_reg structure as 48 * reg_decode(). In addition, for single-bit fields, reg_bit() 49 * can be used to either encode the bit value, or to generate a mask 50 * used to extract the bit value. 53 /* enum ipa_reg_id - IPA register IDs */ [all …]
|
/linux-6.14.4/tools/perf/pmu-events/arch/x86/jaketown/ |
D | uncore-io.json | 8 …. However, because the R2PCIe is close to the Ubox, they generally should not diverge by more tha… 17 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 27 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 37 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 47 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 57 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 67 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 77 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 87 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 97 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… [all …]
|
D | uncore-memory.json | 12 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM WR_CAS (w/ and w/out auto-pre)", 30 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM RD_CAS (w/ and w/out auto-pre)", 57 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Read… 66 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Writ… 79 "PublicDescription": "Uncore Fixed Counter - uclks", 126 …ected by a filter) on the given channel. Major modea are channel-wide, and not a per-rank (or di… 136 …ected by a filter) on the given channel. Major modea are channel-wide, and not a per-rank (or di… 146 …ected by a filter) on the given channel. Major modea are channel-wide, and not a per-rank (or di… 156 …ected by a filter) on the given channel. Major modea are channel-wide, and not a per-rank (or di… 175 …e in PPD mode. If IBT=off is enabled, then this can be used to count those cycles. If it is not … [all …]
|
D | uncore-interconnect.json | 28 …": "Accumulates the number of writes that have acquired ownership but have not yet returned their … 38 …": "Accumulates the number of writes that have acquired ownership but have not yet returned their … 48 …ing in the uncore trying to acquire ownership in each cycle. This can be used with the write tran… 58 …ing in the uncore trying to acquire ownership in each cycle. This can be used with the write tran… 68 …r of reads that are outstanding in the uncore in each cycle. This can be used with the read trans… 78 …r of reads that are outstanding in the uncore in each cycle. This can be used with the read trans… 108 …efetches) that are outstanding in the uncore in each cycle. This can be used with the transactio… 118 …efetches) that are outstanding in the uncore in each cycle. This can be used with the transactio… 160 … This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns fr… 164 "BriefDescription": "BL Ingress Occupancy - DRS", [all …]
|
/linux-6.14.4/Documentation/arch/arm64/ |
D | acpi_object_usage.rst | 8 If a section number is used, it refers to a section number in the ACPI 9 specification where the object is defined. If "Signature Reserved" is used, 16 - Required: DSDT, FADT, GTDT, MADT, MCFG, RSDP, SPCR, XSDT 18 - Recommended: BERT, EINJ, ERST, HEST, PCCT, SSDT 20 - Optional: AGDI, BGRT, CEDT, CPEP, CSRT, DBG2, DRTM, ECDT, FACS, FPDT, 24 - Not supported: AEST, APMT, BOOT, DBGP, DMAR, ETDT, HPET, IVRS, LPIT, 41 This table describes a non-maskable event, that is used by the platform 62 Microsoft only table, will not be supported. 68 Optional, not currently supported, with no real use-case for an 82 Optional, not currently supported, and not recommended until such [all …]
|
/linux-6.14.4/tools/perf/pmu-events/arch/x86/ivytown/ |
D | uncore-io.json | 8 …. However, because the R2PCIe is close to the Ubox, they generally should not diverge by more tha… 17 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 27 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 37 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 47 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 57 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 67 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 77 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 87 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… 97 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… [all …]
|
D | uncore-interconnect.json | 18 … had an address match with another request in the write cache.; When it is not possible to merge t… 28 …not yet returned their data to the uncore. These writes are generally queued up in the switch try… 38 …": "Accumulates the number of writes that have acquired ownership but have not yet returned their … 48 …ing in the uncore trying to acquire ownership in each cycle. This can be used with the write tran… 58 …used with the write transaction count to calculate the average write latency in the uncore. The o… 68 …r of reads that are outstanding in the uncore in each cycle. This can be used with the read trans… 78 …used with the read transaction count to calculate the average read latency in the uncore. The occ… 98 …Q register. This register allows one to select one specific queue. It is not possible to monitor… 108 …efetches) that are outstanding in the uncore in each cycle. This can be used with the transactio… 118 …used with the transaction count event to calculate the average latency in the uncore. The occupan… [all …]
|
/linux-6.14.4/Documentation/input/ |
D | event-codes.rst | 1 .. _input-event-codes: 10 may be used. 14 used to separate input events into packets of input data changes occurring at 20 input subsystem; drivers do not need to maintain the state and may attempt to 31 type has a set of applicable codes to be used in generating events. See the 36 - Used as markers to separate events. Events may be separated in time or in 41 - Used to describe state changes of keyboards, buttons, or other key-like 46 - Used to describe relative axis value changes, e.g. moving the mouse 5 units 51 - Used to describe absolute axis value changes, e.g. describing the 56 - Used to describe miscellaneous input data that do not fit into other types. [all …]
|
/linux-6.14.4/tools/perf/pmu-events/arch/x86/broadwellx/ |
D | uncore-io.json | 8 …. However, because the R2PCIe is close to the Ubox, they generally should not diverge by more tha… 53 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 63 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 73 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 83 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 93 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 103 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 113 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… 123 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… 133 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… [all …]
|
D | uncore-interconnect.json | 7 …-width (L0) mode, flits are made up of four fits, each of which contains 20 bits of data (along wi… 17 …-width (L0) mode, flits are made up of four fits, each of which contains 20 bits of data (along wi… 38 …Q register. This register allows one to select one specific queue. It is not possible to monitor… 131 … "BriefDescription": "Misc Events - Set 0; Cache Inserts of Atomic Transactions as Secondary", 136 …"PublicDescription": "Counts Timeouts - Set 0 : Cache Inserts of Atomic Transactions as Secondary", 141 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Read Transactions as Secondary", 146 … "PublicDescription": "Counts Timeouts - Set 0 : Cache Inserts of Read Transactions as Secondary", 151 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Write Transactions as Secondary", 156 … "PublicDescription": "Counts Timeouts - Set 0 : Cache Inserts of Write Transactions as Secondary", 161 "BriefDescription": "Misc Events - Set 0; Fastpath Rejects", [all …]
|
/linux-6.14.4/tools/perf/pmu-events/arch/x86/broadwellde/ |
D | uncore-io.json | 8 …. However, because the R2PCIe is close to the Ubox, they generally should not diverge by more tha… 53 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 63 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 73 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 83 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 93 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 103 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 113 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… 123 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… 133 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… [all …]
|
/linux-6.14.4/Documentation/scsi/ |
D | st.rst | 1 .. SPDX-License-Identifier: GPL-2.0 17 The driver is generic, i.e., it does not contain any code tailored 23 flexible method and applicable to single-user workstations. However, 32 drive performs auto-detection of the tape format well (like some 33 QIC-drives). The result is that any tape can be read, writing can be 34 continued using existing format, and the default format is used if 37 does not perform auto-detection well enough and there is a single 39 used only in variable block mode (I don't know if this is sensible 40 or not :-). 51 the configuration of mode 0 is used to provide a starting point for [all …]
|
/linux-6.14.4/drivers/tee/optee/ |
D | optee_ffa.h | 1 /* SPDX-License-Identifier: BSD-2-Clause */ 3 * Copyright (c) 2019-2021, 2023 Linaro Limited 7 * This file is exported by OP-TEE and is kept in sync between secure world 8 * and normal world drivers. We're using ARM FF-A 1.0 specification. 23 * defined in FF-A specification: 27 * w3-w7: Implementation defined, free to be used below 38 * Returns the API version implemented, currently follows the FF-A version. 41 * w4-w7: Not used (MBZ) 46 * w5-w7: Not used (MBZ) 51 * Returns the revision of OP-TEE. [all …]
|
D | optee_smc.h | 1 /* SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) */ 3 * Copyright (c) 2015-2021, Linaro Limited 8 #include <linux/arm-smccc.h> 28 * Normal cached memory (write-back), shareable for SMP systems and not 34 * a0..a7 is used as register names in the descriptions below, on arm32 36 * 32-bit registers. 44 * 384fb3e0-e7f8-11e3-af63-0002a5d5c51b. 75 * Used by non-secure world to figure out which Trusted OS is installed. 76 * Note that returned UUID is the UUID of the Trusted OS, not of the API. 78 * Returns UUID in a0-4 in the same way as OPTEE_SMC_CALLS_UID [all …]
|
/linux-6.14.4/tools/perf/pmu-events/arch/x86/haswellx/ |
D | uncore-io.json | 8 …. However, because the R2PCIe is close to the Ubox, they generally should not diverge by more tha… 53 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 63 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 73 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 83 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 93 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 103 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 113 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… 123 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… 133 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… [all …]
|
D | uncore-interconnect.json | 7 …-width (L0) mode, flits are made up of four fits, each of which contains 20 bits of data (along wi… 17 …-width (L0) mode, flits are made up of four fits, each of which contains 20 bits of data (along wi… 38 …Q register. This register allows one to select one specific queue. It is not possible to monitor… 131 … "BriefDescription": "Misc Events - Set 0; Cache Inserts of Atomic Transactions as Secondary", 136 …"PublicDescription": "Counts Timeouts - Set 0 : Cache Inserts of Atomic Transactions as Secondary", 141 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Read Transactions as Secondary", 146 … "PublicDescription": "Counts Timeouts - Set 0 : Cache Inserts of Read Transactions as Secondary", 151 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Write Transactions as Secondary", 156 … "PublicDescription": "Counts Timeouts - Set 0 : Cache Inserts of Write Transactions as Secondary", 161 "BriefDescription": "Misc Events - Set 0; Fastpath Rejects", [all …]
|
/linux-6.14.4/Documentation/arch/arm/ |
D | setup.rst | 6 structure, otherwise known as 'struct param_struct' which is used 9 This structure is used to pass initialisation parameters from the 12 should not be referenced outside of arch/arm/kernel/setup.c:setup_arch(). 26 If the system contains separate VRAM, this value should not 30 This is now obsolete, and should not be used. 47 or VGA console character size. They should not be used for any other 56 is otherwise unused. (should not be used for other console types, and 57 should not be used for other purposes). 61 based machines. May be used differently by different architectures. 64 Default sound setting on Acorn machines. May be used differently by [all …]
|
/linux-6.14.4/drivers/net/ethernet/aquantia/atlantic/macsec/ |
D | macsec_struct.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */ 13 /*! This is used to store the 48 bit value used to compare SA, DA or 17 /*! This is used to store the 16 bit ethertype value used for 21 /*! The match mask is per-nibble. 0 means don't care, i.e. every value 26 /*! 0: No compare, i.e. This entry is not used 52 /*! The 8 bit value used to compare with extracted value for byte 3. */ 54 /*! The 8 bit value used to compare with extracted value for byte 2. */ 56 /*! The 8 bit value used to compare with extracted value for byte 1. */ 58 /*! The 8 bit value used to compare with extracted value for byte 0. */ 60 /*! The 8 bit TCI field used to compare with extracted value. */ [all …]
|
/linux-6.14.4/include/drm/ |
D | drm_modeset_helper_vtables.h | 3 * Copyright © 2007-2008 Dave Airlie 4 * Copyright © 2007-2008 Intel Corporation 6 * Copyright © 2011-2013 Intel Corporation 21 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 39 * they wish. Drivers are not forced to use this code in their 61 * struct drm_crtc_helper_funcs - helper operations for CRTCs 63 * These hooks are used by the legacy CRTC helpers and the new atomic 72 * This is used by the legacy CRTC helpers to implement DPMS 75 * This callback is also used to disable a CRTC by calling it with 76 * DRM_MODE_DPMS_OFF if the @disable hook isn't used. [all …]
|
/linux-6.14.4/include/uapi/mtd/ |
D | ubi-user.h | 1 /* SPDX-License-Identifier: GPL-2.0+ WITH Linux-syscall-note */ 16 * along with this program; if not, write to the Free Software 17 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA 33 * &struct ubi_attach_req object - UBI will attach the MTD device specified in 54 * device should be used. A pointer to the 32-bit volume ID hast to be passed 57 * UBI volume re-size 60 * To re-size a volume, the %UBI_IOCRSVOL ioctl command of the UBI character 61 * device should be used. A &struct ubi_rsvol_req object has to be properly 64 * UBI volumes re-name 67 * To re-name several volumes atomically at one go, the %UBI_IOCRNVOL command [all …]
|
/linux-6.14.4/drivers/net/wireless/intel/iwlwifi/mei/ |
D | sap.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */ 3 * Copyright (C) 2021 - 2022 Intel Corporation 9 #include "mei/iwl-mei.h" 14 * SAP is the protocol used by the Intel Wireless driver (iwlwifi) 32 * interface is used only for signaling and not to transfer 63 * CSME know not to access the shared memory anymore since it'll be freed. 67 * WiFi device or not followed by %SAP_MSG_NOTIF_CSME_CONN_STATUS to inform 82 * OS is not working or even missing, the CSME can request the 84 * is not operational. This is why the host driver needs to 124 * enum iwl_sap_me_msg_id - the ID of the ME message [all …]
|
/linux-6.14.4/sound/pci/emu10k1/ |
D | p17v.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */ 3 * Copyright (c) by James Courtier-Dutton <[email protected]> 8 /* Audigy2Value Tina (P17V) pointer-offset register set, */ 12 /* 00 - 07: Not used */ 16 /* 09 - 12: Not used */ 20 /* 14 - 17: Not used */ 24 /* 1b - 1f: Not used */ 25 /* 20 - 2f: Not used */ 26 /* 30 - 3b: Not used */ 62 /* FIXME: Not tested yet. */ [all …]
|
/linux-6.14.4/include/uapi/linux/ |
D | nl80211.h | 6 * Copyright 2006-2010 Johannes Berg <[email protected]> 13 * Copyright 2015-2017 Intel Deutschland GmbH 14 * Copyright (C) 2018-2024 Intel Corporation 32 * be careful not to break things - i.e. don't move anything around or so 74 * - a setup station entry is added, not yet authorized, without any rate 76 * - when the TDLS setup is done, a single NL80211_CMD_SET_STATION is valid 79 * - %NL80211_TDLS_ENABLE_LINK is then used 80 * - after this, the only valid operation is to remove it by tearing down 91 * that are not being handled by the kernel. This includes, for example, 95 * Frame registration is done on a per-interface basis and registrations [all …]
|
/linux-6.14.4/tools/perf/pmu-events/arch/x86/snowridgex/ |
D | uncore-memory.json | 8 …"PublicDescription": "Counts the total number of DRAM Read CAS commands, w/ and w/o auto-pre, issu… 19 … "Counts the total number of DRAM Write CAS commands issued, w/ and w/o auto-pre, on this channel.… 61 …"PublicDescription": "Counts the total number of DRAM Read CAS commands, w/ and w/o auto-pre, issu… 66 "BriefDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM RD_CAS commands w/auto-pre", 72 …-pre : DRAM RD_CAS and WR_CAS Commands : Counts the total number or DRAM Read CAS commands issued … 88 "BriefDescription": "All DRAM read CAS commands issued (does not include underfills)", 94 …s as well as those with implicit Precharge. We do not filter based on major mode, as RD_CAS is n… 115 … "Counts the total number of DRAM Write CAS commands issued, w/ and w/o auto-pre, on this channel.… 120 "BriefDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM WR_CAS commands w/o auto-pre", 126 …"PublicDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM WR_CAS commands w/o auto-pre : DRAM … [all …]
|