From: "Alan Bennett" <embedded@akb.net>
To: "Scott Wood" <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Serial init / BRG
Date: Tue, 16 Oct 2007 15:38:20 -0600 [thread overview]
Message-ID: <bfa0697f0710161438y5472ced7y92ca981503a45e93@mail.gmail.com> (raw)
In-Reply-To: <47152065.9070403@freescale.com>
The lockup is only the shell. I echo from ttyCPM0 console and it
"locks" then I echo from an ssh session and the kernel messages still
output from the ttyCPM0 console.
NOTE: I found a severe issue that seems to have unlocked ttyCPM2. BUT
ttyCPM1 still hangs. (a while back, we commented out the out_be in
cpm_setbrg - oops (console debug left over))
with address / value in cpm_setbrg
echo test > /dev/ttyCPM1 # * note still hang *
CPM uart[1]:startup - port->irq 00000028
CPM uart[1]:startup - port->irq 40
cpm_setbrg:107 - brg:0 baud:9600
cpm_setbrg:108 - addr:e00119f0 value:00010140
echo test > /dev/ttyCPM2 * note doesn't hang *
CPM uart[2]:startup - port->irq 0000002b
CPM uart[2]:startup - port->irq 43
cpm_setbrg:107 - brg:3 baud:9600
cpm_setbrg:108 - addr:e00119fc value:00010140
On 10/16/07, Scott Wood <scottwood@freescale.com> wrote:
> Alan Bennett wrote:
> > I also verified that when I attempt to echo to the ports that I reach
> > the appropriate driver
> > i.e.
> > echo "hello" > /dev/ttyCPM1
> > CPM uart[1]:startup - port->irq 40
> > echo "hello" > /dev/ttyCPM2
> > CPM uart[2]:startup - port->irq 43
> > but brg's stay 0x0 and my shell's lock up something fierce.
>
> Hmm... try putting a debugging printk in cpm_setbrg with the address
> and value it's writing.
>
> Is it just the shell that locks up, or the console (i.e. can you still
> get kernel messages)?
>
> > (note: my tree is still based off of one you provided a few weeks
> > back. have the 82xx / ep8248e changes we went through been pushed
> > into linus' git tree?)
>
> It should all be in Linus's tree except the actual ep8248e file, which
> didn't make it this time around due to interdependencies on netdev.
> Note that there are some small device tree changes from the tree you're
> currently using (in particular, muram is now in a node of its own).
>
> -Scott
>
prev parent reply other threads:[~2007-10-16 21:38 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
[not found] ` <bfa0697f0710161114y6273af8fre045328b638a9de7@mail.gmail.com>
[not found] ` <47152065.9070403@freescale.com>
2007-10-16 21:38 ` Alan Bennett [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=bfa0697f0710161438y5472ced7y92ca981503a45e93@mail.gmail.com \
--to=embedded@akb.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/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).