On Tue, Jan 15, 2013 at 11:24:53AM +, Thomas Gleixner wrote:
> On Mon, 14 Jan 2013, Mark Rutland wrote:
> > On Mon, Jan 14, 2013 at 02:17:26PM +, Thomas Gleixner wrote:
> > > > I thought this previously also [1], but I couldn't find any path such
> > > > that a
> > > > tick_cpu_device woul
On Mon, 14 Jan 2013, Mark Rutland wrote:
> On Mon, Jan 14, 2013 at 02:17:26PM +, 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
> > > h
On Monday 14 January 2013 09:06 PM, Mark Rutland wrote:
On Mon, Jan 14, 2013 at 02:17:26PM +, Thomas Gleixner wrote:
On Mon, 14 Jan 2013, Mark Rutland wrote:
On Mon, Jan 14, 2013 at 11:50:55AM +, Thomas Gleixner wrote:
On Mon, 14 Jan 2013, Mark Rutland wrote:
On Mon, Jan 14, 2013 at
On Mon, Jan 14, 2013 at 02:17:26PM +, Thomas Gleixner wrote:
> On Mon, 14 Jan 2013, Mark Rutland wrote:
> > On Mon, Jan 14, 2013 at 11:50:55AM +, Thomas Gleixner wrote:
> > > On Mon, 14 Jan 2013, Mark Rutland wrote:
> > >
> > > > On Mon, Jan 14, 2013 at 11:06:31AM +, Thomas Gleixner wr
On Mon, 14 Jan 2013, Mark Rutland wrote:
> On Mon, Jan 14, 2013 at 11:50:55AM +, Thomas Gleixner wrote:
> > On Mon, 14 Jan 2013, Mark Rutland wrote:
> >
> > > On Mon, Jan 14, 2013 at 11:06:31AM +, Thomas Gleixner wrote:
> > > > On Wed, 9 Jan 2013, Mark Rutland wrote:
> > > > > +#ifdef CONF
On Mon, Jan 14, 2013 at 11:50:55AM +, Thomas Gleixner wrote:
> On Mon, 14 Jan 2013, Mark Rutland wrote:
>
> > On Mon, Jan 14, 2013 at 11:06:31AM +, Thomas Gleixner wrote:
> > > On Wed, 9 Jan 2013, Mark Rutland wrote:
> > > > +#ifdef CONFIG_GENERIC_CLOCKEVENTS_BROADCAST
> > > > +extern int
On Mon, 14 Jan 2013, Mark Rutland wrote:
> On Mon, Jan 14, 2013 at 11:06:31AM +, Thomas Gleixner wrote:
> > On Wed, 9 Jan 2013, Mark Rutland wrote:
> > > +#ifdef CONFIG_GENERIC_CLOCKEVENTS_BROADCAST
> > > +extern int tick_receive_broadcast(void);
> > > +#else
> > > +static inline int tick_rece
On Mon, Jan 14, 2013 at 11:06:31AM +, Thomas Gleixner wrote:
> On Wed, 9 Jan 2013, Mark Rutland wrote:
> > +#ifdef CONFIG_GENERIC_CLOCKEVENTS_BROADCAST
> > +extern int tick_receive_broadcast(void);
> > +#else
> > +static inline int tick_receive_broadcast(void)
> > +{
> > + return 0;
> > +}
>
On Wed, 9 Jan 2013, Mark Rutland wrote:
> +#ifdef CONFIG_GENERIC_CLOCKEVENTS_BROADCAST
> +extern int tick_receive_broadcast(void);
> +#else
> +static inline int tick_receive_broadcast(void)
> +{
> + return 0;
> +}
What's the inline function for? If an arch does not have broadcasting
support it
Currently the broadcast mechanism used for timers is abstracted by a
function pointer on struct clock_event_device. As the fundamental
mechanism for broadcast is architecture-specific, this ties each
clock_event_device driver to a single architecture, even where the
driver is otherwise generic.
Th
10 matches
Mail list logo