mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"nico@linaro.org" <nico@linaro.org>,
	Will Deacon <Will.Deacon@arm.com>,
	Marc Zyngier <Marc.Zyngier@arm.com>,
	"john.stultz@linaro.org" <john.stultz@linaro.org>
Subject: Re: [PATCHv2 1/4] clockevents: Add generic timer broadcast receiver
Date: Tue, 15 Jan 2013 12:00:12 +0000	[thread overview]
Message-ID: <20130115120012.GA23333@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1301151224300.7475@ionos>

On Tue, Jan 15, 2013 at 11:24:53AM +0000, Thomas Gleixner wrote:
> On Mon, 14 Jan 2013, Mark Rutland wrote:
> > On Mon, Jan 14, 2013 at 02:17:26PM +0000, Thomas Gleixner wrote:
> > > > I thought this previously also [1], but I couldn't find any path such that a
> > > > tick_cpu_device would have an evtdev without an event_handler. We always set the
> > > > handler before setting evtdev, and alway wipe evtdev before wiping the handler.
> > > > 
> > > > Have I missed something?
> > > 
> > > That's an x86 specific issue. Though we could try and make that
> > > functionality completely generic.
> > 
> > Just to check: is the evt->event_handler check necessary?
> 
> For x86 yes. See the comment.

Ah, sorry. I misunderstood on my initial reading.

I've posted a version with the evt->event_handler check restored, and the
tick_receive_broadcast stub removed when !CONFIG_GENERIC_CLOCKEVENTS_BROADCAST:

https://lkml.org/lkml/2013/1/14/276

The generic clockevents patches (based on v3.8-rc3) can also be found at
git://linux-arm.org/linux-mr.git tags/timer-broadcast-v3-core

> Thanks,
> 
> 	tglx
> 

Thanks,
Mark.


  reply	other threads:[~2013-01-15 12:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09 14:46 [PATCHv2 0/4] clockevents: decouple broadcast mechanism from drivers Mark Rutland
2013-01-09 14:46 ` [PATCHv2 1/4] clockevents: Add generic timer broadcast receiver Mark Rutland
2013-01-14 11:06   ` Thomas Gleixner
2013-01-14 11:29     ` Mark Rutland
2013-01-14 11:50       ` Thomas Gleixner
2013-01-14 12:12         ` Mark Rutland
2013-01-14 14:17           ` Thomas Gleixner
2013-01-14 15:36             ` Mark Rutland
2013-01-15  6:40               ` Santosh Shilimkar
2013-01-15 11:24               ` Thomas Gleixner
2013-01-15 12:00                 ` Mark Rutland [this message]
2013-01-09 14:46 ` [PATCHv2 2/4] arm: Use " Mark Rutland
2013-01-09 14:46 ` [PATCHv2 3/4] clockevents: Add generic timer broadcast function Mark Rutland
2013-01-14 11:10   ` Thomas Gleixner
2013-01-09 14:46 ` [PATCHv2 4/4] arm: Add generic timer broadcast support Mark Rutland
2013-01-09 20:46 ` [PATCHv2 0/4] clockevents: decouple broadcast mechanism from drivers Stephen Boyd
2013-01-10  9:44   ` Mark Rutland

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=20130115120012.GA23333@e106331-lin.cambridge.arm.com \
    --to=mark.rutland@arm.com \
    --cc=Marc.Zyngier@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@linaro.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®