All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tudor Laurentiu <Laurentiu.Tudor@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc/time: When starting the decrementer don't zero the other bits in TCR
Date: Thu, 1 Sep 2011 11:31:10 +0300	[thread overview]
Message-ID: <4E5F42CE.1060502@freescale.com> (raw)
In-Reply-To: <9A0167AA-E19D-4492-8D65-6FA4518ABE98@kernel.crashing.org>

On 9/1/2011 9:27 AM, Kumar Gala wrote:
>
> On Aug 25, 2011, at 7:19 AM, Laurentiu Tudor wrote:
>
>> Clearing the other TCR bits might break code that sets them (e.g. to setup
>> the watchdog or fixed interval timer) before start_cpu_decrementer() gets
>> called.
>
> Can you be more specific about the case you're concerned about.  I'm not sure we want to leave the FIT enabled if it was previously.  Watchdog I could possibly see leaving alone.

My particular case was this: I was experimenting with having the 
watchdog enabled during the boot process, in case something goes wrong 
before the normal watchdog mechanism kicks in. That didn't work without 
making this modification.
Then, thinking that having a function start_cpu_decrementer() touching 
the other timers and not only the decrementer as its name implies might 
not be good. So I submitted this patch to the public mailing list to let 
the community decide if it's useful.

>> Signed-off-by: Laurentiu Tudor<Laurentiu.Tudor@freescale.com>
>> ---
>> arch/powerpc/kernel/time.c |    2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/powerpc/kernel/time.c b/arch/powerpc/kernel/time.c
>> index 03b29a6..e8b5cdc 100644
>> --- a/arch/powerpc/kernel/time.c
>> +++ b/arch/powerpc/kernel/time.c
>> @@ -721,7 +721,7 @@ void start_cpu_decrementer(void)
>> 	mtspr(SPRN_TSR, TSR_ENW | TSR_WIS | TSR_DIS | TSR_FIS);
>>
>> 	/* Enable decrementer interrupt */
>> -	mtspr(SPRN_TCR, TCR_DIE);
>> +	mtspr(SPRN_TCR, mfspr(SPRN_TCR) | TCR_DIE);
>> #endif /* defined(CONFIG_BOOKE) || defined(CONFIG_40x) */
>> }
>>
>> --
>> 1.7.1
>>
>>
>> _______________________________________________
>> Linuxppc-dev mailing list
>> Linuxppc-dev@lists.ozlabs.org
>> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
>

  reply	other threads:[~2011-09-01  8:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25 12:19 [PATCH] powerpc/time: When starting the decrementer don't zero the other bits in TCR Laurentiu Tudor
2011-09-01  6:27 ` Kumar Gala
2011-09-01  8:31   ` Tudor Laurentiu [this message]
2011-09-01 13:56     ` Kumar Gala
2011-09-01 15:38       ` Tudor Laurentiu
2011-09-01 18:49         ` Kumar Gala

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=4E5F42CE.1060502@freescale.com \
    --to=laurentiu.tudor@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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 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.