All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH/RFC] ARM: shmobile: Always enable ARCH_TIMER on SoCs with A7 and/or A15
Date: Tue, 17 Jul 2018 11:59:05 +0200	[thread overview]
Message-ID: <20180717095904.eik3sko64zqymzts@verge.net.au> (raw)
In-Reply-To: <CAMuHMdUsHHDo_2unzUZN9W0kY2p5YW+yGkfsdXE-8ZHuBAuxnA@mail.gmail.com>

On Fri, Jul 13, 2018 at 10:33:17AM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
> 
> On Fri, Jul 13, 2018 at 10:19 AM Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > On Fri, Jul 13, 2018 at 10:08 AM Simon Horman <horms@verge.net.au> wrote:
> > > On Thu, Jul 12, 2018 at 06:08:57PM +0200, Geert Uytterhoeven wrote:
> > > > R-Mobile APE6, R-Car Gen2, and RZ/G1 SoCs have Cortex-A7 and/or
> > > > Cortex-A15 CPU cores, all of which have ARM architectured timers.
> > > >
> > > > Force use of the ARM architectured timer on these SoCs.
> > > > This allows to:
> > > >   - Remove the calls to shmobile_init_delay() from the corresponding
> > > >     machine vectors,
> > > >   - Remove a check in timer setup specific to R-Car Gen2,
> > > >   - Remove a check in shmobile_init_delay().
> > > >
> > > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > >
> > > on which boards did you test this?
> >
> > On APE6EVM and Koelsch (R-Car M2-W).
> > I can give it a spin on a few more remote R-Car Gen2 boards if you want.
> 
> I don't expect any issues, as shmobile_defconfig already enables
> CONFIG_HAVE_ARM_ARCH_TIMER, and shmobile_init_delay() was already
> a no-op in that case.

I am happy if you are happy.
Shall I go ahead and apply this?

Reviewed-by: Simon Horman <horms+renesas@verge.net.au>

WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC] ARM: shmobile: Always enable ARCH_TIMER on SoCs with A7 and/or A15
Date: Tue, 17 Jul 2018 11:59:05 +0200	[thread overview]
Message-ID: <20180717095904.eik3sko64zqymzts@verge.net.au> (raw)
In-Reply-To: <CAMuHMdUsHHDo_2unzUZN9W0kY2p5YW+yGkfsdXE-8ZHuBAuxnA@mail.gmail.com>

On Fri, Jul 13, 2018 at 10:33:17AM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
> 
> On Fri, Jul 13, 2018 at 10:19 AM Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > On Fri, Jul 13, 2018 at 10:08 AM Simon Horman <horms@verge.net.au> wrote:
> > > On Thu, Jul 12, 2018 at 06:08:57PM +0200, Geert Uytterhoeven wrote:
> > > > R-Mobile APE6, R-Car Gen2, and RZ/G1 SoCs have Cortex-A7 and/or
> > > > Cortex-A15 CPU cores, all of which have ARM architectured timers.
> > > >
> > > > Force use of the ARM architectured timer on these SoCs.
> > > > This allows to:
> > > >   - Remove the calls to shmobile_init_delay() from the corresponding
> > > >     machine vectors,
> > > >   - Remove a check in timer setup specific to R-Car Gen2,
> > > >   - Remove a check in shmobile_init_delay().
> > > >
> > > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > >
> > > on which boards did you test this?
> >
> > On APE6EVM and Koelsch (R-Car M2-W).
> > I can give it a spin on a few more remote R-Car Gen2 boards if you want.
> 
> I don't expect any issues, as shmobile_defconfig already enables
> CONFIG_HAVE_ARM_ARCH_TIMER, and shmobile_init_delay() was already
> a no-op in that case.

I am happy if you are happy.
Shall I go ahead and apply this?

Reviewed-by: Simon Horman <horms+renesas@verge.net.au>

  reply	other threads:[~2018-07-17 10:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12 16:08 [PATCH/RFC] ARM: shmobile: Always enable ARCH_TIMER on SoCs with A7 and/or A15 Geert Uytterhoeven
2018-07-12 16:08 ` Geert Uytterhoeven
2018-07-13  3:11 ` Magnus Damm
2018-07-13  3:11   ` Magnus Damm
2018-07-13  7:57   ` Geert Uytterhoeven
2018-07-13  7:57     ` Geert Uytterhoeven
2018-07-13 12:22     ` Chris Brandt
2018-07-13 12:22       ` Chris Brandt
2018-07-13 12:32       ` Geert Uytterhoeven
2018-07-13 12:32         ` Geert Uytterhoeven
2018-07-13  8:08 ` Simon Horman
2018-07-13  8:08   ` Simon Horman
2018-07-13  8:19   ` Geert Uytterhoeven
2018-07-13  8:19     ` Geert Uytterhoeven
2018-07-13  8:33     ` Geert Uytterhoeven
2018-07-13  8:33       ` Geert Uytterhoeven
2018-07-17  9:59       ` Simon Horman [this message]
2018-07-17  9:59         ` Simon Horman
2018-07-17 10:12         ` Geert Uytterhoeven
2018-07-17 10:12           ` Geert Uytterhoeven
2018-07-17 12:16           ` Simon Horman
2018-07-17 12:16             ` 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=20180717095904.eik3sko64zqymzts@verge.net.au \
    --to=horms@verge.net.au \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.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 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.