STRUCT SLIM_SCHED(9)

🌸 NAME 🌸

okay so this is the struct slim_sched(9) page from the Kernel API Manual, and it's very much giving “internal scheduling support.” struct slim_sched — the framework uses this structure internally for scheduling. no cap, that's the whole flex. 💅

✨ SYNOPSIS ✨

here's the shape of it, bestie — literally exact:

struct slim_sched {
    enum slim_clk_state     clk_state;
    struct completion       pause_comp;
    struct mutex            m_reconf;
 };

🧚 Members 🧚

• clk_state — the controller's clock state, straight from enum slim_clk_state. ⏰
• pause_comp — signals completion of the clock pause sequence. This is useful when a client tries to call a SLIMbus transaction when the controller is entering clock pause. 🛑
• m_reconf — this mutex is held until current reconfiguration (data channel scheduling, message bandwidth reservation) is done. Message APIs can use the bus concurrently when this mutex is held since elemental access messages can be sent on the bus when reconfiguration is in progress. 🔒

💜 SEE ALSO 💜

Kernel file ./drivers/slimbus/slimbus.h — and here's the whole squad, bestie:

• struct slim_framer(9)
• struct slim_msg_txn(9)
• enum slim_clk_state(9)
• enum slim_port_direction(9)
• enum slim_port_state(9)
• enum slim_channel_state(9)
• enum slim_ch_data_fmt(9)
• enum slim_ch_aux_bit_fmt(9)
• struct slim_channel(9)
• struct slim_port(9)
• enum slim_transport_protocol(9)
• struct slim_stream_runtime(9)
• struct slim_controller(9)

k bye bestie, mwah 💋 — source/version is ./drivers/slimbus, date is October 2026, and the page is struct slim_sched(9) ✨🫶