From: Chuck Meade <chuck@ThePTRGroup.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: UCC UART
Date: Tue, 22 Jun 2010 17:27:54 -0400 [thread overview]
Message-ID: <4C212ADA.3070409@ThePTRGroup.com> (raw)
In-Reply-To: <4C2128E6.7010201@mlbassoc.com>
>> Also in the current Linux kernel, there is a dependence on the
>> correctness
>> of the "brg-frequency" property from the dts. Look up above
>> qe_setbrg() at
>> the qe_get_brg_clk() function. Before the return (there are multiple
>> return
>> points) printk the brg_clk being returned. That must be correct for your
>> hardware -- must be the actual brg freq. I assume that you are
>> booting from
>> U-Boot. I believe in modern implementations that U-Boot fills in the
>> brg-frequency in the device tree at boot time.
>
> The driver claims to work with either bus-frequency or brg-frequency set.
> I only had bus-frequency; when I set brg-frequency, it has started to work.
> Now to test it with a scope to see what else is wrong...
>
> BTW, I use RedBoot - being the original author, how could I not?
>
> Thanks for the help
No problem -- I am glad it is working for you now.
Chuck Meade
chuck@ThePTRGroup.com
next prev parent reply other threads:[~2010-06-22 21:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 14:55 UCC UART Gary Thomas
2010-06-22 15:06 ` Tabi Timur-B04825
2010-06-22 15:10 ` Chuck Meade
2010-06-22 15:14 ` Gary Thomas
2010-06-22 15:28 ` Chuck Meade
2010-06-22 15:46 ` Gary Thomas
2010-06-22 15:53 ` Chuck Meade
2010-06-22 17:44 ` Gary Thomas
2010-06-22 18:14 ` Chuck Meade
2010-06-22 18:41 ` Gary Thomas
2010-06-22 19:01 ` Chuck Meade
2010-06-22 21:19 ` Gary Thomas
2010-06-22 21:27 ` Chuck Meade [this message]
[not found] ` <4C20D162.2020302@freescale.com>
2010-06-24 21:20 ` Timur Tabi
2010-06-25 0:49 ` Gary Thomas
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=4C212ADA.3070409@ThePTRGroup.com \
--to=chuck@theptrgroup.com \
--cc=linuxppc-dev@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.