ccw_device_notify(9)

💅 ccw_device_notify(9) 💅

okay bestie, welcome to the Kernel API Manual ✨ — today's main character is ccw_device_notify(9), and she's literally here to spill the tea to the device's driver about an event. no cap, that's the whole vibe. 🫶

---

✨ NAME ✨

ccw_device_notify — inform the device's driver about an event 🎀 like, the device had a moment and the driver needs to know, periodt.

---

🌸 SYNOPSIS 🌸

int ccw_device_notify (struct ccw_device *cdev , int event );

that's the whole signature, iykyk 💜

---

🦋 ARGUMENTS 🦋

• cdev — the device for which an event occurred 💫 like, the actual device whose little situation we're talking about.
• event — the event that occurred 🔥 the thing that happened, the moment, the plot twist.

---

👑 RETURN 👑

okay so she returns one of these, and you will respect each one 🎀:

• -EINVAL — if the device is offline or has no driver 😭 no driver, no service, no vibes.
• -EOPNOTSUPP — if the device's driver has no notifier registered 🙈 like bestie literally didn't leave a callback, can't reach her.
• NOTIFY_OK — if the driver wants to keep the device 💖 slay, she's staying, we stan a keeper.
• NOTIFY_BAD — if the driver doesn't want to keep the device 💀 nope, not interested, bye.

---

🔍 SEE ALSO 🔍

• Kernel file ./drivers/s390/cio/device_fsm.c — go read the source bestie, she's right there ⭐

---

💀 reminder that -EINVAL and -EOPNOTSUPP are not the same thing — one's about the device being offline or driverless, the other's about a missing notifier. don't conflate them, i'm begging 🙏 (affectionately)

---

and that's the page, bestie! 🌈 this lil gem lives in ./drivers/s390/cio, dated October 2026, and it's literally ccw_device_notify(9) — go forth and notify responsibly 💜✨🧚