From: Luan Arcanjo
All dce command_table_helper's shares a copy-pasted collection
of copy-pasted functions, which are: phy_id_to_atom,
clock_source_id_to_atom_phy_clk_src_id, and engine_bp_to_atom.
This patch removes the multiple copy-pasted by creating a
common command table and make the comman
Hi Christian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING on drm/drm-next drm-exynos/exynos-drm-next
linus/master drm-intel/for-linux-next drm-intel/for-linux-next-fixes
drm-misc/drm-misc-next drm-tip/drm-tip v
On several HP models (tested on HP 3125 and HP Probook 455 G2),
spurious unplug events are emitted upon login on Chrome OS.
This is likely due to the way Chrome OS restarts graphics
upon login, so it's possible it's an issue on other
distributions but not as common, though I haven't
reproduced the
'struct pci_device_id' is not modified in this driver.
Constifying this structure moves some data to a read-only section, so
increase overall security.
On a x86_64, with allmodconfig:
Before:
==
textdata bss dec hex filename
11984 28672 44 407009efc drivers/g
Hi Dave, Simona,
One last minute patch to fix a regression.
The following changes since commit 7013a8268d311fded6c7a6528fc1de82668e75f6:
drm/amd: Fix initialization mistake for NBIO 7.7.0 (2024-11-12 17:37:39 -0500)
are available in the Git repository at:
https://gitlab.freedesktop.org/agd
smu->workload_mask is IP specific and should not be messed with in
the common code. The mask bits vary across SMU versions.
Move all handling of smu->workload_mask in to the backends and
simplify the code. Store the user's preference in smu->power_profile_mode
which will be reflected in sysfs. F
This reverts commit 8cc438be5d49b8326b2fcade0bdb7e6a97df9e0b.
The handling in smu_switch_power_profile() is broken for
navi3x which results in the last setting from that always
being set. Since a more extensive fix is available, revert.
Link: https://gitlab.freedesktop.org/drm/amd/-/issues/3618
S
Clang on LoongArch (18+) appears to be unaffected by the bug causing
excessive stack usage in calculate_bandwidth(). But when building DC_FP
support the stack frame size can be as large as 2816 bytes, which causes
the FRAME_WARN build warnings. So on LoongArch we allow building DC with
clang, but d
Hi,
在 2024/11/13 23:17, Chuck Lever 写道:
On Mon, Nov 11, 2024 at 11:20:17PM +0800, yangerkun wrote:
在 2024/11/11 22:39, Chuck Lever III 写道:
On Nov 10, 2024, at 9:36 PM, Yu Kuai wrote:
I'm in the cc list ,so I assume you saw my set, then I don't know why
you're ignoring my concerns.
1) nex
