From: Scott Wood <scottwood@freescale.com>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Help with device tree binding for SMC serial
Date: Wed, 09 Jan 2008 16:29:53 -0600 [thread overview]
Message-ID: <47854AE1.7080802@freescale.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B03D58BC9@ismail.innsys.innovsys.com>
Rune Torgersen wrote:
> Ok we're now using
> serial@11a80 {
> device_type = "serial";
> compatible = "fsl,mpc8280-smc-uart",
> "fsl,cpm2-smc-uart";
> reg = <11a80 10 0 40>; // <base_address length
> parameter_ram_address length>
> interrupts = <4 8>; // Interrupt from table 4.3
> of mpc8280rm, interrupt is level or edge
> interrupt-parent = <&PIC>;
> fsl,cpm-brg = <7>;
> fsl,cpm-command = <1d000000>; // Page and Sub-block code
> of the CPCR
> };
Looks good.
> Right now we're trying to just get a kernel to give us some serial
> output, so we can continue the porting job.
> We're unsig a cuImage (using the pq2fads code right now).
>
> Now our problem is that the serial port is spitting out 0x0a's as fast
> as it can.
Don't forget to exclude the SMC parameter RAM from the muram data area
in /soc/cpm/muram/data/reg. If you have an older device tree binding
that has no /soc/cpm/muram node, but instead has two resources in
/soc/cpm/reg, you need to move to head-of-tree to get this to work.
-Scott
next prev parent reply other threads:[~2008-01-09 22:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 19:18 Help with device tree binding for SMC serial Rune Torgersen
2008-01-09 19:45 ` Scott Wood
2008-01-09 22:22 ` Rune Torgersen
2008-01-09 22:29 ` Scott Wood [this message]
2008-01-09 22:37 ` Rune Torgersen
2008-01-09 22:40 ` Scott Wood
2008-01-09 23:07 ` Rune Torgersen
2008-01-10 17:53 ` Scott Wood
2008-01-10 19:10 ` Rune Torgersen
2008-01-10 19:19 ` Scott Wood
2008-01-11 0:07 ` Rune Torgersen
2008-01-11 14:13 ` Rune Torgersen
2008-01-11 17:24 ` Scott Wood
2008-01-11 18:11 ` Rune Torgersen
2008-01-11 18:15 ` Scott Wood
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=47854AE1.7080802@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=runet@innovsys.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).