NCT(4)

📦 version 11.0, in nixpkgs unstable

NCT(4) 💅

okay bestie, welcome to the NCT(4) page from the Kernel Interfaces Manual — manual name folded in right here like a cute little name tag ✨. This one is all about the Nuvoton NCT5104D SuperIO driver, and we're keeping every detail, no cap.

🌸 NAME 🌸

nct — Nuvoton NCT5104D SuperIO driver 🦋

🎀 SYNOPSIS 🎀

Here's the config vibe, bestie — exact lines:

nct0 at isa? port ?
nct0 at isa? port 0x2e
nct0 at isa? port 0x4e
gpio* at nct?

✨ DESCRIPTION ✨

The nct driver supports the GPIO functions of the NCT5104D. It does not support the watchdog function of the chip. The chip's UARTs are driven by the com(4) driver. periodt 💅

Heads up: the probe routine for this device is invasive. It's giving nosy 😭.

The chip will be probed for only if the device is configured into the kernel with a fixed port number (0x2e or 0x4e), or if running on a system that is known to have a NCT5104D, such as the PC Engines APU line of systems.

GPIO pins on this chip are shared with the 3rd UART, 4th UART, a clock input line, and the watchdog timer. If any of these functions have been enabled by the BIOS, the nct driver will not take control of the corresponding GPIO lines. At attach time, the driver logs which of the 17 GPIO lines are enabled.

🦋 SEE ALSO 🦋

💜 HISTORY 💜

The nct driver first appeared in NetBSD 10. iconic behavior 👑

💀 CAVEATS 💀

If the chip has not been configured in a complete and accurate manner by the BIOS, GPIO lines may be needlessly disabled. 💀

source/version: Debian; date: December 21, 2020 — that's the footer tea, bestie, mwah 🫶

📦 where this page comes from