Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750752AbcJSW4O (ORCPT ); Wed, 19 Oct 2016 18:56:14 -0400 Received: from ec2-52-27-115-49.us-west-2.compute.amazonaws.com ([52.27.115.49]:48738 "EHLO s-opensource.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750778AbcJSW4M (ORCPT ); Wed, 19 Oct 2016 18:56:12 -0400 Subject: Re: exynos-drm: display manager fails to start without IOMMU problem To: Tobias Jakobi , Inki Dae , jy0922.shim@samsung.com, sw0312.kim@samsung.com, kyungmin.park@samsung.com, airlied@linux.ie, kgene@kernel.org, Krzysztof Kozlowski References: <1470850251-9150-1-git-send-email-shuahkh@osg.samsung.com> <57ABB1ED.1080301@samsung.com> <57ABB31E.1070802@osg.samsung.com> <57AE0736.6020705@osg.samsung.com> <57AE0CCB.1010708@osg.samsung.com> <57B29925.4020600@samsung.com> <1b2c3b31-7127-af2f-18a2-f3a28567e28d@osg.samsung.com> <2173cc13-7c77-1a38-501d-2c0f522ff5d5@osg.samsung.com> <58079E16.50302@math.uni-bielefeld.de> Cc: dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org, Shuah Khan From: Shuah Khan Message-ID: <0a9b3996-38fb-e4f1-1e25-436f0f09f510@osg.samsung.com> Date: Wed, 19 Oct 2016 16:56:08 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <58079E16.50302@math.uni-bielefeld.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 785 Lines: 28 On 10/19/2016 10:23 AM, Tobias Jakobi wrote: > Hello Shuah, > > just a short note that more misleading comments about default allocation > flags can be found in libdrm. > > https://cgit.freedesktop.org/mesa/drm/tree/exynos/exynos_drm.c > > See e.g. the comment for exynos_bo_create(). > > In my opinion, the whole approach to _set_ a bit to get non-contigious > memory is messed up. It would make more sense to me to set a bit to > request an additional property (here "being contiguous") of the memory. > > Anyway, clearing up this situation is highly appreciated! > > More comments below. > > With best wishes, > Tobias > Hi Tobias, Thanks for the note. Yes the comments are confusing. It seems like some old assumptions are persisting. I will fix these as well. -- Shuah