hpt36x_init_one(9)

💅 hpt36x_init_one(9) — like, the whole kernel API manual vibe, bestie

okay so this is a page straight outta the Kernel API Manual, and it's about waking up an HPT366/368 chip. buckle up 🎀

---

✨ NAME ✨

hpt36x_init_one — initialise an HPT366/368 🧚

---

🌸 SYNOPSIS 🌸

int hpt36x_init_one (struct pci_dev *dev , const struct pci_device_id *id );

---

🦋 ARGUMENTS 🦋

• dev — the PCI device, the actual main character of this whole situation 💅
• id — the entry in the match table, like its little name tag at the party 🎀

---

🔥 DESCRIPTION 🔥

Initialise an HPT36x device. and ngl, there are some interesting complications here bestie, it's giving plot twist 😭

First up: the chip may report 366 and still be one of several variants. like, it's not being shady on purpose, it just has range ✨

Second: all the timings depend on the clock for the chip, which we must detect and look up. no cap, you gotta go find it 👑

Here's the known chip mapping, fr fr. It may be missing a couple of later releases — so like, don't come for it 🙈

• HPT366 — Chip version 4 (HPT366), PCI Rev 0, Notes: UDMA66
• HPT366 — Chip version 4 (HPT366), PCI Rev 1, Notes: UDMA66
• HPT368 — Chip version 4 (HPT366), PCI Rev 2, Notes: UDMA66
• HPT37x/30x — Chip version 4 (HPT366), PCI Rev 3+, Notes: Other driver

so yeah, rev 3+ of the 4 (HPT366) vibe? that's somebody else's problem, it's a whole other driver 💀

---

⭐ SEE ALSO ⭐

Kernel file ./drivers/ata/pata_hpt366.c — and the whole friend group:

• hpt36x_find_mode(9)
• hpt366_filter(9)
• hpt366_set_piomode(9)
• hpt366_set_dmamode(9)
• hpt366_prereset(9)
• hpt36x_init_chipset(9)

---

🫶 that's the whole page, bestie. no gatekeeping, every option and every flag is right there, iykyk.

and for the sign-off: this one lives in ./drivers/ata, dated October 2026, and it's an official hpt36x_init_one(9) situation. slay 💖✨