linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 07/10] ARM: shmobile: Use arch timer on Koelsch
Date: Thu, 3 Oct 2013 13:21:34 +0900	[thread overview]
Message-ID: <20131003042133.GL7925@verge.net.au> (raw)
In-Reply-To: <20131001081257.4136.80053.sendpatchset@w520>

On Tue, Oct 01, 2013 at 05:12:57PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
> 
> Make use of the R-Car Gen2 arch timer workaround on Koelsch.
> 
> Signed-off-by: Magnus Damm <damm@opensource.se>
> ---
> 
>  arch/arm/mach-shmobile/board-koelsch.c |    2 ++
>  1 file changed, 2 insertions(+)
> 
> --- 0003/arch/arm/mach-shmobile/board-koelsch.c
> +++ work/arch/arm/mach-shmobile/board-koelsch.c	2013-10-01 16:35:52.000000000 +0900
> @@ -23,6 +23,7 @@
>  #include <linux/platform_device.h>
>  #include <mach/common.h>
>  #include <mach/r8a7791.h>
> +#include <mach/rcar-gen2.h>
>  #include <asm/mach-types.h>
>  #include <asm/mach/arch.h>
>  
> @@ -40,5 +41,6 @@ static const char * const koelsch_boards
>  DT_MACHINE_START(KOELSCH_DT, "koelsch")
>  	.init_early	= r8a7791_init_early,
>  	.init_machine	= koelsch_add_standard_devices,
> +	.init_time	= rcar_gen2_timer_init,
>  	.dt_compat	= koelsch_boards_compat_dt,
>  MACHINE_END

Thanks, I have queued this up in the boards3 branch.
It should make it into v3.13 but if not I'll rename the branch
soc after rebasing it on v3.13-rcX which will then be targeted at v3.14.

The boards3 branch includes boards code previously queued up for v3.13
and a merge with soc changes previously queued up for v3.13. The reason
for the merge is to provide various build and run-time dependencies
including the rcar_gen2_timer_init code which this patch uses.

  reply	other threads:[~2013-10-03  4:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01  8:11 [PATCH 00/10] ARM: shmobile: r8a7791 SoC and Koelsch update V2 Magnus Damm
2013-10-01  8:11 ` [PATCH 01/10] ARM: shmobile: Introduce r8a7791_add_standard_devices() Magnus Damm
2013-10-03  2:36   ` Simon Horman
2013-10-01  8:12 ` [PATCH 02/10] ARM: shmobile: Use r8a7791_add_standard_devices() on Koelsch Magnus Damm
2013-10-03  4:20   ` Simon Horman
2013-10-01  8:12 ` [PATCH 03/10] ARM: shmobile: r8a7791 IRQC platform device support Magnus Damm
2013-10-03  2:37   ` Simon Horman
2013-10-01  8:12 ` [PATCH 04/10] ARM: shmobile: r8a7791 IRQC device tree node Magnus Damm
2013-10-03  2:43   ` Simon Horman
2013-10-01  8:12 ` [PATCH 05/10] ARM: shmobile: r8a7791 Arch timer " Magnus Damm
2013-10-03  2:44   ` Simon Horman
2013-10-01  8:12 ` [PATCH 06/10] ARM: shmobile: r8a7791 Arch timer workaround Magnus Damm
2013-10-03  3:45   ` Simon Horman
2013-10-01  8:12 ` [PATCH 07/10] ARM: shmobile: Use arch timer on Koelsch Magnus Damm
2013-10-03  4:21   ` Simon Horman [this message]
2013-10-01  8:13 ` [PATCH 08/10] ARM: shmobile: r8a7791 SMP device tree node Magnus Damm
2013-10-03  3:46   ` Simon Horman
2013-10-01  8:13 ` [PATCH 09/10] ARM: shmobile: r8a7791 SMP support Magnus Damm
2013-10-03  3:47   ` Simon Horman
2013-10-01  8:13 ` [PATCH 10/10] ARM: shmobile: Use SMP on Koelsch Magnus Damm
2013-10-03  4:22   ` Simon Horman

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=20131003042133.GL7925@verge.net.au \
    --to=horms@verge.net.au \
    --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 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).