drivers/net/ethernet/marvell/prestera/prestera_span.h
Source file repositories/reference/linux-study-clean/drivers/net/ethernet/marvell/prestera/prestera_span.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/ethernet/marvell/prestera/prestera_span.h- Extension
.h- Size
- 694 bytes
- Lines
- 25
- 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
net/pkt_cls.h
Detected Declarations
struct prestera_portstruct prestera_switchstruct prestera_flow_block_binding
Annotated Snippet
#ifndef _PRESTERA_SPAN_H_
#define _PRESTERA_SPAN_H_
#include <net/pkt_cls.h>
#define PRESTERA_SPAN_INVALID_ID -1
struct prestera_port;
struct prestera_switch;
struct prestera_flow_block_binding;
int prestera_span_init(struct prestera_switch *sw);
void prestera_span_fini(struct prestera_switch *sw);
int prestera_span_rule_add(struct prestera_flow_block_binding *binding,
struct prestera_port *to_port,
bool ingress);
int prestera_span_rule_del(struct prestera_flow_block_binding *binding,
bool ingress);
#endif /* _PRESTERA_SPAN_H_ */
Annotation
- Immediate include surface: `net/pkt_cls.h`.
- Detected declarations: `struct prestera_port`, `struct prestera_switch`, `struct prestera_flow_block_binding`.
- 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.