pccard_loop_tuple(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

pccard_loop_tuple β€” loop over tuples in the CIS. This one's from the Kernel API Manual (and yes, bestie, this is pccard_loop_tuple(9) πŸ’…), and it's literally the helper that walks the CIS like it's strutting down a runway βœ¨πŸ¦‹.

🌸 SYNOPSIS 🌸

int pccard_loop_tuple (struct pcmcia_socket *s , unsigned int function ,
cisdata_t code , cisparse_t *parse , void *priv_data , int (*loop_tuple)
(tuple_t *tuple, cisparse_t *parse, void *priv_data) );

πŸŽ€ ARGUMENTS πŸŽ€

  • s β€” the struct pcmcia_socket where the card is inserted πŸ’³ (yes, the socket, keep up 😌)
  • function β€” the device function we loop for πŸ”
  • code β€” which CIS code shall we look for? πŸ”Ž
  • parse β€” buffer where the tuple shall be parsed (or NULL, if no parse) 🫧
  • priv_data β€” private data to be passed to the loop_tuple function πŸŽ’
  • loop_tuple β€” function to call for each CIS entry of type function. IT gets passed the raw tuple, the paresed tuple (if parse is set β€” yes bestie, that's the source's spelling 😭) and priv_data ✨

πŸ”₯ DESCRIPTION πŸ”₯

Okay so bestie, pccard_loop_tuple loops over all CIS entries of type function, and calls the loop_tuple function for each entry. If the call to loop_tuple returns 0, the loop exits β€” periodt πŸ’…. Returns 0 on success or errorcode otherwise.

The callback returning 0 is the stop signal πŸ›‘ β€” that's the whole vibe check. The function itself returns 0 on success or errorcode otherwise, no cap.

πŸ¦‹ SEE ALSO πŸ¦‹


Signed with love from the ./drivers/pcmcia source πŸ’Œ β€” Kernel API Manual, October 2026, pccard_loop_tuple(9) 🫢✨

πŸ“¦ where this page comes from