From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Tomasz Figa <tomasz.figa@gmail.com>,
Alexandre Courbot <acourbot@nvidia.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Dave Martin <Dave.Martin@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/5] ARM: add basic Trusted Foundations support
Date: Tue, 03 Sep 2013 12:36:06 -0600 [thread overview]
Message-ID: <52262C16.3020406@wwwdotorg.org> (raw)
In-Reply-To: <CAAVeFuJ=z-29gp9=caQaxRGCiOQSnPLfafia3eCgWAUuny3GBg@mail.gmail.com>
On 09/02/2013 01:28 AM, Alexandre Courbot wrote:
> Hi Tomasz!
>
> On Fri, Aug 30, 2013 at 5:20 PM, Tomasz Figa <tomasz.figa@gmail.com> 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"'?
next prev parent reply other threads:[~2013-09-03 18:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 9:57 [PATCH v4 0/5] ARM: tegra: support for Trusted Foundations Alexandre Courbot
2013-08-29 9:57 ` [PATCH v4 1/5] ARM: add basic Trusted Foundations support Alexandre Courbot
2013-08-30 8:20 ` Tomasz Figa
2013-09-02 7:28 ` Alexandre Courbot
2013-09-03 18:36 ` Stephen Warren [this message]
2013-09-03 18:40 ` Stephen Warren
2013-08-29 9:57 ` [PATCH v4 2/5] ARM: tegra: add support for Trusted Foundations Alexandre Courbot
2013-08-29 9:57 ` [PATCH v4 3/5] ARM: tegra: split setting of CPU reset handler Alexandre Courbot
2013-08-29 9:57 ` [PATCH v4 4/5] ARM: tegra: set CPU reset handler with firmware op Alexandre Courbot
2013-08-29 9:57 ` [PATCH v4 5/5] ARM: tegra: support Trusted Foundations by default Alexandre Courbot
2013-08-30 8:23 ` [PATCH v4 0/5] ARM: tegra: support for Trusted Foundations Tomasz Figa
2013-09-03 18:42 ` Stephen Warren
2013-09-04 2:31 ` Alex Courbot
2013-09-04 18:25 ` Stephen Warren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52262C16.3020406@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Dave.Martin@arm.com \
--cc=acourbot@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tomasz.figa@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox