From mboxrd@z Thu Jan 1 00:00:00 1970 From: robherring2@gmail.com (Rob Herring) Date: Mon, 18 Feb 2013 15:58:26 -0600 Subject: [Linaro-mm-sig] [PATCH 0/2] Device Tree support for CMA (Contiguous Memory Allocator) In-Reply-To: References: <1360845928-8107-1-git-send-email-m.szyprowski@samsung.com> <20130214213013.GG1906@pengutronix.de> <511D6076.9090503@gmail.com> <20130215083304.GK1906@pengutronix.de> <511E6143.609@gmail.com> Message-ID: <5122A402.7030807@gmail.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 02/16/2013 11:18 PM, Nishanth Peethambaran wrote: > Limiting the scope of the product to a particular use-case (720p or > 1080p video playback) will be part of firmware mostly OTP-ed in the > SoC. Firmware author could decide the amount of CMA memory needed and > put this as part of DT. What kernel developer would want a firmware author deciding how much memory is needed? It is not a decision that can be made without knowledge of the OS. While the frame size could be determined easily enough based on resolution, the number of buffers needed cannot. Rob From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [Linaro-mm-sig] [PATCH 0/2] Device Tree support for CMA (Contiguous Memory Allocator) Date: Mon, 18 Feb 2013 15:58:26 -0600 Message-ID: <5122A402.7030807@gmail.com> References: <1360845928-8107-1-git-send-email-m.szyprowski@samsung.com> <20130214213013.GG1906@pengutronix.de> <511D6076.9090503@gmail.com> <20130215083304.GK1906@pengutronix.de> <511E6143.609@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: "devicetree-discuss" To: Nishanth Peethambaran Cc: Sascha Hauer , Michal Nazarewicz , linaro-mm-sig-cunTk1MwBs8s++Sfvej+rw@public.gmane.org, Kyungmin Park , Sylwester Nawrocki , devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: devicetree@vger.kernel.org On 02/16/2013 11:18 PM, Nishanth Peethambaran wrote: > Limiting the scope of the product to a particular use-case (720p or > 1080p video playback) will be part of firmware mostly OTP-ed in the > SoC. Firmware author could decide the amount of CMA memory needed and > put this as part of DT. What kernel developer would want a firmware author deciding how much memory is needed? It is not a decision that can be made without knowledge of the OS. While the frame size could be determined easily enough based on resolution, the number of buffers needed cannot. Rob