public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale•com>
To: Laurent Pinchart <laurentp@cse-semaphore•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: Trouble with SCC UART ports when moving from ppc to powerpc
Date: Mon, 17 Mar 2008 10:33:26 -0500	[thread overview]
Message-ID: <20080317153326.GA2644@loki.buserror.net> (raw)
In-Reply-To: <200803101317.04455.laurentp@cse-semaphore.com>

On Mon, Mar 10, 2008 at 01:17:01PM +0100, Laurent Pinchart wrote:
> On Friday 07 March 2008 17:21, Scott Wood wrote:
> > cpm2_reset() doesn't currently actually reset the CPM, for some reason
> > (unlike cpm1).  This should probably be fixed, though then we'd have to
> > deal with assigning SMC parameter RAM addresses ourselves.
> 
> I had overlooked that. Resetting the CPM in cpm2_reset() helps. Is there any 
> reason not to rset the CPM in cpm2_reset() ?

The only issue I'm aware of other than the SMC parameter RAM relocation is
that the reset can't happen if the early udbg printk is being used.

> How should SMC parameter RAM assignment be handled ? I'm not very familiar 
> with the CPM1, 

CPM1 has hardcoded SMC parameter RAM addresses, so it's not relevant here.

> but for CPM2 the cpm_uart driver could easily cpm_dpalloc() parameter RAM.

It can, yes.  Patches welcome. :-)

-Scott

  reply	other threads:[~2008-03-17 15:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07 14:20 Trouble with SCC UART ports when moving from ppc to powerpc Laurent Pinchart
2008-03-07 15:00 ` Timur Tabi
2008-03-07 16:21 ` Scott Wood
2008-03-10 12:17   ` Laurent Pinchart
2008-03-17 15:33     ` Scott Wood [this message]
2008-03-20 13:39       ` Laurent Pinchart
2008-03-20 15:08         ` Scott Wood
2008-03-20 15:18           ` Laurent Pinchart
2008-03-20 16:24             ` 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=20080317153326.GA2644@loki.buserror.net \
    --to=scottwood@freescale$(echo .)com \
    --cc=laurentp@cse-semaphore$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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