All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Alexandre Courbot <acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Russell King - ARM Linux
	<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
	Tomasz Figa <tomasz.figa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Dave Martin <Dave.Martin-5wv7dgnIgG8@public.gmane.org>,
	Joseph Lo <josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Jassi Brar
	<jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v3 4/5] ARM: tegra: set CPU reset handler with firmware op
Date: Wed, 14 Aug 2013 15:40:31 -0600	[thread overview]
Message-ID: <520BF94F.60907@wwwdotorg.org> (raw)
In-Reply-To: <1376360992-1508-5-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

On 08/12/2013 08:29 PM, Alexandre Courbot wrote:
> Use a firmware operation to set the CPU reset handler and only resort to
> doing it ourselves if there is none defined.
> 
> This supports the booting of secondary CPUs on devices using a TrustZone
> secure monitor.

> diff --git a/arch/arm/mach-tegra/reset.c b/arch/arm/mach-tegra/reset.c

> +	err = call_firmware_op(set_cpu_boot_addr, 0, reset_address);
> +	switch (err) {
> +	case -ENOSYS:
> +		tegra_cpu_reset_handler_set(reset_address);
> +		/* pass-through */
> +	case 0:
> +		is_enabled = true;
> +		break;
> +	default:
> +		pr_crit("Cannot set CPU reset handler: %d\n", err);
> +		BUG();
> +	}

Instead of trying and failing, does it make sense to register
tegra_cpu_reset_handler_set() as the set_cpu_boot_addr firmware op when
there is no firmware present? That would simplify all call-sites of any
firmware op.

WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/5] ARM: tegra: set CPU reset handler with firmware op
Date: Wed, 14 Aug 2013 15:40:31 -0600	[thread overview]
Message-ID: <520BF94F.60907@wwwdotorg.org> (raw)
In-Reply-To: <1376360992-1508-5-git-send-email-acourbot@nvidia.com>

On 08/12/2013 08:29 PM, Alexandre Courbot wrote:
> Use a firmware operation to set the CPU reset handler and only resort to
> doing it ourselves if there is none defined.
> 
> This supports the booting of secondary CPUs on devices using a TrustZone
> secure monitor.

> diff --git a/arch/arm/mach-tegra/reset.c b/arch/arm/mach-tegra/reset.c

> +	err = call_firmware_op(set_cpu_boot_addr, 0, reset_address);
> +	switch (err) {
> +	case -ENOSYS:
> +		tegra_cpu_reset_handler_set(reset_address);
> +		/* pass-through */
> +	case 0:
> +		is_enabled = true;
> +		break;
> +	default:
> +		pr_crit("Cannot set CPU reset handler: %d\n", err);
> +		BUG();
> +	}

Instead of trying and failing, does it make sense to register
tegra_cpu_reset_handler_set() as the set_cpu_boot_addr firmware op when
there is no firmware present? That would simplify all call-sites of any
firmware op.

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Tomasz Figa <tomasz.figa@gmail.com>,
	Dave Martin <Dave.Martin@arm.com>, Joseph Lo <josephl@nvidia.com>,
	Jassi Brar <jassisinghbrar@gmail.com>,
	gnurou@gmail.com, linux-arm-kernel@lists.infradead.org,
	linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/5] ARM: tegra: set CPU reset handler with firmware op
Date: Wed, 14 Aug 2013 15:40:31 -0600	[thread overview]
Message-ID: <520BF94F.60907@wwwdotorg.org> (raw)
In-Reply-To: <1376360992-1508-5-git-send-email-acourbot@nvidia.com>

On 08/12/2013 08:29 PM, Alexandre Courbot wrote:
> Use a firmware operation to set the CPU reset handler and only resort to
> doing it ourselves if there is none defined.
> 
> This supports the booting of secondary CPUs on devices using a TrustZone
> secure monitor.

> diff --git a/arch/arm/mach-tegra/reset.c b/arch/arm/mach-tegra/reset.c

> +	err = call_firmware_op(set_cpu_boot_addr, 0, reset_address);
> +	switch (err) {
> +	case -ENOSYS:
> +		tegra_cpu_reset_handler_set(reset_address);
> +		/* pass-through */
> +	case 0:
> +		is_enabled = true;
> +		break;
> +	default:
> +		pr_crit("Cannot set CPU reset handler: %d\n", err);
> +		BUG();
> +	}

Instead of trying and failing, does it make sense to register
tegra_cpu_reset_handler_set() as the set_cpu_boot_addr firmware op when
there is no firmware present? That would simplify all call-sites of any
firmware op.

  parent reply	other threads:[~2013-08-14 21:40 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13  2:29 [PATCH v3 0/5] ARM: tegra: support for Trusted Foundations Alexandre Courbot
2013-08-13  2:29 ` Alexandre Courbot
2013-08-13  2:29 ` Alexandre Courbot
2013-08-13  2:29 ` [PATCH v3 1/5] ARM: add basic Trusted Foundations support Alexandre Courbot
2013-08-13  2:29   ` Alexandre Courbot
2013-08-13  2:29   ` Alexandre Courbot
2013-08-14 21:35   ` Stephen Warren
2013-08-14 21:35     ` Stephen Warren
2013-08-18  8:37     ` Alexandre Courbot
2013-08-18  8:37       ` Alexandre Courbot
     [not found]       ` <CAAVeFuJ9tgXRf+QZRK5K8O2X=mKxUZtFgTsB06r4huQrDwZx2A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-19 15:56         ` Stephen Warren
2013-08-19 15:56           ` Stephen Warren
2013-08-19 15:56           ` Stephen Warren
2013-08-15 11:52   ` Dave Martin
2013-08-15 11:52     ` Dave Martin
2013-08-15 11:52     ` Dave Martin
     [not found]     ` <20130815115227.GC2562-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2013-08-15 22:02       ` Stephen Warren
2013-08-15 22:02         ` Stephen Warren
2013-08-15 22:02         ` Stephen Warren
2013-08-16 13:23         ` Dave Martin
2013-08-16 13:23           ` Dave Martin
     [not found]           ` <20130816132326.GC2909-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2013-08-18  8:38             ` Alexandre Courbot
2013-08-18  8:38               ` Alexandre Courbot
2013-08-18  8:38               ` Alexandre Courbot
2013-08-18  8:37       ` Alexandre Courbot
2013-08-18  8:37         ` Alexandre Courbot
2013-08-18  8:37         ` Alexandre Courbot
     [not found] ` <1376360992-1508-1-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-08-13  2:29   ` [PATCH v3 2/5] ARM: tegra: add support for Trusted Foundations Alexandre Courbot
2013-08-13  2:29     ` Alexandre Courbot
2013-08-13  2:29     ` Alexandre Courbot
2013-08-14 21:38     ` Stephen Warren
2013-08-14 21:38       ` Stephen Warren
     [not found]       ` <520BF8BD.7050706-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-08-18  8:37         ` Alexandre Courbot
2013-08-18  8:37           ` Alexandre Courbot
2013-08-18  8:37           ` Alexandre Courbot
2013-08-13  2:29 ` [PATCH v3 3/5] ARM: tegra: split setting of CPU reset handler Alexandre Courbot
2013-08-13  2:29   ` Alexandre Courbot
2013-08-13  2:29   ` Alexandre Courbot
2013-08-13  2:29 ` [PATCH v3 4/5] ARM: tegra: set CPU reset handler with firmware op Alexandre Courbot
2013-08-13  2:29   ` Alexandre Courbot
2013-08-13  2:29   ` Alexandre Courbot
     [not found]   ` <1376360992-1508-5-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-08-14 21:40     ` Stephen Warren [this message]
2013-08-14 21:40       ` Stephen Warren
2013-08-14 21:40       ` Stephen Warren
2013-08-18  8:37       ` Alexandre Courbot
2013-08-18  8:37         ` Alexandre Courbot
2013-08-13  2:29 ` [PATCH v3 5/5] ARM: tegra: support Trusted Foundations by default Alexandre Courbot
2013-08-13  2:29   ` Alexandre Courbot
2013-08-13  2:29   ` Alexandre Courbot

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=520BF94F.60907@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=Dave.Martin-5wv7dgnIgG8@public.gmane.org \
    --cc=acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=tomasz.figa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.