From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hiroshi Doyu Subject: Re: Tegra DRM device tree bindings Date: Thu, 28 Jun 2012 09:18:53 +0300 Message-ID: <20120628091853.d4c3d85749f9d41a5dfafd28@nvidia.com> References: <20120626160224.40ba10a26e3dd3a56b1f312c@nvidia.com> <20120626140033.GC1115@avionic-0098.mockup.avionic-design.de> <23B010BBA481A74B98487467C29BA57BF2361DA3AA@HKMAIL01.nvidia.com> <4FEA6E09.30800@nvidia.com> <23B010BBA481A74B98487467C29BA57BF2361DA3C4@HKMAIL01.nvidia.com> <4FEA7472.7050201@nvidia.com> <20120627051418.GB7177@avionic-0098.mockup.avionic-design.de> <20120627155907.871b2a506374b7db14c202c4@nvidia.com> <20120627140809.GD19319@avionic-0098.mockup.avionic-design.de> <20120627172914.30a2ccfd1344161ca7724722@nvidia.com> <20120627144414.GA20681@avionic-0098.mockup.avionic-design.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120627144414.GA20681-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Thierry Reding Cc: Stephen Warren , "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org" , Mark Zhang , "dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org" , "iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org" , "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: iommu@lists.linux-foundation.org On Wed, 27 Jun 2012 16:44:14 +0200 Thierry Reding wrote: > > I think that "coherent_pool" can be used only when the amount of > > contiguous memory is short in your system. Otherwise even unnecessary. > > > > Could you explain a bit more why you want carveout size on per-board basis? > > In the ideal case I would want to not have a carveout size at all. > However there may be situations where you need to make sure some driver > can allocate a given amount of memory. Having to specify this using a > kernel command-line parameter is cumbersome because it may require > changes to the bootloader or whatever. So if you know that a particular > board always needs 128 MiB of carveout, then it makes sense to specify > it on a per-board basis. Hm...I could understand somewhat;) but DT can also specify "bootargs" in dts file, which can support per-board-wide spec too, like the above sum of carveout needed from all drivers. I just want to avoid introducing a new parameter additionaly if we can make use of the existing mechanism.