From: slawomir.cygan@gmail.com (Sławomir Cygan)
To: linux-arm-kernel@lists.infradead.org
Subject: hard coded value for idcode field in struct cpu_table
Date: Sat, 5 Mar 2011 14:50:58 +0100 [thread overview]
Message-ID: <AANLkTi=1zJoGwOXCbAaCn=+wRuAjgBsOUvKhOPqH0SaF@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinYBcaOcuOMQBy+gN8h2i+fEOR9zT0c3DZQdP57@mail.gmail.com>
On Thu, Mar 3, 2011 at 2:49 PM, Madhavi Manchala
<madhavi.linux@gmail.com> wrote:
> Dear All,
>
> I do not understand the value of idcode field in the struct cpu_table
> i.e. the value is hard coded. I did not find that value in the user
> manuals also. The code is available at
> linux/arch/arm/plat-s3c24xx/cpu.c file. Currently, I am implementing
> code for Samsung S3C2510A processor which is not available in the
> current sources. Where can I find the idcode value for Samsung
> S3C2510A processor?
>
> Any ideas will be appreciated.
>
> Thanks and ?Regards,
> Madhavi M.
>
Hi,
This field is defined for example in this datasheed:
http://www.alldatasheet.com/datasheet-pdf/pdf/84872/SAMSUNG/S3C2410A.html
PDF page 282:
GENERAL STATUS REGISTER (GSTATUSn)
Register Address R/W Description Reset Value
GSTATUS0 0x560000AC R External pin status Undefined
>>>>> GSTATUS1 0x560000B0 R Chip ID 0x32410000 <<<
GSTATUS2 0x560000B4 R/W Reset status 0x1
GSTATUS3 0x560000B8 R/W Infrom register 0x0
GSTATUS4 0x560000BC R/W Infrom register 0x0
This is "GSTATUS1" register initial value
I don't think that S3c25 are so similar to S3c25, so they provide
exactly the same method of chip identification.
--
Pozdrawiam,
S?awomir Cygan
next prev parent reply other threads:[~2011-03-05 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 13:49 hard coded value for idcode field in struct cpu_table Madhavi Manchala
2011-03-05 13:50 ` Sławomir Cygan [this message]
2011-03-06 7:51 ` Madhavi Manchala
2011-03-06 18:49 ` Sławomir Cygan
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='AANLkTi=1zJoGwOXCbAaCn=+wRuAjgBsOUvKhOPqH0SaF@mail.gmail.com' \
--to=slawomir.cygan@gmail.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).