Skip to main content

Linux Upstream Hardware Support Status

This page tracks the support status of Loongson platform-related hardware in the upstream Linux kernel. In the following tables, the conventions are:

  • Version: Supported from this Linux version
  • OK: Uses standard interfaces, no additional support needed
  • WIP: Patches exist but not yet merged upstream
  • TODO: Functionality exists but no patches available
  • N/A: Hardware does not support this feature
  • ?: Lack of data (no information submitted yet, contributions welcome!)

CPU Support Status​

Feature3A50003A60003C6000
SMTN/A6.56.5
AVECN/AN/A6.12
LCL (CPU PCIe)N/AN/AOK
LSX6.56.56.5
LASXOK (same as LSX)OK (same as LSX)OK (same as LSX)
LBT6.66.66.6
LVZ (KVM)6.76.76.7
HWMonWIPWIPWIP
CPUFreq16.116.116.11
Feature2K1000LA2K15002K20002K03002K05002K3000/3B6000M2
SMTN/AN/AN/AN/AN/A?
AVECN/AN/AN/AN/AN/A?
LCL (CPU PCIe)N/AN/AN/AN/AN/A?
LSX6.5?6.5??6.5
LASXN/AN/AN/AN/AN/AOK (same as LSX)
LBTN/AN/AN/AN/AN/A?
LVZ (KVM)N/AN/AN/AN/AN/A?
HWMon??????
CPUFreq1??????

Bridge Chip Support Status​

Feature7A10007A2000
RTC (UEFI)3OKOK
RTC (Native)36.56.5
GPIO6.46.4
I2C6.36.3
Ethernet5.14WIP
OHCI USB1.1OKOK
EHCI USB2.0OKOK
XHCI USB3.0N/AOK
GPUTODOTODO
DC6.66.6
HDA6.56.5
AC97TODON/A
I2SN/A6.5
SATAOKOK
PCIEOKOK
SPI6.66.6
LPCTODOTODO
IOMMUN/AWIP

Footnotes​

  1. The cpufreq operations on the Loongson platform largely rely on the management core (usually a small LA132 core) to assist in execution. The system program on the main core communicates with the RTOS on the management core to indirectly achieve control, so the management core firmware communication protocol is an ABI boundary that needs to consider compatibility. Similar to the Old and New World issues in the Loongson Linux ecosystem, the CPUFreq driver also has two versions, and the mainstream off-the-shelf hardware generally carries a management core firmware communication protocol that is incompatible with the Linux upstream driver implementation. Some domestic Linux distributions' Linux forks integrate the old protocol, such as deepin, openEuler 甲 乙, and openAnolis (with a submission history similar to openEuler), for reference. ↩ ↩2

  2. This model has not been officially released or even fully developed, so all related content is based on reasonable speculation from currently available public information. "Are We Loong Yet?" is not responsible for the accuracy of this information. ↩

  3. In Loongson systems following the UEFI specification, the RTC can be operated through UEFI standard interfaces or by directly reading and writing related registers, but there is only one hardware resource. The native RTC driver is more for non-EFI Loongson systems, such as embedded devices booting with DT. ↩ ↩2