drivers/net/dsa/realtek/rtl8366rb.c

File Facts

System

Linux kernel

Corpus path

drivers/net/dsa/realtek/rtl8366rb.c

Extension

.c

Size

56784 bytes

Lines

1902

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/bitops.h
• linux/etherdevice.h
• linux/if_bridge.h
• linux/if_vlan.h
• linux/interrupt.h
• linux/irqdomain.h
• linux/irqchip/chained_irq.h
• linux/of_irq.h
• linux/regmap.h
• linux/string_choices.h
• realtek.h
• realtek-smi.h
• realtek-mdio.h
• rtl83xx.h
• rtl8366rb.h

Detected Declarations

• struct rtl8366rb_jam_tbl_entry
• function rtl8366rb_get_mib_counter
• function rtl8366rb_get_irqmask
• function rtl8366rb_mask_irq
• function rtl8366rb_unmask_irq
• function rtl8366rb_irq
• function rtl8366rb_irq_map
• function rtl8366rb_irq_unmap
• function rtl8366rb_setup_cascaded_irq
• function rtl8366rb_set_addr
• function rtl8366rb_jam_table
• function rb8366rb_set_ledgroup_mode
• function rtl8366rb_setup_all_leds_off
• function rtl8366rb_setup
• function of_machine_is_compatible
• function rtl8366_get_tag_protocol
• function rtl8366rb_phylink_get_caps
• function rtl8366rb_mac_config
• function rtl8366rb_mac_link_down
• function rtl8366rb_port_enable
• function rtl8366rb_port_disable
• function rtl8366rb_port_bridge_join
• function rtl8366rb_port_bridge_leave
• function rtl8366rb_drop_untagged
• function rtl8366rb_vlan_filtering
• function rtl8366rb_port_pre_bridge_flags
• function rtl8366rb_port_bridge_flags
• function rtl8366rb_port_stp_state_set
• function rtl8366rb_port_fast_age
• function rtl8366rb_change_mtu
• function rtl8366rb_max_mtu
• function rtl8366rb_get_vlan_4k
• function rtl8366rb_set_vlan_4k
• function rtl8366rb_get_vlan_mc
• function rtl8366rb_set_vlan_mc
• function rtl8366rb_get_mc_index
• function rtl8366rb_set_mc_index
• function rtl8366rb_is_vlan_valid
• function rtl8366rb_enable_vlan
• function rtl8366rb_enable_vlan4k
• function rtl8366rb_phy_read
• function rtl8366rb_phy_write
• function rtl8366rb_reset_chip
• function rtl8366rb_detect
• function rtl8366rb_init
• function rtl8366rb_exit
• module init rtl8366rb_init

Annotated Snippet

module_init(rtl8366rb_init);

static void __exit rtl8366rb_exit(void)
{
	realtek_smi_driver_unregister(&rtl8366rb_smi_driver);
	realtek_mdio_driver_unregister(&rtl8366rb_mdio_driver);
}
module_exit(rtl8366rb_exit);

MODULE_AUTHOR("Linus Walleij <linus.walleij@linaro.org>");
MODULE_DESCRIPTION("Driver for RTL8366RB ethernet switch");
MODULE_LICENSE("GPL");
MODULE_IMPORT_NS("REALTEK_DSA");

Annotation

• Immediate include surface: `linux/bitops.h`, `linux/etherdevice.h`, `linux/if_bridge.h`, `linux/if_vlan.h`, `linux/interrupt.h`, `linux/irqdomain.h`, `linux/irqchip/chained_irq.h`, `linux/of_irq.h`.
• Detected declarations: `struct rtl8366rb_jam_tbl_entry`, `function rtl8366rb_get_mib_counter`, `function rtl8366rb_get_irqmask`, `function rtl8366rb_mask_irq`, `function rtl8366rb_unmask_irq`, `function rtl8366rb_irq`, `function rtl8366rb_irq_map`, `function rtl8366rb_irq_unmap`, `function rtl8366rb_setup_cascaded_irq`, `function rtl8366rb_set_addr`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: integration implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.