From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Tue, 7 Nov 2017 07:48:42 -0800 Subject: n900 in next-20170901 In-Reply-To: <20171107053313.GA12447@js1304-P5Q-DELUXE> References: <20170925145437.GG4394@atomide.com> <20171018082927.GB27595@js1304-P5Q-DELUXE> <20171019183033.GH4394@atomide.com> <20171020015542.GA10438@js1304-P5Q-DELUXE> <20171020173146.GN4394@atomide.com> <20171023045342.GA23082@js1304-P5Q-DELUXE> <20171025173137.GQ4394@atomide.com> <20171026044829.GB11791@js1304-P5Q-DELUXE> <20171026141627.GD21504@atomide.com> <20171107053313.GA12447@js1304-P5Q-DELUXE> Message-ID: <20171107154842.GP28152@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi, * Joonsoo Kim [171107 05:30]: > Could you test follwing updated branch? > > https://github.com/JoonsooKim/linux/tree/cma-debug4-next-20180901 > > It has three relevant commits on top and enables CMA memory use. Okie dokie. > "arm/dma: remove i-cache flush" Your branch at the above commit is not booting on n900. > "arm/dma: flush i-cache and d-cache separately" Not booting at this commit either. > "arm/dma: call flush_cache_all() and don't do outer cache operation" Not booting at this commit either. Earlier commit f14f3479c0d7 ("arm/dma: re-enable to remap the CMA area and flush cache before remapping") in you branch boots. Then the following commit d6512d6d0171 ("Revert "arm/mm: disable atomic_pool"") won't boot. Also your tree at commit 6d0525cef962 ("arm/dma: remove i-cache flush") with only commit d6512d6d0171 ("Revert "arm/mm: disable atomic_pool"") reverted boots on n900. So it seems the issue is currently at the atomic_pool_init() related code? Regards, Tony