ata_force_link_limits(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, this page is ata_force_link_limits(9) from the Kernel API Manual πŸ’… and the name is literally the whole vibe: ata_force_link_limits β€” force link limits according to libata.force. no cap, that's the function's whole job.

✨ SYNOPSIS ✨

void ata_force_link_limits (struct ata_link *link );

πŸŽ€ ARGUMENTS πŸŽ€

  • link β€” ATA link of interest πŸ‘€

πŸ¦‹ DESCRIPTION πŸ¦‹

So this function forces link flags and the SATA spd limit according to libata.force β€” and it will literally whine about it 😭. That's the mood.

When only the port part is specified (e.g. 1:), the limit applies to all links connected to both the host link and all fan-out ports connected via PMP. yes, all of them πŸ’€.

If the device part is specified as 0 (e.g. 1.00:), it specifies the first fan-out link β€” not the host link. important distinction, bestie πŸ‘‘.

Device number 15 always points to the host link whether PMP is attached or not. always. periodt.

If the controller has slave link, device number 16 points to it. slay for specificity πŸ’….

LOCKING: EH context. πŸ”’

🌈 SEE ALSO 🌈

Kernel file: ./drivers/ata/libata-core.c


okay that's the whole page, bestie 🫢 β€” source/version ./drivers/ata, date October 2026, and yes, the page is ata_force_link_limits(9) βœ¨πŸ’–

πŸ“¦ where this page comes from