linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource: arm_arch_timer: control the evtstrm via the cmdline
Date: Mon, 27 Jun 2016 19:02:40 +0200	[thread overview]
Message-ID: <57715C30.4000202@linaro.org> (raw)
In-Reply-To: <1467045013-27211-1-git-send-email-will.deacon@arm.com>

On 06/27/2016 06:30 PM, Will Deacon wrote:
> Disabling the eventstream can be useful for both remotely debugging a
> deployed production system and development of code using WFE-based
> polling loops. Whilst this can currently be controlled via a Kconfig
> option (CONFIG_ARM_ARCH_TIMER_EVTSTREAM), it's often desirable to toggle
> the feature on the command line, so this patch adds a new command-line
> option ("clocksource.arm_arch_timer.evtstrm") to do just that. The
> default behaviour is determined based on CONFIG_ARM_ARCH_TIMER_EVTSTREAM.
>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
> ---

Sounds good for me. I will take it through my tree.

By the way, I would like to do some cleanups in the Kconfig and 
consistently change the Kconfig options to be silent without the 
COMPILE_TEST option.

I am wondering if we can just remove the ARM_ARCH_TIMER_EVTSTREAM option 
with this patch applied and always enable it by default (like what is 
done today).

   -- Daniel

-- 
  <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

      reply	other threads:[~2016-06-27 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 16:30 [PATCH] clocksource: arm_arch_timer: control the evtstrm via the cmdline Will Deacon
2016-06-27 17:02 ` Daniel Lezcano [this message]

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=57715C30.4000202@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --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).