From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: rcar-gen2: Do not attempt to re-setup timer if running correctly
Date: Wed, 11 Dec 2013 10:06:54 +0000 [thread overview]
Message-ID: <52A8393E.2030007@codethink.co.uk> (raw)
In-Reply-To: <1386753916-25648-1-git-send-email-ben.dooks@codethink.co.uk>
On 11/12/13 09:25, Ben Dooks wrote:
> If the system has been started in non-secure mode, then the ARM generic
> timer is not configurable during the kernel initialisation. Currently
> the only thing we can check for is if the timer has been correctly
> configured during the boot process.
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> Reviewed-by: Ian Molton <ian.molton@codethink.co.uk>
Sorry, I've gone and re-posted the same patch as yesterday.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
WARNING: multiple messages have this Message-ID (diff)
From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: rcar-gen2: Do not attempt to re-setup timer if running correctly
Date: Wed, 11 Dec 2013 10:06:54 +0000 [thread overview]
Message-ID: <52A8393E.2030007@codethink.co.uk> (raw)
In-Reply-To: <1386753916-25648-1-git-send-email-ben.dooks@codethink.co.uk>
On 11/12/13 09:25, Ben Dooks wrote:
> If the system has been started in non-secure mode, then the ARM generic
> timer is not configurable during the kernel initialisation. Currently
> the only thing we can check for is if the timer has been correctly
> configured during the boot process.
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> Reviewed-by: Ian Molton <ian.molton@codethink.co.uk>
Sorry, I've gone and re-posted the same patch as yesterday.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2013-12-11 10:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 9:25 [PATCH] ARM: rcar-gen2: Do not attempt to re-setup timer if running correctly Ben Dooks
2013-12-11 9:25 ` Ben Dooks
2013-12-11 9:36 ` Magnus Damm
2013-12-11 9:36 ` Magnus Damm
2013-12-11 10:06 ` Ben Dooks [this message]
2013-12-11 10:06 ` Ben Dooks
2013-12-11 17:14 ` Sergei Shtylyov
2013-12-11 17:14 ` Sergei Shtylyov
2013-12-11 17:15 ` Ben Dooks
2013-12-11 17:15 ` Ben Dooks
2013-12-11 17:20 ` Sergei Shtylyov
2013-12-11 17:20 ` Sergei Shtylyov
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=52A8393E.2030007@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-arm-kernel@lists.infradead.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.