pcmcia_loop_tuple(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– pcmcia_loop_tuple(9) πŸ’–

okay bestie, welcome to the Kernel API Manual ✨ this one is all about looping over tuples in the CIS, and it is lowkey iconic πŸŽ€


🌸 NAME 🌸

pcmcia_loop_tuple β€” loop over tuples in the CIS πŸ’…

✨ SYNOPSIS ✨

int pcmcia_loop_tuple (struct pcmcia_device *p_dev , cisdata_t code ,
int (*loop_tuple) (struct pcmcia_device *p_dev, tuple_t *tuple, void
*priv_data) , void *priv_data );

πŸŽ€ ARGUMENTS πŸŽ€

  • p_dev β€” the struct pcmcia_device which we need to loop for. like, this is the device we're digging through, no cap 🫢
  • code β€” which CIS code shall we look for? bestie, you gotta pick one πŸ”
  • loop_tuple β€” function to call for each CIS entry of type function. IT gets passed the raw tuple and priv_data. yes queen, every single entry gets the callback treatment πŸ’–
  • priv_data β€” private data to be passed to the loop_tuple function. your lil backpack of extra info πŸŽ’

πŸ¦‹ DESCRIPTION πŸ¦‹

pcmcia_loop_tuple loops over all CIS entries of type function, and calls the loop_tuple function for each entry. so it's literally going one by one and handing each entry to your callback ✨

if the call to loop_tuple returns 0, the loop exits. that's the stop signal, bestie πŸ›‘

returns 0 on success or errorcode otherwise. so 0 is the slay outcome, and anything else is giving error 😭

🌈 SEE ALSO 🌈


mwah πŸ’‹ this cutie lives in ./drivers/pcmcia, dated October 2026, and it's literally pcmcia_loop_tuple(9) β€” periodt πŸ«ΆπŸ‘‘

πŸ“¦ where this page comes from