From: Huang Rui <ray.huang@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: <amd-gfx@lists.freedesktop.org>,
Alex Deucher <alexander.deucher@amd.com>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] drm/amdgpu/gfx6: properly cache mc_arb_ramcfg
Date: Mon, 5 Jun 2017 15:41:02 +0800 [thread overview]
Message-ID: <20170605074101.GA23929@hr-amur2> (raw)
In-Reply-To: <1496435611-11611-1-git-send-email-alexander.deucher@amd.com>
On Fri, Jun 02, 2017 at 04:33:31PM -0400, Alex Deucher wrote:
> This was missing for gfx6.
>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> Cc: stable@vger.kernel.org
Acked-by: Huang Rui <ray.huang@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/gfx_v6_0.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v6_0.c b/drivers/gpu/drm/amd/amdgpu/gfx_v6_0.c
> index 1351f92..c2b4e9f 100644
> --- a/drivers/gpu/drm/amd/amdgpu/gfx_v6_0.c
> +++ b/drivers/gpu/drm/amd/amdgpu/gfx_v6_0.c
> @@ -1475,7 +1475,8 @@ static void gfx_v6_0_gpu_init(struct amdgpu_device *adev)
> WREG32(mmBIF_FB_EN, BIF_FB_EN__FB_READ_EN_MASK | BIF_FB_EN__FB_WRITE_EN_MASK);
>
> mc_shared_chmap = RREG32(mmMC_SHARED_CHMAP);
> - mc_arb_ramcfg = RREG32(mmMC_ARB_RAMCFG);
> + adev->gfx.config.mc_arb_ramcfg = RREG32(mmMC_ARB_RAMCFG);
> + mc_arb_ramcfg = adev->gfx.config.mc_arb_ramcfg;
>
> adev->gfx.config.num_tile_pipes = adev->gfx.config.max_tile_pipes;
> adev->gfx.config.mem_max_burst_length_bytes = 256;
> --
> 2.5.5
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2017-06-05 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 20:33 [PATCH] drm/amdgpu/gfx6: properly cache mc_arb_ramcfg Alex Deucher
2017-06-05 7:41 ` Huang Rui [this message]
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=20170605074101.GA23929@hr-amur2 \
--to=ray.huang@amd.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
/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