linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: maz@misterjones.org (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Samsung SoCs: CPU detection support (v4)
Date: Wed, 24 Mar 2010 12:39:19 +0100	[thread overview]
Message-ID: <f333d3ab46b3a4d82c3406199326fc81@localhost> (raw)
In-Reply-To: <20100324070943.GA6779@july>


On Wed, 24 Mar 2010 16:09:43 +0900, Kyungmin Park <kmpark@infradead.org>
wrote:
> Store the CPU ID to cpu_id variable and use it to detect CPU
> 
> On S3C64XX, Some pheripherals such as OneNAND have different
configuration
> and handle it differently to do this it needs to detect CPU ID.
> 
> Also S5PC1XX is supported.

For the sake of completeness, would you consider adding support for
s5p6440?

        M.
-- 
Who you jivin' with that Cosmik Debris?

  reply	other threads:[~2010-03-24 11:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24  7:09 [PATCH] Samsung SoCs: CPU detection support (v4) Kyungmin Park
2010-03-24 11:39 ` Marc Zyngier [this message]
2010-03-31  1:04 ` Ben Dooks
2010-03-31  3:00   ` Kyungmin Park

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=f333d3ab46b3a4d82c3406199326fc81@localhost \
    --to=maz@misterjones.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).