drivers/net/ethernet/microchip/sparx5/sparx5_vcap_debugfs.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/microchip/sparx5/sparx5_vcap_debugfs.h

Extension

.h

Size

729 bytes

Lines

34

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

• linux/netdevice.h
• vcap_api.h
• vcap_api_client.h

Detected Declarations

• function sparx5_port_info

Annotated Snippet

#ifndef __SPARX5_VCAP_DEBUGFS_H__
#define __SPARX5_VCAP_DEBUGFS_H__

#include <linux/netdevice.h>

#include <vcap_api.h>
#include <vcap_api_client.h>

#if defined(CONFIG_DEBUG_FS)

/* Provide port information via a callback interface */
int sparx5_port_info(struct net_device *ndev,
		     struct vcap_admin *admin,
		     struct vcap_output_print *out);

#else

static inline int sparx5_port_info(struct net_device *ndev,
				   struct vcap_admin *admin,
				   struct vcap_output_print *out)
{
	return 0;
}

#endif

#endif /* __SPARX5_VCAP_DEBUGFS_H__ */

Annotation

• Immediate include surface: `linux/netdevice.h`, `vcap_api.h`, `vcap_api_client.h`.
• Detected declarations: `function sparx5_port_info`.
• 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.