drivers/net/ethernet/microchip/sparx5/sparx5_pgid.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/microchip/sparx5/sparx5_pgid.c

Extension

.c

Size

1219 bytes

Lines

54

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

• sparx5_main.h

Detected Declarations

• function sparx5_pgid_init
• function sparx5_pgid_alloc_mcast
• function sparx5_pgid_free
• function sparx5_get_pgid

Annotated Snippet

if (spx5->pgid_map[i] == SPX5_PGID_FREE) {
			spx5->pgid_map[i] = SPX5_PGID_MULTICAST;
			*idx = i;
			return 0;
		}
	}

	return -EBUSY;
}

int sparx5_pgid_free(struct sparx5 *spx5, u16 idx)
{
	if (idx <= sparx5_get_pgid(spx5, PGID_CPU) ||
	    idx >= spx5->data->consts->n_pgids)
		return -EINVAL;

	if (spx5->pgid_map[idx] == SPX5_PGID_FREE)
		return -EINVAL;

	spx5->pgid_map[idx] = SPX5_PGID_FREE;
	return 0;
}

int sparx5_get_pgid(struct sparx5 *sparx5, int pgid)
{
	return sparx5->data->consts->n_ports + pgid;
}

Annotation

• Immediate include surface: `sparx5_main.h`.
• Detected declarations: `function sparx5_pgid_init`, `function sparx5_pgid_alloc_mcast`, `function sparx5_pgid_free`, `function sparx5_get_pgid`.
• 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.