ice_dpll_input_state_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

Bestie, this is ice_dpll_input_state_get(9) from the Kernel API Manual β€” the page for getting input pin state on a dpll device. It’s a tiny callback with main-character energy, and we’re keeping every technical detail, no cap. πŸ’–

πŸ’– NAME

ice_dpll_input_state_get β€” get input pin state on dpll device. That’s the whole name-section moment, and it ate. ✨

✨ SYNOPSIS

int ice_dpll_input_state_get (const struct dpll_pin *pin , void
       *pin_priv , const struct dpll_device *dpll , void *dpll_priv , enum
       dpll_pin_state *state , struct netlink_ext_ack *extack );

πŸŽ€ ARGUMENTS

Okay bestie, here’s the cast list β€” every single one matters:

  • pin β€” pointer to a pin
  • pin_priv β€” private data pointer passed on pin registration
  • dpll β€” registered dpll pointer
  • dpll_priv β€” private data pointer passed on dpll registration
  • state β€” on success holds state of the pin
  • extack β€” error reporting

πŸ¦‹ DESCRIPTION

Dpll subsystem callback. Check state of a input pin. That’s literally the whole job β€” it’s giving β€œsmall function, clear purpose,” and I’m obsessed. πŸ¦‹

🌸 CONTEXT

Context tea, periodt: this calls a function which acquires pf->dplls.lock. So yeah, lock acquisition is part of the vibe here. πŸ”₯

πŸ’… RETURN

Two outcomes, no cap:

  • 0 - success
  • negative - failed to get state

πŸ‘‘ SEE ALSO

Okay the friend group is huge, iykyk β€” every single one of these is on the roster:


Source/version energy: ./drivers/net/ethernet/intel/ice. Date stamp: October 2026. That’s the footer tea, bestie β€” now go check that input pin state and slay. πŸ’œ

πŸ“¦ where this page comes from