All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>
To: Alex Deucher <alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Alex Deucher <alexander.deucher-5C7GfCeVMHo@public.gmane.org>,
	dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm: return false in drm_arch_can_wc_memory() for ARM
Date: Thu, 20 Dec 2018 16:36:19 +0100	[thread overview]
Message-ID: <20181220153619.GP21184@phenom.ffwll.local> (raw)
In-Reply-To: <20181220145657.304-1-alexander.deucher-5C7GfCeVMHo@public.gmane.org>

On Thu, Dec 20, 2018 at 09:56:57AM -0500, Alex Deucher wrote:
> I'm not familiar enough with ARM to know if write combining
> is actually an architectural limitation or if it's an issue
> with the PCIe IPs used on various platforms, but so far
> everyone that has tried to run radeon hardware on
> ARM has had to disable it.  So let's just make it official.

wc on arm is Really Complicated (tm) afaiui. There's issues with aliasing
mappings and stuff, so you need to allocate your wc memory from special
pools. So probably best to just disable it until we figure this out.
 
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>

> ---
>  include/drm/drm_cache.h | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/include/drm/drm_cache.h b/include/drm/drm_cache.h
> index bfe1639df02d..691b4c4b0587 100644
> --- a/include/drm/drm_cache.h
> +++ b/include/drm/drm_cache.h
> @@ -47,6 +47,8 @@ static inline bool drm_arch_can_wc_memory(void)
>  	return false;
>  #elif defined(CONFIG_MIPS) && defined(CONFIG_CPU_LOONGSON3)
>  	return false;
> +#elif defined(CONFIG_ARM) || defined(CONFIG_ARM64)
> +	return false;
>  #else
>  	return true;
>  #endif
> -- 
> 2.13.6
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2018-12-20 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20 14:56 [PATCH] drm: return false in drm_arch_can_wc_memory() for ARM Alex Deucher
     [not found] ` <20181220145657.304-1-alexander.deucher-5C7GfCeVMHo@public.gmane.org>
2018-12-20 15:36   ` Daniel Vetter [this message]
     [not found]     ` <20181220153619.GP21184-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2018-12-21 14:16       ` Liviu Dudau
     [not found]         ` <20181221141644.GB22341-A/Nd4k6kWRHZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2018-12-21 14:48           ` Alex Deucher
     [not found]             ` <CADnq5_P9VZMhC_4j3F4hqHdD6Ey0=totPuNhF3hYBzkbgHsPpg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-12-21 16:39               ` Eric Anholt

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=20181220153619.GP21184@phenom.ffwll.local \
    --to=daniel-/w4ywyx8dfk@public.gmane.org \
    --cc=alexander.deucher-5C7GfCeVMHo@public.gmane.org \
    --cc=alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.