From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: Identifying Primecells
Date: Fri, 23 Sep 2011 15:10:49 +0100 [thread overview]
Message-ID: <1316787049.4611.920.camel@hornet.cambridge.arm.com> (raw)
In-Reply-To: <CAKON4OxZPFFL5NAgxLPRw2xxnS=v7iVWtQSSLcUJWfOYh4yfjA@mail.gmail.com>
> Is peripheral use documented at ARM for the lpc3130? What I don't know
> is if the peripherals have been modified or replaced with an
> alternative implementation.
>
> So I guess I need to figure out how to read the ID register.
I'm not sure what your problem exactly is, but if you want to know what
PeriphID for PL011 is, have a look here:
http://infocenter.arm.com/help/topic/com.arm.doc.ddi0183g/I18381.html
So if your UART is PL011, reading four 8-bit wide registers at
* base + 0xfe0
* base + 0xfe4
* base + 0xfe8
* base + 0xfec
should give you (respectively):
* 0x11
* 0x10
* 0x_4 (_ depends on the cell revision)
* 0x00
Of course AMBA bus match_id will do this for you so, as I said, I'm not
sure what the problem is...
If you don't know what the base address is, well, only NXP and their
datasheet can help you here.
Cheers!
Pawe?
next prev parent reply other threads:[~2011-09-23 14:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 18:19 Identifying Primecells jonsmirl at gmail.com
2011-09-23 12:46 ` Rob Herring
2011-09-23 13:11 ` jonsmirl at gmail.com
2011-09-23 13:30 ` Rob Herring
2011-09-23 13:35 ` jonsmirl at gmail.com
2011-09-23 14:10 ` Pawel Moll [this message]
2011-09-23 14:17 ` jonsmirl at gmail.com
2011-09-23 14:22 ` jonsmirl at gmail.com
2011-09-23 14:22 ` Pawel Moll
2011-09-23 19:11 ` jonsmirl at gmail.com
2011-09-24 13:27 ` Linus Walleij
2011-09-24 23:15 ` Vitaly Wool
2011-09-25 3:03 ` jonsmirl at gmail.com
2011-09-23 19:53 ` Russell King - ARM Linux
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=1316787049.4611.920.camel@hornet.cambridge.arm.com \
--to=pawel.moll@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