Home
last modified time | relevance | path

Searched full:discovered (Results 1 – 25 of 303) sorted by relevance

12345678910>>...13

/linux/drivers/net/ethernet/freescale/dpaa2/
H A DKconfig12 The driver manages network objects discovered on the Freescale
39 switch objects discovered on the Freeescale MC bus.
/linux/Documentation/scsi/
H A Dbnx2fc.rst9 transparent. Devices discovered on the SAN will be registered and unregistered
19 support the VLANs that have been discovered for FCoE operation (e.g.
H A Dmegaraid.rst51 adapter discovered, and lsiioctl would essentially be a switch,
H A Dscsi-parameters.rst97 discovered. async scans them in kernel threads,
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-fcoe41 FCFs discovered by this controller.
131 used to identify the discovered FCF. FCFs will exist in a
/linux/tools/perf/pmu-events/arch/x86/silvermont/
H A Dpipeline.json107 "PublicDescription": "ALL_BRANCHES counts the number of any mispredicted branch instructions retired. This umask is an architecturally defined event. This event counts the number of retired branch instructions that were mispredicted by the processor, categorized by type. A branch misprediction occurs when the processor predicts that the branch would be taken, but it is not, or vice-versa. When the misprediction is discovered, all the instructions executed in the wrong (speculative) path must be discarded, and the processor must start fetching from the correct path.",
116 "PublicDescription": "IND_CALL counts the number of mispredicted near indirect CALL branch instructions retired. This event counts the number of retired branch instructions that were mispredicted by the processor, categorized by type. A branch misprediction occurs when the processor predicts that the branch would be taken, but it is not, or vice-versa. When the misprediction is discovered, all the instructions executed in the wrong (speculative) path must be discarded, and the processor must start fetching from the correct path.",
126 "PublicDescription": "JCC counts the number of mispredicted conditional branches (JCC) instructions retired. This event counts the number of retired branch instructions that were mispredicted by the processor, categorized by type. A branch misprediction occurs when the processor predicts that the branch would be taken, but it is not, or vice-versa. When the misprediction is discovered, all the instructions executed in the wrong (speculative) path must be discarded, and the processor must start fetching from the correct path.",
136 "PublicDescription": "NON_RETURN_IND counts the number of mispredicted near indirect JMP and near indirect CALL branch instructions retired. This event counts the number of retired branch instructions that were mispredicted by the processor, categorized by type. A branch misprediction occurs when the processor predicts that the branch would be taken, but it is not, or vice-versa. When the misprediction is discovered, all the instructions executed in the wrong (speculative) path must be discarded, and the processor must start fetching from the correct path.",
146 "PublicDescription": "RETURN counts the number of mispredicted near RET branch instructions retired. This event counts the number of retired branch instructions that were mispredicted by the processor, categorized by type. A branch misprediction occurs when the processor predicts that the branch would be taken, but it is not, or vice-versa. When the misprediction is discovered, all the instructions executed in the wrong (speculative) path must be discarded, and the processor must start fetching from the correct path.",
156 "PublicDescription": "TAKEN_JCC counts the number of mispredicted taken conditional branch (JCC) instructions retired. This event counts the number of retired branch instructions that were mispredicted by the processor, categorized by type. A branch misprediction occurs when the processor predicts that the branch would be taken, but it is not, or vice-versa. When the misprediction is discovered, all the instructions executed in the wrong (speculative) path must be discarded, and the processor must start fetching from the correct path.",
/linux/arch/arm/boot/dts/vt8500/
H A Dwm8950.dtsi6 /* No differences have been discovered vs. WM8850, but chip markings differ */
/linux/arch/powerpc/include/asm/
H A Dserial.h8 * Serial ports are not listed here, because they are discovered
/linux/Documentation/driver-api/rapidio/
H A Drapidio.rst210 form a network which will be enumerated/discovered. Discovering endpoints have
212 controllers have been initialized and are ready to be discovered. Configuration
291 in the system, it sets the Discovered bit in the Port General Control CSR
298 about RapidIO network structure and are building an internal map of discovered
/linux/fs/sysfs/
H A DKconfig12 kernel, such as the devices the kernel has discovered on each bus and
/linux/drivers/parisc/
H A DREADME.dino4 ** "HP has discovered a potential system defect that can affect
/linux/Documentation/driver-api/nfc/
H A Dnfc-hci.rst106 discovered target.
275 that was discovered).
308 active, it will send a tag discovered event with an empty tag list to the user
/linux/net/tipc/
H A Ddiscover.c56 * @num_nodes: number of nodes currently discovered (i.e. with an active link)
261 /* tipc_disc_add_dest - increment set of discovered nodes
270 /* tipc_disc_remove_dest - decrement set of discovered nodes
/linux/include/scsi/
H A Dlibfcoe.h83 * @fcfs: list of discovered FCFs.
85 * @fcf_count: number of discovered FCF entries.
179 * @fip: The controller that the FCF was discovered on
/linux/net/sctp/
H A DKconfig25 -- data fragmentation to conform to discovered path MTU size,
/linux/arch/x86/pci/
H A Dlegacy.c50 pr_info("PCI: Discovered peer bus %02x\n", busn); in pcibios_scan_specific_bus()
/linux/arch/parisc/include/asm/
H A Dparisc-device.h37 int (*probe)(struct parisc_device *dev); /* New device discovered */
/linux/Documentation/devicetree/bindings/arm/
H A Dqcom,coresight-ctcu.yaml17 The configuration mode (ETB, ETF, ETR) is discovered at boot time when
/linux/include/uapi/linux/
H A Dnfc.h74 * @NFC_EVENT_SE_ADDED: Event emitted when a new secure element is discovered.
87 * @NFC_CMD_GET_SE: Dump all discovered secure elements from an NFC controller.
/linux/drivers/nfc/microread/
H A Dmicroread.c474 pr_info("target discovered to gate 0x%x\n", gate); in microread_target_discovered()
531 pr_info("discard target discovered to gate 0x%x\n", gate); in microread_target_discovered()
544 pr_err("Failed to handle discovered target err=%d\n", r); in microread_target_discovered()
/linux/Documentation/admin-guide/device-mapper/
H A Dverity.rst82 Restart the system when a corrupted block is discovered. This option is
87 Panic the device when a corrupted block is discovered. This option is
/linux/Documentation/devicetree/bindings/virtio/
H A Dpci-iommu.yaml14 discovered dynamically by the PCI probing infrastructure. However the
/linux/Documentation/firmware-guide/acpi/
H A Denumeration.rst72 that can be discovered and enumerated natively, through a protocol defined for
75 by the platform firmware so that they can be discovered. Still, for any device
87 objects for the majority of devices that are discovered and enumerated with the
92 discovered with the help of the platform firmware.
/linux/drivers/rapidio/
H A Drio-scan.c219 /* Mark device as discovered and enable master */ in rio_clear_locks()
540 pr_debug("RIO: PE already discovered by this host\n"); in rio_enum_peer()
542 * Already discovered by this host. Add it as another in rio_enum_peer()
704 * Tests the PGCCSR discovered bit for non-zero value (enumeration
719 * @net: RIO network being discovered
/linux/Documentation/security/tpm/
H A Dtpm_ffa_crb.rst43 - If a TPM service is discovered by FF-A, the probe() function in the

12345678910>>...13