From mboxrd@z Thu Jan 1 00:00:00 1970 From: aford173@gmail.com (Adam Ford) Date: Thu, 26 Sep 2019 08:09:52 -0500 Subject: [PATCH v2 00/21] Refine memblock API In-Reply-To: References: <1548057848-15136-1-git-send-email-rppt@linux.ibm.com> List-ID: Message-ID: To: linux-snps-arc@lists.infradead.org On Wed, Sep 25, 2019@10:17 AM Fabio Estevam wrote: > > On Wed, Sep 25, 2019@9:17 AM Adam Ford wrote: > > > I tried cma=256M and noticed the cma dump at the beginning didn't > > change. Do we need to setup a reserved-memory node like > > imx6ul-ccimx6ulsom.dtsi did? > > I don't think so. > > Were you able to identify what was the exact commit that caused such regression? I was able to narrow it down the 92d12f9544b7 ("memblock: refactor internal allocation functions") that caused the regression with Etnaviv. I also noticed that if I create a reserved memory node as was done one imx6ul-ccimx6ulsom.dtsi the 3D seems to work again, but without it, I was getting errors regardless of the 'cma=256M' or not. I don't have a problem using the reserved memory, but I guess I am not sure what the amount should be. I know for the video decoding 1080p, I have historically used cma=128M, but with the 3D also needing some memory allocation, is that enough or should I use 256M? adam