All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] xtensa: Switch to sched_clock_register()
@ 2013-11-15 23:31 Stephen Boyd
  2013-11-17 20:27 ` Max Filippov
  0 siblings, 1 reply; 5+ messages in thread
From: Stephen Boyd @ 2013-11-15 23:31 UTC (permalink / raw)
  To: Chris Zankel, Max Filippov; +Cc: linux-xtensa, linux-kernel, John Stultz

The 32 bit sched_clock interface now supports 64 bits. Upgrade
to the 64 bit function to allow us to remove the 32 bit
registration interface.

Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
---

Patch is based on Linus' tip. Not event compile tested.

 arch/xtensa/kernel/time.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/xtensa/kernel/time.c b/arch/xtensa/kernel/time.c
index 9af3dd8..415c3f6 100644
--- a/arch/xtensa/kernel/time.c
+++ b/arch/xtensa/kernel/time.c
@@ -36,7 +36,7 @@ static cycle_t ccount_read(struct clocksource *cs)
 	return (cycle_t)get_ccount();
 }
 
-static u32 notrace ccount_sched_clock_read(void)
+static u64 notrace ccount_sched_clock_read(void)
 {
 	return get_ccount();
 }
@@ -141,7 +141,7 @@ void __init time_init(void)
 	setup_irq(ccount_timer.evt.irq, &timer_irqaction);
 	ccount_timer.irq_enabled = 1;
 
-	setup_sched_clock(ccount_sched_clock_read, 32, ccount_freq);
+	sched_clock_register(ccount_sched_clock_read, 32, ccount_freq);
 }
 
 /*
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation


^ permalink raw reply related	[flat|nested] 5+ messages in thread

* Re: [PATCH] xtensa: Switch to sched_clock_register()
  2013-11-15 23:31 [PATCH] xtensa: Switch to sched_clock_register() Stephen Boyd
@ 2013-11-17 20:27 ` Max Filippov
  2013-11-20 18:26   ` Stephen Boyd
  0 siblings, 1 reply; 5+ messages in thread
From: Max Filippov @ 2013-11-17 20:27 UTC (permalink / raw)
  To: Stephen Boyd; +Cc: Chris Zankel, linux-xtensa, LKML, John Stultz

On Sat, Nov 16, 2013 at 3:31 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
> The 32 bit sched_clock interface now supports 64 bits. Upgrade
> to the 64 bit function to allow us to remove the 32 bit
> registration interface.
>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> ---
>
> Patch is based on Linus' tip. Not event compile tested.
>
>  arch/xtensa/kernel/time.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Build and run-tested, appears to work.
Acked-by: Max Filippov <jcmvbkbc@gmail.com>

Should it go through xtensa tree, or through some other tree as a part
of a bigger conversion series?

> diff --git a/arch/xtensa/kernel/time.c b/arch/xtensa/kernel/time.c
> index 9af3dd8..415c3f6 100644
> --- a/arch/xtensa/kernel/time.c
> +++ b/arch/xtensa/kernel/time.c
> @@ -36,7 +36,7 @@ static cycle_t ccount_read(struct clocksource *cs)
>         return (cycle_t)get_ccount();
>  }
>
> -static u32 notrace ccount_sched_clock_read(void)
> +static u64 notrace ccount_sched_clock_read(void)
>  {
>         return get_ccount();
>  }
> @@ -141,7 +141,7 @@ void __init time_init(void)
>         setup_irq(ccount_timer.evt.irq, &timer_irqaction);
>         ccount_timer.irq_enabled = 1;
>
> -       setup_sched_clock(ccount_sched_clock_read, 32, ccount_freq);
> +       sched_clock_register(ccount_sched_clock_read, 32, ccount_freq);
>  }
>
>  /*
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> hosted by The Linux Foundation
>



-- 
Thanks.
-- Max

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH] xtensa: Switch to sched_clock_register()
  2013-11-17 20:27 ` Max Filippov
@ 2013-11-20 18:26   ` Stephen Boyd
  2013-12-12 23:54     ` Stephen Boyd
  0 siblings, 1 reply; 5+ messages in thread
From: Stephen Boyd @ 2013-11-20 18:26 UTC (permalink / raw)
  To: Max Filippov; +Cc: Chris Zankel, linux-xtensa, LKML, John Stultz

On 11/17/13 12:27, Max Filippov wrote:
> On Sat, Nov 16, 2013 at 3:31 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>> The 32 bit sched_clock interface now supports 64 bits. Upgrade
>> to the 64 bit function to allow us to remove the 32 bit
>> registration interface.
>>
>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>> ---
>>
>> Patch is based on Linus' tip. Not event compile tested.
>>
>>  arch/xtensa/kernel/time.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
> Build and run-tested, appears to work.
> Acked-by: Max Filippov <jcmvbkbc@gmail.com>
>
> Should it go through xtensa tree, or through some other tree as a part
> of a bigger conversion series?

If it can go through xtensa that sounds like the best option. Otherwise
we can send it through the tip/timers tree.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH] xtensa: Switch to sched_clock_register()
  2013-11-20 18:26   ` Stephen Boyd
@ 2013-12-12 23:54     ` Stephen Boyd
  2013-12-13  0:00       ` czankel
  0 siblings, 1 reply; 5+ messages in thread
From: Stephen Boyd @ 2013-12-12 23:54 UTC (permalink / raw)
  To: Max Filippov; +Cc: Chris Zankel, linux-xtensa, LKML, John Stultz

On 11/20/13 10:26, Stephen Boyd wrote:
> On 11/17/13 12:27, Max Filippov wrote:
>> On Sat, Nov 16, 2013 at 3:31 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>>> The 32 bit sched_clock interface now supports 64 bits. Upgrade
>>> to the 64 bit function to allow us to remove the 32 bit
>>> registration interface.
>>>
>>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>>> ---
>>>
>>> Patch is based on Linus' tip. Not event compile tested.
>>>
>>>  arch/xtensa/kernel/time.c | 4 ++--
>>>  1 file changed, 2 insertions(+), 2 deletions(-)
>> Build and run-tested, appears to work.
>> Acked-by: Max Filippov <jcmvbkbc@gmail.com>
>>
>> Should it go through xtensa tree, or through some other tree as a part
>> of a bigger conversion series?
> If it can go through xtensa that sounds like the best option. Otherwise
> we can send it through the tip/timers tree.
>

Ping? I don't see this patch in linux-next yet so should I send this
through the tip/timers tree?

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH] xtensa: Switch to sched_clock_register()
  2013-12-12 23:54     ` Stephen Boyd
@ 2013-12-13  0:00       ` czankel
  0 siblings, 0 replies; 5+ messages in thread
From: czankel @ 2013-12-13  0:00 UTC (permalink / raw)
  To: Stephen Boyd, Max Filippov; +Cc: linux-xtensa, LKML, John Stultz

Hi Stephen,

Sorry for the delay. Will add it later today.

Thanks,
-Chris

On 12/12/13 3:54 PM, Stephen Boyd wrote:
> On 11/20/13 10:26, Stephen Boyd wrote:
>> On 11/17/13 12:27, Max Filippov wrote:
>>> On Sat, Nov 16, 2013 at 3:31 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>>>> The 32 bit sched_clock interface now supports 64 bits. Upgrade
>>>> to the 64 bit function to allow us to remove the 32 bit
>>>> registration interface.
>>>>
>>>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>>>> ---
>>>>
>>>> Patch is based on Linus' tip. Not event compile tested.
>>>>
>>>>   arch/xtensa/kernel/time.c | 4 ++--
>>>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>> Build and run-tested, appears to work.
>>> Acked-by: Max Filippov <jcmvbkbc@gmail.com>
>>>
>>> Should it go through xtensa tree, or through some other tree as a part
>>> of a bigger conversion series?
>> If it can go through xtensa that sounds like the best option. Otherwise
>> we can send it through the tip/timers tree.
>>
> Ping? I don't see this patch in linux-next yet so should I send this
> through the tip/timers tree?
>


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2013-12-13  0:00 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-11-15 23:31 [PATCH] xtensa: Switch to sched_clock_register() Stephen Boyd
2013-11-17 20:27 ` Max Filippov
2013-11-20 18:26   ` Stephen Boyd
2013-12-12 23:54     ` Stephen Boyd
2013-12-13  0:00       ` czankel

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.