All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Anderson <dianders@chromium.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Christopher Covington <cov@codeaurora.org>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
	Russell King <linux@arm.linux.org.uk>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Will Deacon <Will.Deacon@arm.com>,
	Sudeep Holla <Sudeep.Holla@arm.com>,
	Olof Johansson <olof@lixom.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	Sonny Rao <sonnyrao@chromium.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] clocksource: arch_timer: Fix code to use physical timers when requested
Date: Wed, 10 Sep 2014 10:19:28 -0700	[thread overview]
Message-ID: <CAD=FV=URg=vQbOqkg57Uujs4UWv8OKEjY+3Rx=7jbgab5pgoBQ@mail.gmail.com> (raw)
In-Reply-To: <20140910155509.GA7519@leverpostej>

Mark,

On Wed, Sep 10, 2014 at 8:55 AM, Mark Rutland <mark.rutland@arm.com> wrote:
> That's not true in general as other secure initialization will still be
> necessary, and the extent and character of that initialization is going
> to be implementation specific.

Can you give more examples of what you mean by implementation
specific?  Does this mean that secure initialization will be different
for every SoC out there?  ...or is it just different for different ARM
cores?

-Doug

WARNING: multiple messages have this Message-ID (diff)
From: dianders@chromium.org (Doug Anderson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource: arch_timer: Fix code to use physical timers when requested
Date: Wed, 10 Sep 2014 10:19:28 -0700	[thread overview]
Message-ID: <CAD=FV=URg=vQbOqkg57Uujs4UWv8OKEjY+3Rx=7jbgab5pgoBQ@mail.gmail.com> (raw)
In-Reply-To: <20140910155509.GA7519@leverpostej>

Mark,

On Wed, Sep 10, 2014 at 8:55 AM, Mark Rutland <mark.rutland@arm.com> wrote:
> That's not true in general as other secure initialization will still be
> necessary, and the extent and character of that initialization is going
> to be implementation specific.

Can you give more examples of what you mean by implementation
specific?  Does this mean that secure initialization will be different
for every SoC out there?  ...or is it just different for different ARM
cores?

-Doug

  parent reply	other threads:[~2014-09-10 17:19 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 21:03 [PATCH] clocksource: arch_timer: Fix code to use physical timers when requested Sonny Rao
2014-08-27 21:03 ` Sonny Rao
2014-08-27 21:19 ` Olof Johansson
2014-08-27 21:19   ` Olof Johansson
2014-08-27 21:27   ` Sonny Rao
2014-08-27 21:27     ` Sonny Rao
2014-08-27 22:26     ` Stephen Boyd
2014-08-27 22:26       ` Stephen Boyd
2014-08-27 22:33       ` Olof Johansson
2014-08-27 22:33         ` Olof Johansson
2014-08-28  0:56         ` Stephen Boyd
2014-08-28  0:56           ` Stephen Boyd
2014-08-28  2:58           ` Olof Johansson
2014-08-28  2:58             ` Olof Johansson
2014-08-28  3:33             ` Doug Anderson
2014-08-28  3:33               ` Doug Anderson
2014-08-28  9:35               ` Mark Rutland
2014-08-28  9:35                 ` Mark Rutland
2014-08-28 17:09                 ` Christopher Covington
2014-08-28 17:09                   ` Christopher Covington
2014-08-28 18:04                   ` Mark Rutland
2014-08-28 18:04                     ` Mark Rutland
2014-08-29  0:10                 ` Sonny Rao
2014-08-29  0:10                   ` Sonny Rao
2014-08-29 10:04                   ` Mark Rutland
2014-08-29 10:04                     ` Mark Rutland
2014-09-04 17:01                     ` Sonny Rao
2014-09-04 17:01                       ` Sonny Rao
2014-09-04 17:47                       ` Mark Rutland
2014-09-04 17:47                         ` Mark Rutland
2014-09-04 17:48                       ` Lorenzo Pieralisi
2014-09-04 17:48                         ` Lorenzo Pieralisi
2014-09-05 22:11                 ` Doug Anderson
2014-09-05 22:11                   ` Doug Anderson
2014-09-08 13:54                   ` Catalin Marinas
2014-09-08 13:54                     ` Catalin Marinas
2014-09-10 17:17                     ` Doug Anderson
2014-09-10 17:17                       ` Doug Anderson
2014-09-10 17:34                       ` Will Deacon
2014-09-10 17:34                         ` Will Deacon
2014-09-10 18:09                         ` Doug Anderson
2014-09-10 18:09                           ` Doug Anderson
2014-09-10 18:46                           ` Will Deacon
2014-09-10 18:46                             ` Will Deacon
2014-09-10 19:50                             ` Doug Anderson
2014-09-10 19:50                               ` Doug Anderson
2014-09-11  9:57                               ` Will Deacon
2014-09-11  9:57                                 ` Will Deacon
2014-09-11 15:54                                 ` Doug Anderson
2014-09-11 15:54                                   ` Doug Anderson
2014-09-10 14:58                   ` Christopher Covington
2014-09-10 14:58                     ` Christopher Covington
2014-09-10 15:47                     ` Catalin Marinas
2014-09-10 15:47                       ` Catalin Marinas
2014-09-10 15:55                     ` Mark Rutland
2014-09-10 15:55                       ` Mark Rutland
2014-09-10 16:39                       ` Olof Johansson
2014-09-10 16:39                         ` Olof Johansson
2014-09-10 17:19                       ` Doug Anderson [this message]
2014-09-10 17:19                         ` Doug Anderson
2014-08-28  9:23 ` Marc Zyngier
2014-08-28  9:23   ` Marc Zyngier
2014-09-10 17:27 ` Mark Rutland
2014-09-10 17:27   ` Mark Rutland
2014-09-10 17:52   ` Doug Anderson
2014-09-10 17:52     ` Doug Anderson
2014-09-10 18:05     ` Sonny Rao
2014-09-10 18:05       ` Sonny Rao
2014-09-10 18:35     ` Doug Anderson
2014-09-10 18:35       ` Doug Anderson

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='CAD=FV=URg=vQbOqkg57Uujs4UWv8OKEjY+3Rx=7jbgab5pgoBQ@mail.gmail.com' \
    --to=dianders@chromium.org \
    --cc=Catalin.Marinas@arm.com \
    --cc=Lorenzo.Pieralisi@arm.com \
    --cc=Sudeep.Holla@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=cov@codeaurora.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=olof@lixom.net \
    --cc=sboyd@codeaurora.org \
    --cc=sonnyrao@chromium.org \
    --cc=tglx@linutronix.de \
    /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.