iort_dev_find_its_id(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… iort_dev_find_its_id(9) β€” like, the Kernel API Manual page, bestie πŸŽ€

okay so this is a page straight outta the Kernel API Manual, and it's giving "small function, big responsibilities" energy. We're talking iort_dev_find_its_id β€” aka the little guy that goes and finds the ITS identifier for a device. Let's get into it, no cap ✨


🌸 NAME 🌸

iort_dev_find_its_id β€” find the ITS identifier for a device πŸ¦‹

Like, that's literally the whole job. It finds the ITS id. For a device. Iconic behavior honestly.


✨ SYNOPSIS ✨

int iort_dev_find_its_id (struct device *dev , u32 id , unsigned int idx
, int *its_id );

copy that exactly, bestie, spacing and all β€” do NOT let your editor "fix" it πŸ™ˆ


πŸ’– ARGUMENTS πŸ’–

okay so the function takes four things, and each one is doing its own little job:

  • dev β€” the device. yeah. just the device. the main character of this whole operation πŸ‘‘
  • id β€” the device's ID. it's a u32, and it's the ID we're working with.
  • idx β€” the index of the ITS identifier list. so there's a list, and this is which slot in it we care about πŸ”₯
  • its_id β€” the ITS identifier. this is where the ITS id lands 🎯

⭐ RETURN ⭐

0 on success β€” slay πŸ’… β€” and, like, an appropriate error value otherwise 😭 so always check your return value, fr fr.


🌈 SEE ALSO 🌈

the Kernel file ./drivers/acpi/arm64/iort.c and honestly the whole IORT friend group, all showing up to the group chat together 🫢:


🫢 okay that's the whole page, go read the source at ./drivers/acpi/arm64 if you're feeling brave, and remember: iort_dev_find_its_id(9) said hi πŸ’œ

and that's a wrap, bestie β€” this one's from ./drivers/acpi/arm64, dated October 2026, and it will forever be known as iort_dev_find_its_id(9) πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from