public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource: dw_apb_timer_of: support timer-based delay
Date: Mon, 02 Nov 2015 22:49:01 +0100	[thread overview]
Message-ID: <4138087.gESYTxjr8X@wuerfel> (raw)
In-Reply-To: <56372366.6090905@linaro.org>

On Monday 02 November 2015 09:48:38 Daniel Lezcano wrote:
> If I follow the logic of arch_arm_timer is better than dw_apb timer.
> 
> 1. The arch_arm_timer is present
> 
>   => dw_apb timer is not used at all
> 
>   CONFIG_ARM_ARCH_TIMER=y
>   # CONFIG_DW_APB_TIMER is not set
> 
> 2. The arch_arm_timer is *not* present
> 
>   => dw_apb_timer is used with delay code
> 
>   # CONFIG_ARM_ARCH_TIMER is not set
>   CONFIG_DW_APB_TIMER=y
> 
> In both cases, DW_APB_TIMER_BASED_DELAY is not needed.
> 

This still has the same problem that running a multi_v7_defconfig
kernel or a binary distro kernel will always enable both. We really
want to have a good run-time decision, not compile-time.

	Arnd

  parent reply	other threads:[~2015-11-02 21:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30  8:27 [PATCH] clocksource: dw_apb_timer_of: support timer-based delay Jisheng Zhang
2015-10-30 10:14 ` Jisheng Zhang
2015-10-30 10:44 ` Daniel Lezcano
2015-10-30 11:09   ` Jisheng Zhang
2015-10-30 12:37     ` Daniel Lezcano
2015-11-02  2:51       ` Jisheng Zhang
2015-11-02  8:48         ` Daniel Lezcano
2015-11-02 13:33           ` Jisheng Zhang
2015-11-02 21:49           ` Arnd Bergmann [this message]
2015-10-30 12:42     ` Arnd Bergmann
2015-11-02  3:03       ` Jisheng Zhang
2015-11-02 21:56         ` Arnd Bergmann
2015-11-03  6:59           ` Jisheng Zhang
2015-11-03  8:49             ` Arnd Bergmann
2015-11-03  9:45               ` Jisheng Zhang

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=4138087.gESYTxjr8X@wuerfel \
    --to=arnd@arndb.de \
    --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