public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Courbot <acourbot@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>,
	Russell King <linux@arm.linux.org.uk>,
	Tomasz Figa <t.figa@samsung.com>
Cc: Olof Johansson <olof@lixom.net>,
	Dave Martin <Dave.Martin@arm.com>, Arnd Bergmann <arnd@arndb.de>,
	Kevin Hilman <khilman@linaro.org>,
	Rob Herring <rob.herring@calxeda.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <Mark.Rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v10 4/7] ARM: tegra: add support for Trusted Foundations
Date: Wed, 13 Nov 2013 10:59:56 +0900	[thread overview]
Message-ID: <5282DD1C.4000307@nvidia.com> (raw)
In-Reply-To: <52828E31.8010408@wwwdotorg.org>

On 11/13/2013 05:23 AM, Stephen Warren wrote:
> On 11/07/2013 03:11 AM, Alexandre Courbot wrote:
>> Register the firmware operations for Trusted Foundations if the device
>> tree indicates it is active on the device.
>
>> diff --git a/arch/arm/mach-tegra/common.c b/arch/arm/mach-tegra/common.c
>
>>   void __init tegra_init_early(void)
>>   {
>> +	of_register_trusted_foundations();
>>   	tegra_cpu_reset_handler_init();
>>   	tegra_apb_io_init();
>>   	tegra_init_fuse();
>
> Your other bugfix patch for 3.13 moved tegra_cpu_reset_handler_init().
> Should the call to of_register_trusted_foundations() move with it when
> this is applied, or should it just stay right at the start of
> tegra_init_early()? Either way is fine; just let me know which way to
> fix up the conflict when this gets applied.

I rebased on -next and left it at the start of tegra_init_early(). Even 
though at the moment the only requirement is that the call is made 
before tegra_cpu_reset_handler_init(), it seems to make sense to get rid 
of firmware-related initialization as early as possible.

Btw, this patchset is still based on the 3.12 code, before common.c got 
renamed to tegra.c, so you will have a problem here as well (sorry about 
that). The conflict is easy to resolve, but if you want me to send you a 
properly rebased version, just let me know.


  reply	other threads:[~2013-11-13  2:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 10:11 [PATCH v10 0/7] ARM: support for Trusted Foundations secure monitor Alexandre Courbot
2013-11-07 10:11 ` [PATCH v10 1/7] ARM: add basic support for Trusted Foundations Alexandre Courbot
2013-11-07 10:11 ` [PATCH v10 2/7] of: add vendor prefix for Trusted Logic Mobility Alexandre Courbot
2013-11-07 10:11 ` [PATCH v10 3/7] of: add Trusted Foundations bindings Alexandre Courbot
2013-11-07 10:11 ` [PATCH v10 4/7] ARM: tegra: add support for Trusted Foundations Alexandre Courbot
2013-11-12 20:23   ` Stephen Warren
2013-11-13  1:59     ` Alex Courbot [this message]
2013-11-07 10:11 ` [PATCH v10 5/7] ARM: tegra: split setting of CPU reset handler Alexandre Courbot
2013-11-07 10:11 ` [PATCH v10 6/7] ARM: tegra: set CPU reset handler with firmware op Alexandre Courbot
2013-11-07 10:11 ` [PATCH v10 7/7] ARM: tegra: support Trusted Foundations by default Alexandre Courbot
2013-11-12 20:26 ` [PATCH v10 0/7] ARM: support for Trusted Foundations secure monitor Stephen Warren
2013-11-12 20:38   ` Olof Johansson
2013-11-13  2:14     ` Alex Courbot
2013-11-13 17:57       ` Olof Johansson
2013-11-14  1:20         ` Alex Courbot
2013-11-17  9:03           ` Alexandre Courbot
2013-11-18  6:28             ` Alex Courbot
2013-11-21 18:48         ` Stephen Warren
2013-11-21 18:51           ` Olof Johansson
2013-11-21 19:00             ` Russell King - ARM Linux
2013-11-21 19:57               ` 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=5282DD1C.4000307@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=Dave.Martin@arm.com \
    --cc=Mark.Rutland@arm.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=khilman@linaro.org \
    --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=olof@lixom.net \
    --cc=pawel.moll@arm.com \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@wwwdotorg.org \
    --cc=t.figa@samsung.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