From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: hwblk base implementation
Date: Sat, 04 Jul 2009 15:40:15 +0000 [thread overview]
Message-ID: <20090704154014.GE9933@linux-sh.org> (raw)
On Fri, Jul 03, 2009 at 07:08:05PM +0900, Magnus Damm wrote:
> This patch is the hwblk base implementation, containing
> structures and shared functions dealing with hardware blocks.
>
> A each processor model should provide a list of hwblks and
> describe which module stop bit that is associated with each
> hwblck and how the hwblks are grouped together into areas.
>
> The shared code keeps track of the usage count for each
> hwblk and the areas. Fallback implementations for processor
> specific code are also kept as weak symbols.
>
> The clock framework, the runtime pm code and cpuidle will
> all tie into this hwblk implementation.
On Fri, Jul 03, 2009 at 07:15:25PM +0900, Magnus Damm wrote:
> This patch contains the sh7722 specific hwblk implementation.
>
> Hwblk ids are added to the processor specific header file,
> module stop bits and areas are kept track of as hwblks,
> clocks are converted to make use of the shared hwblk code.
> Code to determine allowed sleep modes is also added.
On Fri, Jul 03, 2009 at 07:28:00PM +0900, Magnus Damm wrote:
> This patch adds cpuidle support for SuperH Mobile.
>
> The sleep mode selected by cpuidle is compared with
> the mode selected by the hwblk sleep code and the
> best allowed mode is entered.
>
> At this point "Sleep mode" and "Sleep mode + SF" are
> supported. This code can easily be extended to support
> "Software suspend mode", but the assembly code must
> first be updated to avoid loosing interrupts.
>
> Also, update the code to only copy the assembly snippet
> into internal memory once at bootup.
All applied, thanks.
reply other threads:[~2009-07-04 15:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090704154014.GE9933@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox