From: Scott Wood <scottwood@freescale.com>
To: Alan Bennett <embedded@akb.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Serial init / BRG
Date: Tue, 16 Oct 2007 11:31:31 -0500 [thread overview]
Message-ID: <4714E763.5060901@freescale.com> (raw)
In-Reply-To: <bfa0697f0710160719r44099b19jbda55af2ef88e9f8@mail.gmail.com>
Alan Bennett wrote:
> A few questions: To use 3 brgs, should I have 1 brg entry and X reg
> values or three brg entries in my device tree?
The current brg entry describes all 8 BRGs... don't touch it. :-)
> what are the third and fourth reg values of the brg item in the
> device tree. I'll need 3 separate baud rates on the serial lines.
> Should I just add code to initialize the brg's in u-boot or figure
> out how to get the kernel to do it?
No, the kernel should do it. Are you associating the BRG with the SCC
in the CMXSCR register, and setting up the pins required by SCC1 and
SCC4, in either u-boot or your platform code?
> boot sequence
> ===========
> CPM UART serial mem=e0011a80 pram=e0000000
> ttyCPM0 at MMIO 0xe0011a80 (irq = 16) is a CPM UART
>
> CPM UART serial mem=e0011a00 pram=e0008000
> CPM uart[1]:init_scc - sup = e0008000
> ttyCPM1 at MMIO 0xe0011a00 (irq = 40) is a CPM UART
>
> CPM UART serial mem=e0011a60 pram=e0008300
> CPM uart[2]:init_scc - sup = e0008300
> ttyCPM2 at MMIO 0xe0011a60 (irq = 43) is a CPM UART
>
> BRG Values after above
> =================
> brgc1: 0x00000000
> brgc2: 0x00000000
> brgc3: 0x00000000
> brgc4: 0x00000000
> brgc5: 0x00000000
> brgc6: 0x00000000
> brgc7: 0x0001004e
> brgc8: 0x00000000
This is expected if you haven't opened the other serial ports yet... it
doesn't initialize the brg until then.
-Scott
next prev parent reply other threads:[~2007-10-16 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 14:19 Serial init / BRG Alan Bennett
2007-10-16 16:31 ` Scott Wood [this message]
[not found] ` <bfa0697f0710161114y6273af8fre045328b638a9de7@mail.gmail.com>
[not found] ` <47152065.9070403@freescale.com>
2007-10-16 21:38 ` Alan Bennett
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=4714E763.5060901@freescale.com \
--to=scottwood@freescale.com \
--cc=embedded@akb.net \
--cc=linuxppc-dev@ozlabs.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).