From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932848AbcCCWwp (ORCPT ); Thu, 3 Mar 2016 17:52:45 -0500 Received: from mail.kernel.org ([198.145.29.136]:42812 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932306AbcCCWwo (ORCPT ); Thu, 3 Mar 2016 17:52:44 -0500 Date: Thu, 3 Mar 2016 16:52:40 -0600 From: Rob Herring To: Vinayak Menon Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, frowand.list@gmail.com, grant.likely@linaro.org, m.szyprowski@samsung.com, vinayakm.list@gmail.com Subject: Re: [PATCH] of: alloc anywhere from memblock if range not specified Message-ID: <20160303225240.GA17541@rob-hp-laptop> References: <1456148744-7583-1-git-send-email-vinmenon@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1456148744-7583-1-git-send-email-vinmenon@codeaurora.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 22, 2016 at 07:15:44PM +0530, Vinayak Menon wrote: > early_init_dt_alloc_reserved_memory_arch passes end as 0 to > __memblock_alloc_base, when limits are not specified. But > __memblock_alloc_base takes end value of 0 as MEMBLOCK_ALLOC_ACCESSIBLE > and limits the end to memblock.current_limit. This results in regions > never being placed in HIGHMEM area, for e.g. CMA. > Let __memblock_alloc_base allocate from anywhere in memory if limits are > not specified. > > Acked-by: Marek Szyprowski > Signed-off-by: Vinayak Menon Applied and marked for stable. Rob