All of lore.kernel.org
 help / color / mirror / Atom feed
From: gerg@snapgear.com (Greg Ungerer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: fix use of clock disable on idle for simple AT91 devices
Date: Tue, 21 Sep 2010 20:38:29 +1000	[thread overview]
Message-ID: <4C988B25.6020501@snapgear.com> (raw)
In-Reply-To: <20100920151511.GE32018@game.jcrosoft.org>

On 21/09/10 01:15, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 10:14 Mon 20 Sep     , Jean-Christophe PLAGNIOL-VILLARD wrote:
>> On 11:22 Wed 08 Sep     , Greg Ungerer wrote:
>>>
>>> Not all types of AT91 device have the PMC hardware unit. Don't do a
>>> clock disable at idle on those family members that don't have it.
>>>
>>> Signed-off-by: Greg Ungerer<gerg@uclinux.org>
>>> ---
>>>   arch/arm/mach-at91/include/mach/system.h |    2 +-
>>>   1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/arch/arm/mach-at91/include/mach/system.h b/arch/arm/mach-at91/include/mach/system.h
>>> index c80e090..0bc497f 100644
>>> --- a/arch/arm/mach-at91/include/mach/system.h
>>> +++ b/arch/arm/mach-at91/include/mach/system.h
>>> @@ -28,7 +28,7 @@
>>>
>>>   static inline void arch_idle(void)
>>>   {
>>> -#ifndef CONFIG_DEBUG_KERNEL
>>> +#if defined(AT91_PMC)&&  !defined(CONFIG_DEBUG_KERNEL)
>> we can do this on at91x40 also
> cf PS Control Register
> p52 of the datasheet

Personally I see no problem with the old functionality (not using
the clock disable) for the AT91x40 devices. But then I don't run
on real hardware, only emulators.

A patch follows using the PS CPU clock disable bit. I think it
is more ugly than the first patch. Of course I can only test it
in an emulator (skyeye), works on that.

Regards
Greg

      reply	other threads:[~2010-09-21 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08  1:22 [PATCH] arm: fix use of clock disable on idle for simple AT91 devices Greg Ungerer
2010-09-20  8:14 ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-20 15:15   ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-21 10:38     ` Greg Ungerer [this message]

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=4C988B25.6020501@snapgear.com \
    --to=gerg@snapgear.com \
    --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 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.