zynqmp_pm_se...sk_write_reg(9)

📦 version 7.3.1, in nixpkgs unstable

👑 zynqmp_pm_sec_mask_write_reg — from the Kernel API Manual, bestie ✨

Okay so picture this: you're deep in the kernel, you've got a device node staring at you, and you need the PM firmware to write to it securely, with a mask and everything. That's literally this function. It's giving "trusted middleman" energy 💅

🌸 NAME 🌸

zynqmp_pm_sec_mask_write_reg — the PM call that securely writes to a given offset of the node 🫶

✨ SYNOPSIS ✨

int zynqmp_pm_sec_mask_write_reg (const u32 node_id , const u32 offset ,
       u32 mask , u32 value );

Not me obsessing over a four-argument signature 😭 she's compact and she knows it.

🎀 ARGUMENTS 🎀

  • node_id — the Node Id of the device. Like, which device are we talking to, bestie? Gotta name names 💖
  • offset — the offset to be used, and heads up, it's 20-bit. Twenty bits. Precious little offset 🦋
  • mask — the mask to be used. So we're not just blindly writing, we're being selective ✨
  • value — the value to be written. The actual payload, the main character of this whole operation 👑

🔥 RETURN 🔥

Returns 0 on success, or an error value on failure. That's it. Zero means slay, anything else means the vibe check failed 💀

🌈 SEE ALSO 🌈

Kernel file ./drivers/firmware/xilinx/zynqmp.c — and honestly the whole friend group is here, get comfy, this is a long guest list:

Bestie note: yes, zynqmp_pm_sec_read_reg(9) is right there in the list too — the read half of this whole secure-register situation, iykyk 📖✨

Okay that's the whole page, no cap. Sourced from ./drivers/firmware/xilinx, October 2026 edition, and the page itself answers to the name zynqmp_pm_se...sk_write_reg(9) (the terminal truncated her name, she's dramatic like that 😭). Mwah, go forth and write securely 💜🎀🦋

📦 where this page comes from