linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: mxs: use CHIPID hardware to detect SoC
Date: Fri,  6 Jan 2012 10:41:50 +0800	[thread overview]
Message-ID: <1325817712-4573-1-git-send-email-shawn.guo@linaro.org> (raw)

As suggested by Wolfram, the first patch changes cpu_is_xxx and
__arch_decomp_setup to use the CHIPID register than machine type to
detect the chip between imx23 and imx28, so that we do not need to
change these functions whenever a new board/machine gets added.

The second one is a rebase of patch [1] on above patch.

Regards,
Shawn

[1] [PATCH v4] ARM: mxs: Add initial support for Bluegiga APX4 Development Kit

---

Lauri Hintsala (1):
      ARM: mxs: Add initial support for Bluegiga APX4 Development Kit

Shawn Guo (1):
      ARM: mxs: detect SoC by checking CHIPID register

 arch/arm/mach-mxs/Kconfig                   |   16 ++
 arch/arm/mach-mxs/Makefile                  |    1 +
 arch/arm/mach-mxs/include/mach/mxs.h        |   28 ++--
 arch/arm/mach-mxs/include/mach/uncompress.h |   11 +-
 arch/arm/mach-mxs/mach-apx4devkit.c         |  245 +++++++++++++++++++++++++++
 5 files changed, 283 insertions(+), 18 deletions(-)

             reply	other threads:[~2012-01-06  2:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06  2:41 Shawn Guo [this message]
2012-01-06  2:41 ` [PATCH 1/2] ARM: mxs: detect SoC by checking CHIPID register Shawn Guo
2012-01-06 11:40   ` Wolfram Sang
2012-01-06 13:39     ` Shawn Guo
2012-01-06 13:43       ` Wolfram Sang
2012-01-06  2:41 ` [PATCH 2/2] ARM: mxs: Add initial support for Bluegiga APX4 Development Kit Shawn Guo
2012-01-06 11:26 ` [PATCH 0/2] ARM: mxs: use CHIPID hardware to detect SoC Lauri Hintsala

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=1325817712-4573-1-git-send-email-shawn.guo@linaro.org \
    --to=shawn.guo@linaro.org \
    --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).