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 v2 0/4] arm: zynq: Enable global timer
Date: Wed, 25 Sep 2013 17:20:43 +0200	[thread overview]
Message-ID: <5242FF4B.6050901@linaro.org> (raw)
In-Reply-To: <1379530118-22813-1-git-send-email-soren.brinkmann@xilinx.com>

On 09/18/2013 08:48 PM, Soren Brinkmann wrote:
> Hi all,
> 
> here's a v2. I reused the subject from my v1 submission although the focus of
> this series moved a bit towards the timer subsystem.
> I replaced Stephen's fix to prevent per cpu devices from becoming
> the broadcast device with Thomas' proposal, but I kept the original commit
> message. I split the whole approach in small chunks that I found reasonable.
> 
> In 4/4, I picked up Grant's comment regarding the DT node name.
> 
> v2:
>  - drop 1/2 of the original series
>  - implement preventing per cpu devices from becoming broadcast device according
>    to Thomas' proposal
>    - introduce new CLOCK_EVT_FEAT_PERCPU flag
>    - set the flag for the arm_global_timer
>    - filter per cpu devices based on this flag when choosing the broadcast
>      device
>  - rename DT node to avoid '_'s
>  
> 
> Soren Brinkmann (4):
>   clockchips: Add FEAT_PERCPU clockevent flag
>   clocksource/arm_global_timer: Set FEAT_PERCPU flag
>   tick: broadcast: Deny per-cpu clockevents from being broadcast sources
>   arm: zynq: Enable arm_global_timer
> 
>  arch/arm/boot/dts/zynq-7000.dtsi       | 8 ++++++++
>  arch/arm/mach-zynq/Kconfig             | 1 +
>  drivers/clocksource/arm_global_timer.c | 3 ++-
>  include/linux/clockchips.h             | 1 +
>  kernel/time/tick-broadcast.c           | 1 +
>  5 files changed, 13 insertions(+), 1 deletion(-)

This patches falls under different maintainer's umbrella.

I acked-by the patches, so if someone is willing to take the patches I
am ok with that. I am ok also to pick them into my tree with the
acked-by maintainer. Just let me know ...

Thanks
  -- 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

  parent reply	other threads:[~2013-09-25 15:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 18:48 [PATCH v2 0/4] arm: zynq: Enable global timer Soren Brinkmann
2013-09-18 18:48 ` [PATCH v2 1/4] clockchips: Add FEAT_PERCPU clockevent flag Soren Brinkmann
2013-09-25 15:10   ` Daniel Lezcano
2013-09-18 18:48 ` [PATCH v2 2/4] clocksource/arm_global_timer: Set FEAT_PERCPU flag Soren Brinkmann
2013-09-25 15:10   ` Daniel Lezcano
2013-09-26 10:38   ` Srinivas KANDAGATLA
2013-09-18 18:48 ` [PATCH v2 3/4] tick: broadcast: Deny per-cpu clockevents from being broadcast sources Soren Brinkmann
2013-09-25 15:11   ` Daniel Lezcano
2013-09-18 18:48 ` [PATCH v2 4/4] arm: zynq: Enable arm_global_timer Soren Brinkmann
2013-09-25 15:20 ` Daniel Lezcano [this message]
2013-09-25 15:37   ` [PATCH v2 0/4] arm: zynq: Enable global timer Sören Brinkmann
2013-09-26  8:16   ` Michal Simek
2013-09-26 10:14     ` Daniel Lezcano

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=5242FF4B.6050901@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).