From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Identifying Primecells
Date: Fri, 23 Sep 2011 20:53:33 +0100 [thread overview]
Message-ID: <20110923195333.GR17169@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAKON4OxHwjrw-dhH2qvXopqUqmKSx2TCPgW4eVHF9dmQO4=Cvw@mail.gmail.com>
On Fri, Sep 23, 2011 at 10:17:32AM -0400, jonsmirl at gmail.com wrote:
> My registers don't seem to match up with the pl011 documentation...
>
> Table 437. Register overview: UART (register base address 0x1500 1000)
> Name R/W Address Offset Description
> RBR R 0x000 Receiver Buffer Register
> THR W 0x000 Transmitter Holding Register
> DLL R/W 0x000 Divisor Latch LSB
> DLM R/W 0x004 Divisor Latch MSB
> IER R/W 0x004 Interrupt Enable Register
> IIR R 0x008 Interrupt Identification Register
> FCR W 0x008 FIFO Control Register
> LCR R/W 0x00C Line Control Register
> MCR R/W 0x010 Modem Control Register
> LSR R 0x014 Line Status Register
> MSR R 0x018 Modem Status Register
> SCR R/W 0x01C Scratch Register
This looks like an 8250 like clone. You might be about to get away
with using a platform device for the 8250 driver specifying an io
shift of 2, base address 0x15001000.
What worries me is the extra registers below, and whether they need to
be programmed to something at runtime (rather than just being able to
rely on the standard 8250 register set.)
> - - 0x020 Reserved
> ICR R/W 0x024 IrDA Control Register
> FDR R/W 0x028 Fractional Divider Register
> - - 0x02C Reserved
> POP W 0x030 NHP Pop Register
> MODE R/W 0x034 NHP Mode Selection Register
> - - 0x038-0xFD4 Reserved
> INTCE W 0xFD8 Interrupt Clear Enable Register
> INTSE W 0xFDC Interrupt Set Enable Register
> INTS R 0xFE0 Interrupt Status Register
> INTE R 0xFE4 Interrupt Enable Register
prev parent reply other threads:[~2011-09-23 19:53 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
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 [this message]
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=20110923195333.GR17169@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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