linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFT 0/12] step towards removal of mach/system.h
Date: Tue, 25 Oct 2011 13:21:07 +0100	[thread overview]
Message-ID: <20111025122107.GA6892@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1319449801-12367-1-git-send-email-nico@fluxnic.net>

Hi Nico,

On Mon, Oct 24, 2011 at 10:49:49AM +0100, Nicolas Pitre wrote:
> In the spirit of eventually being able to boot a single zImage on multiple
> SOCs, we need to get rid of mach/system.h.  This file mainly contains two
> inline functions that should be out-of-line and assigned to the existing global
> hooks at run time.  Those functions are arch_idle() and arch_reset().  The
> following series only address the former.

I'm looking at the latter, but I'm losing the will to live in the process.

> [PATCH 01/12] ARM: clean up idle handlers
> [PATCH 02/12] ARM: mach-at91: move special idle code to a
> [PATCH 03/12] ARM: mach-clps711x: move special idle code to a
> [PATCH 04/12] ARM: mach-ebsa110: move special idle code to a
> [PATCH 05/12] ARM: mach-gemini: move special idle code to a
> [PATCH 06/12] ARM: mach-h720x: move special idle code to a
> [PATCH 07/12] ARM: mach-ixp23xx: properly disable CPU idle call
> [PATCH 08/12] ARM: mach-ixp4xx: properly disable CPU idle call
> [PATCH 09/12] ARM: s3c24xx: move special idle code to a proper
> [PATCH 10/12] ARM: mach-shark: properly disable CPU idle call
> [PATCH 11/12] ARM: mach-w90x900: properly disable CPU idle call
> [PATCH 12/12] ARM: imx: move special idle code to proper out-of-line

I think you might need to hack on mach-msm too as they have an
implementation of arch_idle which is written in assembly (for reasons which
aren't obvious to me).

Will

      parent reply	other threads:[~2011-10-25 12:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24  9:49 [PATCH/RFT 0/12] step towards removal of mach/system.h Nicolas Pitre
2011-10-24  9:49 ` [PATCH 01/12] ARM: clean up idle handlers Nicolas Pitre
2011-10-25  7:56   ` Tony Lindgren
2011-10-25  8:26     ` Russell King - ARM Linux
2011-10-25 11:37   ` Russell King - ARM Linux
2011-10-24  9:49 ` [PATCH 02/12] ARM: mach-at91: move special idle code to a out-of-line pm_idle hook Nicolas Pitre
2011-10-24  9:49 ` [PATCH 03/12] ARM: mach-clps711x: " Nicolas Pitre
2011-10-24  9:49 ` [PATCH 04/12] ARM: mach-ebsa110: " Nicolas Pitre
2011-10-24  9:49 ` [PATCH 05/12] ARM: mach-gemini: " Nicolas Pitre
2011-10-24  9:49 ` [PATCH 06/12] ARM: mach-h720x: " Nicolas Pitre
2011-10-24  9:49 ` [PATCH 07/12] ARM: mach-ixp23xx: properly disable CPU idle call Nicolas Pitre
2011-10-24  9:49 ` [PATCH 08/12] ARM: mach-ixp4xx: " Nicolas Pitre
2011-10-25 11:39   ` Russell King - ARM Linux
2011-10-24  9:49 ` [PATCH 09/12] ARM: s3c24xx: move special idle code to a proper out-of-line pm_idle hooks Nicolas Pitre
2011-10-24  9:49 ` [PATCH 10/12] ARM: mach-shark: properly disable CPU idle call Nicolas Pitre
2011-10-24  9:50 ` [PATCH 11/12] ARM: mach-w90x900: " Nicolas Pitre
2011-10-24  9:50 ` [PATCH 12/12] ARM: imx: move special idle code to proper out-of-line pm_idle hooks Nicolas Pitre
2011-10-24 12:58   ` Sascha Hauer
2011-10-25 12:21 ` Will Deacon [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=20111025122107.GA6892@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).