From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>
Cc: Alex Deucher <alexdeucher@gmail.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hawking Zhang <Hawking.Zhang@amd.com>,
Huang Rui <ray.huang@amd.com>,
DRI <dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: build failure after merge of the amdgpu tree
Date: Thu, 27 Jun 2019 13:35:27 +1000 [thread overview]
Message-ID: <20190627133527.391ed0a1@canb.auug.org.au> (raw)
In-Reply-To: <20190626212212.25b41df4@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2710 bytes --]
Hi Dave,
On Wed, 26 Jun 2019 21:22:12 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi Alex,
>
> After merging the amdgpu tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> In file included from drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c:25:
> drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c: In function 'gfx_v10_0_cp_gfx_resume':
> drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c:2628:27: error: 'CP_RB1_CNTL__BUF_SWAP_MASK' undeclared (first use in this function); did you mean 'CP_RB_CNTL__BUF_SWAP_MASK'?
> tmp = REG_SET_FIELD(tmp, CP_RB1_CNTL, BUF_SWAP, 1);
> ^~~~~~~~~~~
> drivers/gpu/drm/amd/amdgpu/amdgpu.h:1067:36: note: in definition of macro 'REG_FIELD_MASK'
> #define REG_FIELD_MASK(reg, field) reg##__##field##_MASK
> ^~~
> drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c:2628:8: note: in expansion of macro 'REG_SET_FIELD'
> tmp = REG_SET_FIELD(tmp, CP_RB1_CNTL, BUF_SWAP, 1);
> ^~~~~~~~~~~~~
> drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c:2628:27: note: each undeclared identifier is reported only once for each function it appears in
> tmp = REG_SET_FIELD(tmp, CP_RB1_CNTL, BUF_SWAP, 1);
> ^~~~~~~~~~~
> drivers/gpu/drm/amd/amdgpu/amdgpu.h:1067:36: note: in definition of macro 'REG_FIELD_MASK'
> #define REG_FIELD_MASK(reg, field) reg##__##field##_MASK
> ^~~
> drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c:2628:8: note: in expansion of macro 'REG_SET_FIELD'
> tmp = REG_SET_FIELD(tmp, CP_RB1_CNTL, BUF_SWAP, 1);
> ^~~~~~~~~~~~~
> drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c:2628:27: error: 'CP_RB1_CNTL__BUF_SWAP__SHIFT' undeclared (first use in this function); did you mean 'CP_RB0_CNTL__BUF_SWAP__SHIFT'?
> tmp = REG_SET_FIELD(tmp, CP_RB1_CNTL, BUF_SWAP, 1);
> ^~~~~~~~~~~
> drivers/gpu/drm/amd/amdgpu/amdgpu.h:1066:37: note: in definition of macro 'REG_FIELD_SHIFT'
> #define REG_FIELD_SHIFT(reg, field) reg##__##field##__SHIFT
> ^~~
> drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c:2628:8: note: in expansion of macro 'REG_SET_FIELD'
> tmp = REG_SET_FIELD(tmp, CP_RB1_CNTL, BUF_SWAP, 1);
> ^~~~~~~~~~~~~
>
> Caused by commit
>
> a644d85a5cd4 ("drm/amdgpu: add gfx v10 implementation (v10)")
>
> I have disabled that driver for today. Please let me know when it is
> fixed so that I can enable it again.
I assume that this has now been inherited by the drm tree (since there
has been no fix). So the AMD_GPU driver will still be disabled in
linux-next today as of the drm tree merge.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next parent reply other threads:[~2019-06-27 3:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190626212212.25b41df4@canb.auug.org.au>
2019-06-27 3:35 ` Stephen Rothwell [this message]
2019-06-27 14:18 ` linux-next: build failure after merge of the amdgpu tree Alex Deucher
2019-06-27 22:01 ` Stephen Rothwell
[not found] <20200612102552.2d573ebb@canb.auug.org.au>
2020-06-26 1:47 ` Stephen Rothwell
2021-02-05 2:12 Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2021-07-28 12:34 Mark Brown
2021-09-17 0:57 Stephen Rothwell
2021-12-03 1:11 Stephen Rothwell
[not found] <20220307111342.105ce204@canb.auug.org.au>
[not found] ` <YiYC2fQgf7d/QPSM@sirena.org.uk>
2022-03-08 11:15 ` Noralf Trønnes
2023-05-19 0:06 Stephen Rothwell
2023-05-19 3:10 ` James Zhu
2023-05-19 13:38 ` Alex Deucher
[not found] <20231010124357.5251e100@canb.auug.org.au>
2023-10-19 1:06 ` Stephen Rothwell
2023-10-24 0:59 ` Stephen Rothwell
2023-10-24 12:57 ` Alex Deucher
2023-10-24 19:52 ` Alex Deucher
2023-10-24 21:47 ` Stephen Rothwell
2024-08-19 1:56 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190627133527.391ed0a1@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Hawking.Zhang@amd.com \
--cc=airlied@linux.ie \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ray.huang@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox