linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Matvejchikov Ilya" <matvejchikov@gmail.com>
To: "Scott Wood" <scottwood@freescale.com>
Cc: Ben Gardiner <BenGardiner@nanometrics.ca>, linuxppc-embedded@ozlabs.org
Subject: Re: No output from SMC1 console with the 2.6.26 kernel (8xx based board)
Date: Wed, 30 Jul 2008 13:37:43 +0400	[thread overview]
Message-ID: <8496f91a0807300237q302cafd3ga21ddb7bbc0bd513@mail.gmail.com> (raw)
In-Reply-To: <20080729193901.GC8051@ld0162-tx32.am.freescale.net>

> Did you use CONFIG_PPC_CPM_NEW_BINDING in 2.6.25?  It became mandatory in
> 2.6.26.  Also, try commenting out cpm_setbrg() calls in case the
> frequency is not being set properly.

Yes, this option was enabled. Nothing changed with empty cpm_setbrg()
function :(

> 2.6.26 introduced the allocation of the CPM2 SMC parameter RAM area; what
> did your device node look like in 2.6.25?  What happens if you use that
> device tree with 2.6.26?

The cpm node for the 2.6.25.4 kernel was the following:

		cpm@119c0 {
			#address-cells = <1>;
			#size-cells = <1>;
			#interrupt-cells = <2>;
			compatible = "fsl,mpc8280-cpm", "fsl,cpm2";
			reg = <119c0 30>;
			ranges;

			muram {
				#address-cells = <1>;
				#size-cells = <1>;
				ranges = <0 0 10000>;

				data-only@0 {
					compatible = "fsl,cpm-muram-data";
					reg = <100 1f00 9800 800>;
				};
			};

			brg@119f0 {
				compatible = "fsl,cpm-brg", "fsl,cpm2-brg";
				reg = <119f0 10 115f0 10>;
			};

			smc1: serial@11a80 {
				device_type = "serial";
				compatible = "fsl,cpm2-smc-uart";
				reg = <11a80 20 0 40>;
				interrupts = <4 8>;
				interrupt-parent = <&PIC>;
				fsl,cpm-brg = <7>;
				fsl,cpm-command = <1d000000>;
			};

		};

(muram node for 2.6.25 is differs from muram node for the 2.6.26)

With this device tree I have a warning message from cpm_uart driver
tells that the dts file needs to be updated.

Ilya.

  reply	other threads:[~2008-07-30  9:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 19:43 No output from SMC1 console with the 2.6.26 kernel (PQ2FADS based board) Matvejchikov Ilya
2008-07-28 19:59 ` Scott Wood
2008-07-29  6:10   ` Matvejchikov Ilya
2008-07-29 15:33     ` No output from SMC1 console with the 2.6.26 kernel (8xx " Ben Gardiner
2008-07-29 18:36       ` Matvejchikov Ilya
2008-07-29 19:39         ` Scott Wood
2008-07-30  9:37           ` Matvejchikov Ilya [this message]
2008-07-30 15:45             ` Scott Wood
2008-08-19 11:13               ` Matvejchikov Ilya
2008-08-19 16:13                 ` Scott Wood
2008-08-21 13:04                   ` Matvejchikov Ilya
2008-07-29 19:36       ` Scott Wood
2008-07-30 13:36         ` Ben Gardiner

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=8496f91a0807300237q302cafd3ga21ddb7bbc0bd513@mail.gmail.com \
    --to=matvejchikov@gmail.com \
    --cc=BenGardiner@nanometrics.ca \
    --cc=linuxppc-embedded@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).