From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: [PATCH v4 1/5] ARM: add basic Trusted Foundations support Date: Tue, 03 Sep 2013 12:36:06 -0600 Message-ID: <52262C16.3020406@wwwdotorg.org> References: <1377770268-14014-1-git-send-email-acourbot@nvidia.com> <1377770268-14014-2-git-send-email-acourbot@nvidia.com> <2081838.eZHRxlDf7s@flatron> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Alexandre Courbot Cc: Tomasz Figa , Alexandre Courbot , Russell King - ARM Linux , Dave Martin , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Linux Kernel Mailing List List-Id: devicetree@vger.kernel.org On 09/02/2013 01:28 AM, Alexandre Courbot wrote: > Hi Tomasz! > > On Fri, Aug 30, 2013 at 5:20 PM, Tomasz Figa wrote: >>> +Required properties: >>> +- compatible : "tl,trusted-foundations" >>> +- version-major : major version number of Trusted Foundations firmware >>> +- version-minor: minor version number of Trusted Foundations firmware >> >> Hmm, maybe you could simply define a single version property that could >> have multiple cells? Like: >> >> firmware { >> compatible = "tl,trusted-foundations"; >> version = <2 8>; >> }; > > I'm fine this way too, but do we have other bindings that use the same > scheme? What is the general convention for version number bindings? I don't know if there are enough cases of this for there to be a convention. A 2-cell property seems fine to me. >>> + This option allows the kernel to invoke the secure monitor whenever >>> + required on devices using Trusted Foundations. >>> + >>> + Devices using Trusted Foundations should pass a device tree >>> containing + a node compatible with "tl,trusted-foundations" to >>> signal the presence + of the secure monitor. >> >> What about pointing to the documentation file instead? > > Yes, that would make more sense. Possibly. What about when the binding document is no longer part of the kernel though? Perhaps we could reference the documentation in some way other than by the pathname within the kernel source tree though, e.g. 'see the device tree binding documentation for compatible="tl,trusted-foundations"'?