ata_acpi_exec_tfs(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ata_acpi_exec_tfs β€” the <pink>Kernel API Manual</pink> entry, bestie edition πŸŽ€

okay so real talk, this is ata_acpi_exec_tfs(9) and it is lowkey the moment ACPI meets your ATA device and they exchange notes. it's giving "get the settings, then write the settings." slay.


✨ SYNOPSIS ✨

int ata_acpi_exec_tfs (struct ata_device *dev , int *nr_executed );

literally that's the whole signature. two args. gorgeous. no cap. πŸ’…


🌸 ARGUMENTS 🌸

  • dev β€” the target ATA device 🎯 like, the actual device we're doing all this for. main character energy fr.
  • nr_executed β€” an out parameter for the number of executed commands. yes bestie, it's an out parameter β€” the function writes back into it so you know how many commands actually got executed. 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

so what does it do? it evaluates _GTF and then executes the taskfiles that came back from it. that's it, that's the vibe. get the taskfile settings, then write them. iconic. ✨

LOCKING: EH context. 🚨 that's the lock context, keep it in mind, iykyk.


πŸ”₯ RETURN πŸ”₯

  • the number of executed taskfiles on success β€” yay πŸŽ‰
  • 0 if _GTF doesn't exist (like, it just wasn't there, no drama, no error)
  • -errno on other errors 😭 so check your negative values okay

⭐ SEE ALSO ⭐

the kernel file lives at ./drivers/ata/libata-acpi.c β€” go look, it's right there πŸ’–

and like, the whole friend group:

all of them. every single one. we don't skip the squad. πŸ‘‘


and that's the page!! love that for us. go forth and evaluate your _GTF responsibly bestie πŸ’œ

mwah πŸ’‹ this has been ./drivers/ata, October 2026, ata_acpi_exec_tfs(9) β€” see you in the next manpage, bye!! πŸŒˆπŸ“

πŸ“¦ where this page comes from