Bug 103129 - drm-tip doesn't compile due to redefining ci_send_msg_to_smc
Summary: drm-tip doesn't compile due to redefining ci_send_msg_to_smc
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: XOrg git
Hardware: All All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-06 21:25 UTC by Fei Yang
Modified: 2019-11-19 08:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Fei Yang 2017-10-06 21:25:26 UTC
The following commit introduced another implementation of ci_send_msg_to_smc() which is causing compile issue with allyesconfig.
 
commit 9f4b35411cfed96d4f9f092b2fed14905af84d89
Author: Rex Zhu <Rex.Zhu@amd.com>
Date:   Fri Sep 8 19:34:33 2017 +0800

    drm/amd/powerplay: add CI asics support to smumgr (v3)
    
    This ports support for CI asics (Bonaire, Hawaii)
    to the powerplay smumgr
    
    v2: warning fix (Alex)
    v3: squash in fix for thermal (Tom)
    
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Rex Zhu <Rex.Zhu@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

To reproduce the issue:
checkout the latest drm-tip
make allyesconfig
make

...
drivers/gpu/drm/amd/powerplay/smumgr/ci_smc.o: In function `ci_send_msg_to_smc':
ci_smc.c:(.text+0xea0): multiple definition of `ci_send_msg_to_smc'
drivers/gpu/drm/radeon/ci_smc.o:ci_smc.c:(.text+0x300): first defined here
make: *** [vmlinux] Error 1
Comment 1 Martin Peres 2019-11-19 08:24:45 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/244.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.