Skip to content

Experimental Loongson3 CPUFreq ABIv1 driver #11270

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: stable
Choose a base branch
from

Conversation

ziyao233
Copy link
Member

@ziyao233 ziyao233 commented Jun 4, 2025

Topic Description

  • linux-kernel: Support cpufreq on Loongson 3 with older SMC firmware
    Introduces the experimental downstream patch for CPUFreq support on
    Loongson 3 machines with older SMC firmware (CMD_GET_VERSION returns 0
    instead of a value greater than 0).
    Signed-off-by: Yao Zi [email protected]

Package(s) Affected

  • linux-kernel-${__VER}: 6.14.9-3

Security Update?

No

Build Order

#buildit linux-kernel

Test Build(s) Done

Primary Architectures

  • LoongArch 64-bit loongarch64

Introduces the experimental downstream patch for CPUFreq support on
Loongson 3 machines with older SMC firmware (CMD_GET_VERSION returns 0
instead of a value greater than 0).

Signed-off-by: Yao Zi <[email protected]>
@ziyao233 ziyao233 added the preview Topic/issue involves a long-term testing and is intended to preview new features/changes label Jun 4, 2025
@xry111
Copy link
Contributor

xry111 commented Jun 6, 2025

I really don't like the terminology "ABIv1."

Those pairs are in fact, completely different and orthogonal concepts:

  • Downstream "Linux 4.19.0" UAPI vs. Linux 5.19.0 UAPI
  • Stack-based relocs vs. relocs directly operating on the immediate slot
  • BPI vs. UEFI
  • SMC shipped with current HW vs. SMC implementing the interface expected by the upstream kernel
  • Maybe others...

Mixing up those concepts into "ABIv1" vs "ABIv2" has already caused many misunderstandings.

@ziyao233
Copy link
Member Author

ziyao233 commented Jun 7, 2025 via email

@ziyao233
Copy link
Member Author

ziyao233 commented Jun 7, 2025

@KatyushaScarlet reported that the CPUFreq driver causes frequently amdgpu resets on TongFang L820-T2 when using amdgpu instead of radeon driver. I'll dig it further later.

@KatyushaScarlet
Copy link
Member

@KatyushaScarlet reported that the CPUFreq driver causes frequently amdgpu resets on TongFang L820-T2 when using amdgpu instead of radeon driver. I'll dig it further later.

  1. Log 1: After unlocking the screen in KDE6 and clicking the tray icon, the desktop froze, blinked, and reported a GPU reset.
    dmesg-l860-t2-amdgpu-reset-6.14.9-log1.log

  2. Log 2: After reproducing the same steps, the GPU reset occurred. I then removed the loongson3_cpufreq driver using rmmod, and the GPU stopped resetting. However, when I reinserted the driver using modprobe, the GPU reset again.
    dmesg-l860-t2-amdgpu-reset-6.14.9-log2.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
preview Topic/issue involves a long-term testing and is intended to preview new features/changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants