linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] MPC8360E-RDK: Device tree and board file
Date: Wed, 26 Dec 2007 19:29:44 +0300	[thread overview]
Message-ID: <20071226162943.GB11230@localhost.localdomain> (raw)
In-Reply-To: <47716BBE.5090000@freescale.com>

On Tue, Dec 25, 2007 at 02:44:46PM -0600, Timur Tabi wrote:
> Anton Vorontsov wrote:
> 
> >Yup. I've seen it, thanks. I'm going to test it as well. ;-)
> 
> If they work for you, please let Kumar know.

Unfortunately they don't.

root@mpc8360erdk:~# echo abc > /dev/ttyQE0

And hang. No interrupts.

After ^C:
ucc_uart e0102400.ucc: shutdown timeout

The same for ttyQE1 (just for testing I set it up to not use
Soft-UART).

The same for loopback mode.

I wonder what are the symptoms if microcode is at fault? According
to errata description, hang isn't something I should get on the
transmit attempt.

> >MPC8360E, Rev: 21. Are you aware of any known issues on this chip
> >regarding UCC serials?
> 
> Yep.  You need a microcode upload.  My patches describe everything.

Well. All I've found is: QERAMPTCH.zip ("RAM Microcode Patches for
PowerQUICC II Pro Family QE Errata"), which should fix QE_UART5 errata
for MPC8323 Rev 1.1. Can I assume it works for MPC8360 too? I've tried
it. No luck.

Here are dts entries I use:

		firmware {
			id = "Soft-UART";
			extended_modes = <0 0>;
			virtual_traps = <0 0 0 0 0 0 0 0>;
		};

		ucc@2400 {
			device_type = "serial";
			compatible = "ucc_uart";
			reg = <0x2400 0x200>;
			device-id = <5>;
			port-number = <0>;
			rx-clock-name = "brg7";
			tx-clock-name = "brg8";
			interrupts = <40>;
			interrupt-parent = <&qeic>;
			soft-uart;
		};

		ucc@3400 {
			device_type = "serial";
			compatible = "ucc_uart";
			reg = <0x3400 0x200>;
			device-id = <6>;
			port-number = <1>;
			rx-clock-name = "brg14";
			tx-clock-name = "brg14";
			interrupts = <41>;
			interrupt-parent = <&qeic>;
		};

Any ideas?

Thanks,

-- 
Anton Vorontsov
email: cbou@mail.ru
backup email: ya-cbou@yandex.ru
irc://irc.freenode.net/bd2

  reply	other threads:[~2007-12-26 16:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 20:23 [PATCH] [POWERPC] MPC8360E-RDK: Device tree and board file Anton Vorontsov
2007-12-23  2:16 ` Stephen Rothwell
2007-12-23  3:25 ` Timur Tabi
2007-12-24 12:15   ` Anton Vorontsov
2007-12-25 20:44     ` Timur Tabi
2007-12-26 16:29       ` Anton Vorontsov [this message]
2007-12-26 20:38         ` Anton Vorontsov
2007-12-27 15:38         ` Timur Tabi
2007-12-27 16:00           ` Anton Vorontsov
2007-12-23  3:28 ` Timur Tabi
2007-12-24 12:17   ` Anton Vorontsov
2007-12-24 17:39     ` Timur Tabi

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=20071226162943.GB11230@localhost.localdomain \
    --to=avorontsov@ru.mvista.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@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).