From: Ben Dooks <ben-linux@fluff.org>
To: linux-samsung-soc@vger.kernel.org
Subject: identifying s5p based devices
Date: Thu, 14 Jan 2010 07:01:32 +0000 [thread overview]
Message-ID: <20100114070132.GS3738@trinity.fluff.org> (raw)
After thinking about previous discussions with Samsng SystemLSI group
about the newer SoC and lack of continuty in the placement of the device
identification register I was thinking the following:
Woud it be possible to probe each possible ID register location to see
if there is a valid identity there and stop once a valid one is read?
IE:
void __iomem *idplaces = {
...
....
}
...
for (r in idplaces) {
id = __raw_readl(r);
cpu = cpu_find(r);
if (cpu) {
print_cpu_id(cpu);
break;
}
}
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
reply other threads:[~2010-01-14 7:01 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=20100114070132.GS3738@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=linux-samsung-soc@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 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.