zl3073x_out_state_set(9)

📦 version 7.3.1, in nixpkgs unstable

💅 zl3073x_out_state_set(9) — the Kernel API Manual, bestie edition 🎀

Okay so this one's from the kernel API manual (yes, the manual manual, the big serious one) and it's all about pushing your output state changes down into the actual hardware. Let's get into it ✨

🌸 NAME 🌸

zl3073x_out_state_set — the function that actually commits your output state changes to the hardware, no take-backsies 💖

🦋 SYNOPSIS 🦋

int zl3073x_out_state_set (struct zl3073x_dev *zldev , u8 index , const
struct zl3073x_out *out );

Like, that's the whole vibe. Three args, one int back. Slay 💅

🎀 ARGUMENTS 🎀

  • zldev — pointer to the zl3073x_dev structure. This is the device, the main character 👑
  • index — which output you're setting state for. Gotta know which one, bestie 🫶
  • out — the desired output state. The dream. The goal. The moment ✨

🔥 DESCRIPTION 🔥

Okay so here's the whole plot, fr fr:

First up it validates that the invariant fields have not been modified — like, those fields are invariant, they're not supposed to change, so if they did, that's a vibe check fail 😭

Then, if the mutable configuration is literally unchanged? It skips the HW write entirely. Nothing to do, no notes, we stay home 💀

But if stuff did change, it writes only the changed cfg fields to hardware via the mailbox interface. Not all the fields. Just the changed ones. Efficient queen behavior 👑

⭐ RETURN ⭐

  • 0 on success — we ate, no crumbs 💖
  • -EINVAL if invariants changed — nope, invalid, not today 🙈
  • <0 on HW error — hardware said no 😭

🌈 SEE ALSO 🌈

Go read those too, iykyk 🧚

Heads up bestie: -EINVAL means the invariants got messed with, so don't go changing stuff you're not supposed to change, okay? 💜

That's the whole page! 🦋 Brought to you from ./drivers/dpll/zl3073x, dated October 2026, in the Kernel API Manual — mwah, love u, go commit those state changes 💅💖

📦 where this page comes from