drivers/net/ethernet/mscc/ocelot_police.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/mscc/ocelot_police.h

Extension

.h

Size

1366 bytes

Lines

42

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

• ocelot.h
• net/flow_offload.h

Detected Declarations

• struct qos_policer_conf
• enum mscc_qos_rate_mode

Annotated Snippet

struct qos_policer_conf {
	enum mscc_qos_rate_mode mode;
	bool dlb; /* Enable DLB (dual leaky bucket mode */
	bool cf;  /* Coupling flag (ignored in SLB mode) */
	u32  cir; /* CIR in kbps/fps (ignored in SLB mode) */
	u32  cbs; /* CBS in bytes/frames (ignored in SLB mode) */
	u32  pir; /* PIR in kbps/fps */
	u32  pbs; /* PBS in bytes/frames */
	u8   ipg; /* Size of IPG when MSCC_QOS_RATE_MODE_LINE is chosen */
};

int qos_policer_conf_set(struct ocelot *ocelot, u32 pol_ix,
			 struct qos_policer_conf *conf);

int ocelot_policer_validate(const struct flow_action *action,
			    const struct flow_action_entry *a,
			    struct netlink_ext_ack *extack);

#endif /* _MSCC_OCELOT_POLICE_H_ */

Annotation

• Immediate include surface: `ocelot.h`, `net/flow_offload.h`.
• Detected declarations: `struct qos_policer_conf`, `enum mscc_qos_rate_mode`.
• 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.