linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Courbot <gnurou@gmail.com>
To: Alex Courbot <acourbot@nvidia.com>
Cc: Olof Johansson <olof@lixom.net>,
	Russell King <linux@arm.linux.org.uk>,
	Mark Rutland <Mark.Rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Kevin Hilman <khilman@linaro.org>,
	Pawel Moll <pawel.moll@arm.com>, Arnd Bergmann <arnd@arndb.de>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Tomasz Figa <t.figa@samsung.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Rob Herring <rob.herring@calxeda.com>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	Dave Martin <Dave.Martin@arm.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v10 0/7] ARM: support for Trusted Foundations secure monitor
Date: Sun, 17 Nov 2013 18:03:37 +0900	[thread overview]
Message-ID: <CAAVeFu+Uh9fi_kGv-g-0fH=p4758sCRONexZN25weS0s3PrvxA@mail.gmail.com> (raw)
In-Reply-To: <52842553.2080807@nvidia.com>

On Thu, Nov 14, 2013 at 10:20 AM, Alex Courbot <acourbot@nvidia.com> wrote:
> On 11/14/2013 02:57 AM, Olof Johansson wrote:
>>
>> On Tue, Nov 12, 2013 at 6:14 PM, Alex Courbot <acourbot@nvidia.com> wrote:
>>>
>>> On 11/13/2013 05:38 AM, Olof Johansson wrote:
>>>>
>>>>
>>>> On Tue, Nov 12, 2013 at 12:26 PM, Stephen Warren <swarren@wwwdotorg.org>
>>>> wrote:
>>>>>
>>>>>
>>>>> On 11/07/2013 03:11 AM, Alexandre Courbot wrote:
>>>>>>
>>>>>>
>>>>>> Just a set of small fixes to address the concerns expressed on v9 with
>>>>>> the
>>>>>> non-prefixed version DT properties. I hope there won't be a need for
>>>>>> an
>>>>>> eleventh (!) version. :P
>>>>>
>>>>>
>>>>>
>>>>> BTW, this version looks fine to me. On IRC, Olof said it looked OK to
>>>>> him. I'm just waiting to hear back from Olof/Russell whether I should
>>>>> merge this through the Tegra tree, or whether the first 1-3 patches
>>>>> should go through Russell's tree.
>>>>
>>>>
>>>>
>>>> I pinged Russell, and he brought up the fact that there were earlier
>>>> requests to move it to drivers/firmware. It would make sense to try to
>>>> get that done before merging, especially if you anticipate someone
>>>> using TF on 64-bit platforms.
>>>
>>>
>>>
>>> IIRC when we discussed this point your last comment was as follows:
>>
>>
>> Touche. :) Thanks for the reminder.
>>
>>> On Tue, Oct 29, 2013 at 6:55 AM, Olof Johansson <olof@lixom.net> wrote:
>>>>
>>>> I think we can probably merge this under arch/arm now, and when we
>>>> figure out what needs to be common with ARM64 we can move it out to a
>>>> good location. It might be that mostly just a header file with ABI
>>>> conventions needs to be shared, not actual implementation, for
>>>> example.
>>>
>>>
>>> So I thought we agreed on that. If in the end we prefer to move the ARM
>>> firmware interface into drivers/firmware, I'm fine with that too (Tomasz
>>> also confirmed he would be ok with it) but I wonder if that would not be
>>> somehow premature.
>>>
>>> Another worry of mine is that this might delay this patchset some more.
>>> Support for TF is one of the last remaining step towards making NVIDIA
>>> branded Tegra retail devices (SHIELD and TegraNote at the moment) run
>>> upstream directly. I missed 3.13, I'd like to make sure I won't miss
>>> 3.14.
>>> Would it be acceptable if we move the ARM firmware interface to a common
>>> place after this patchset is merged?
>>
>>
>> Well, as I already said I'm ok with things going into arch/arm to
>> start with, as long as Russell is. Once we see 64-bit needs for the
>> same we'll move it out -- it's not like it's a whole lot of code to
>> start with. But Russell has veto on the topic. :-)
>
>
> Thanks Olof. Russell, are you ok with the patchset in its current form? I
> can start moving the firmware interface out of arch/arm if that's what you
> want (there is no user outside of ARM at the moment, but as Olof pointed out
> that's not too much code) but I'd really like to see this series secured for
> 3.14.

Never mind, I have submitted a patch that moves firmware_ops to
drivers/firmware, that will hopefully settle this issue. Then maybe we
can finally flush this series as well (I will need to resubmit a new
version though).

Alex.

  reply	other threads:[~2013-11-17  9:04 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
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 [this message]
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='CAAVeFu+Uh9fi_kGv-g-0fH=p4758sCRONexZN25weS0s3PrvxA@mail.gmail.com' \
    --to=gnurou@gmail.com \
    --cc=Dave.Martin@arm.com \
    --cc=Mark.Rutland@arm.com \
    --cc=acourbot@nvidia.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;
as well as URLs for NNTP newsgroup(s).