public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Courbot <acourbot@nvidia.com>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Joseph Lo <josephl@nvidia.com>, Karan Jhavar <kjhavar@nvidia.com>,
	Varun Wadekar <vwadekar@nvidia.com>,
	Chris Johnson <CJohnson@nvidia.com>,
	Matthew Longnecker <MLongnecker@nvidia.com>,
	"gnurou@gmail.com" <gnurou@gmail.com>,
	"devicetree-discuss@lists.ozlabs.org" 
	<devicetree-discuss@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] ARM: tegra: add basic SecureOS support
Date: Thu, 6 Jun 2013 19:37:49 +0900	[thread overview]
Message-ID: <51B0667D.30801@nvidia.com> (raw)
In-Reply-To: <1740292.8Sz57ytBcM@flatron>

Hi Tomasz,

On 06/06/2013 07:17 PM, Tomasz Figa wrote:
>> +Global properties
>> +-------------------------------------------
>> +
>> +The following properties can be specified into the "chosen" root
>> +node:
>> +
>> +  nvidia,secure-os: enable SecureOS.
>
> Hmm, on Exynos we had something like
>
>          firmware@0203F000 {
>                  compatible = "samsung,secure-firmware";
>                  reg = <0x0203F000 0x1000>;
>          };
>
> but your solution might be actually the proper one, since firmware is not
> a hardware block. (The address in reg property is pointing to SYSRAM
> memory, which is an additional communication channel with the firmware.)

Yes, I saw your implementation but decided to do it through the chosen 
node anyway, since that's what it seems to be designed and we don't need 
any reg parameter.

> I think this patch could be split into several patches:
>   - add support for firmware
>   - split reset function
>   - add reset support using firmware.

Mmm possibly yes, but I wonder if that would not be too much splitting. 
Stephen?

> Hmm, I wonder if you need all this complexity here. Have a look at our
> exynos_smc function
>
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/arch/arm/mach-exynos/exynos-smc.S?id=refs/tags/next-20130606

Yes, I just embarrassed myself showing my ignorance of ARM assembler. ;) 
The fix Russel proposed is pretty close to your version.

>> +static const struct firmware_ops tegra_firmware_ops = {
>> +     .set_cpu_boot_addr = tegra_set_cpu_boot_addr,
>> +};
>
> It's good that this interface is finally getting some user besides Exynos.

I didn't know about it first but Joseph kindly pointed it out to me and 
it indeed makes it easier to implement this.

Thanks,
Alex.



  reply	other threads:[~2013-06-06 10:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06  7:28 [PATCH] ARM: tegra: add basic SecureOS support Alexandre Courbot
2013-06-06  9:35 ` Russell King - ARM Linux
2013-06-06 10:23   ` Alex Courbot
2013-06-06 10:17 ` Tomasz Figa
2013-06-06 10:37   ` Alex Courbot [this message]
2013-06-06 16:28     ` Stephen Warren
2013-06-06 11:11   ` Dave Martin
2013-06-06 11:02 ` Dave Martin
2013-06-07  7:25   ` Alexandre Courbot
2013-06-07 17:30     ` Dave Martin
2013-06-10  7:47       ` Alexandre Courbot
2013-06-10  9:10         ` Russell King - ARM Linux
2013-06-06 12:26 ` Jassi Brar
2013-06-07  7:13   ` Alexandre Courbot
2013-06-07  8:52     ` Jassi Brar
2013-06-06 16:44 ` Stephen Warren
2013-06-06 18:08   ` Dave Martin
2013-06-06 18:29     ` Stephen Warren
2013-06-07 17:47       ` Dave Martin
2013-06-07  9:03     ` Alexandre Courbot
2013-06-07 18:13       ` Dave Martin
2013-06-10  8:05         ` Alexandre Courbot
2013-06-10 11:20           ` Dave Martin
2013-06-07  8:11   ` Alexandre Courbot
2013-06-07 16:33     ` Stephen Warren
2013-06-10  8:11       ` Alexandre Courbot
2013-06-10  9:14         ` Russell King - ARM Linux
2013-06-10 16:35           ` Stephen Warren
2013-06-10 11:16         ` Dave Martin

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=51B0667D.30801@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=CJohnson@nvidia.com \
    --cc=MLongnecker@nvidia.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=gnurou@gmail.com \
    --cc=josephl@nvidia.com \
    --cc=kjhavar@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=tomasz.figa@gmail.com \
    --cc=vwadekar@nvidia.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