ctucan_probe_common(9)

💖 NAME 💖

ctucan_probe_common — the device-type-independent registration call, bestie. Like, it does not care what kind of device you brought to the party; it handles the registration vibe anyway. ✨

🌸 SYNOPSIS 🌸

int ctucan_probe_common (struct device *dev , void __iomem *addr , int
irq , unsigned int ntxbufs , unsigned long can_clk_rate , int
pm_enable_call , void (*set_drvdata_fnc)(struct device *dev, struct
net_device *ndev) );

🎀 ARGUMENTS 🎀

• dev — handle to the generic device structure. It’s the main-character device handle, periodt. 👑
• addr — base address of the CTU CAN FD core address. Yes, that exact phrase; it’s the core’s address home base. 🏠
• irq — the interrupt number. The literal “hey bestie, something happened” number. 🔔
• ntxbufs — number of implemented Tx buffers. Count those Tx buffers, don’t guess. 🔥
• can_clk_rate — clock rate. If it’s 0, then the clock is taken from the device node. No cap, that’s the rule. 🕰️
• pm_enable_call — whether pm_runtime_enable should be called. So it’s basically a yes/no vibe check for that call. ✅
• set_drvdata_fnc — function to set network driver data for the physical device. It’s giving “you provide the setter, I’ll handle the rest” energy. 🫶

🦋 DESCRIPTION 🦋

This function does all the memory allocation and registration for the CAN device. Like, all of it — the allocation and the registration, together, slay. 💅

⭐ RETURN ⭐

0 on success, and a failure value on error. So, success is the iconic 0; anything else is the error vibe telling you something went sideways. 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/net/can/ctucanfd/ctucanfd.h — go look, iykyk. 📚

Source/version cuteness: this page lives under ./drivers/net/can/ctucanfd, and the date on it is October 2026. Stay hydrated, read your headers, and mwah 💋🧚‍♀️