drivers/net/ethernet/mellanox/mlx5/core/lib/pci_vsc.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/mellanox/mlx5/core/lib/pci_vsc.h

Extension

.h

Size

823 bytes

Lines

33

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• enum mlx5_vsc_state
• function mlx5_vsc_accessible

Annotated Snippet

#ifndef __MLX5_PCI_VSC_H__
#define __MLX5_PCI_VSC_H__

enum mlx5_vsc_state {
	MLX5_VSC_UNLOCK,
	MLX5_VSC_LOCK,
};

enum {
	MLX5_VSC_SPACE_SCAN_CRSPACE = 0x7,
};

void mlx5_pci_vsc_init(struct mlx5_core_dev *dev);
int mlx5_vsc_gw_lock(struct mlx5_core_dev *dev);
int mlx5_vsc_gw_unlock(struct mlx5_core_dev *dev);
int mlx5_vsc_gw_set_space(struct mlx5_core_dev *dev, u16 space,
			  u32 *ret_space_size);
int mlx5_vsc_gw_read_block_fast(struct mlx5_core_dev *dev, u32 *data,
				int length);

static inline bool mlx5_vsc_accessible(struct mlx5_core_dev *dev)
{
	return !!dev->vsc_addr;
}

int mlx5_vsc_sem_set_space(struct mlx5_core_dev *dev, u16 space,
			   enum mlx5_vsc_state state);

#endif /* __MLX5_PCI_VSC_H__ */

Annotation

• Detected declarations: `enum mlx5_vsc_state`, `function mlx5_vsc_accessible`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.