zl3073x_flash_block(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 zl3073x_flash_block 💅

okay so bestie, welcome to the Kernel API Manual ✨ this one's a kernel function, and it's called zl3073x_flash_block — say that three times fast, I dare you 😭

💖 NAME

zl3073x_flash_block — downloads a memory block and flashes it, no cap 🔥

✨ SYNOPSIS

int zl3073x_flash_block (struct zl3073x_dev *zldev , const char
*component , u32 operation , u32 page , u32 addr , const void *data ,
size_t size , struct netlink_ext_ack *extack );

like… that's a lot of arguments, but she handles it, main character energy 👑

🦋 ARGUMENTS

  • zldev — the zl3073x device structure 🫶 your actual device, bestie
  • component — component name, literally just the name of the thing
  • operation — the flash operation to perform, like which move we're doing 💅
  • page — destination flash page 🎀 that's where it's going
  • addr — device memory address to load data, i.e. where the data goes first
  • data — pointer to the data to be flashed ✨ the actual payload
  • size — size of data, yes we need to know how much 📏
  • extack — netlink extack pointer to report errors, so when things go wrong (and they might 😭) it gets reported properly

🌸 DESCRIPTION

So here's the vibe: the function downloads the memory block given by the data pointer and the size size, and flashes it into internal memory on flash page page 🔥

The internal flash operation that the firmware actually performs? That's specified by the operation parameter 💫 so like, operation is the one calling the shots, iykyk.

⭐ RETURN

  • 0 on success — slay, we ate 💅
  • <0 on error — not slay, something went wrong 😭

🌈 SEE ALSO

Kernel file ./drivers/dpll/zl3073x/flash.c and the whole friend group:

bestie reminder: all of these live in ./drivers/dpll/zl3073x — go read them, they're iconic 👑

anyway that's the page! 🧚 from ./drivers/dpll/zl3073x, dated October 2026, this has been zl3073x_flash_block(9) — mwah, go flash something responsibly 💜🍓

📦 where this page comes from