STRUCT MT7621_PCIE(9)

🌸 NAME 🌸

struct mt7621_pcie — the PCIe host info, bestie. That's literally it, that's the whole vibe. It's the little struct that holds everything the MediaTek MT7621 PCIe controller needs to know about itself 👑

This page lives in section 9 of the Kernel API Manual, so like… kernel-internals territory, iykyk 🎀

✨ SYNOPSIS ✨

struct mt7621_pcie {
    struct device *dev;
    void __iomem *base;
    struct list_head ports;
    bool resets_inverted;
 };

Four members, no notes, no cap. Copy it exactly, don't be out here free-styling the field names 💅

🫶 Members 🫶

Ok so here's the group chat roll call for every single field, and yes every one matters:

• dev — Pointer to the PCIe device. Like, the actual struct device pointer, not a copy, not a vibe. A pointer. 🔥
• base — The IO Mapped Register Base. This is your void __iomem *, so like, treat it with respect — it's memory-mapped I/O and it's giving main character energy.
• ports — Pointer to PCIe port information. It's a struct list_head, so it's a linked list node, and it's holding onto all the port deets for you 🦋
• resets_inverted — Depends on chip revision: reset lines are inverted. Yes, depends on chip revision. A bool. So some chips say "inverted" and some say "not inverted" and you have to actually check before you assume. Not me finding this out the hard way 😭

Real talk: the whole resets_inverted situation is chip-revision-dependent, so pls pls pls don't hardcode an assumption about it. That's the entire point of the field existing 💀

👑 SEE ALSO 👑

• Kernel file ./drivers/pci/controller/pcie-mt7621.c
• struct mt7621_pcie_port(9) — the port-side counterpart, go read it next, you'll be obsessed 🌈

That's the whole page, bestie, you ate it up ⭐ — this one came straight out of ./drivers/pci/controller and it's dated October 2026, page struct mt7621_pcie(9). Periodt 💖🌸✨