linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ladislav Klenovic <poseidon21@post.sk>
To: <linuxppc-embedded@ozlabs.org>
Subject: Re: Re: SMC as UART problem on mpc8xx
Date: 02 Feb 2007 11:51:01 +0100 (CET)	[thread overview]
Message-ID: <45C31795.000001.05998@kamasutra> (raw)

> On 01 Feb 2007 17:10:31 +0100 (CET)
> a b  wrote:
> 
> > Hi,
> > I have mpc8xx where I would like the following configuration:
> >  - SCC1 as system console (works fine) 
> >  - SMC1-2 as UART (doesn\\\'t work)
> > 
> > I use linux 2.6.16.20 with backward patch from linux-2.6.19.2 for SMCs. My only problem is 
> > that even I can see cpm_uart registered for IRQ 20 (for SMC1) I never get interrupt even
> > I do e.g. \\\"echo 123 > /dev/ttyCPM\\\". 
> > 
> > here is a short extract from /proc/interrupts:
> >  20:          0   CPM       Edge      cpm_uart  <--SMC1
> >  21:       7546   CPM       Edge      SPI
> >  46:         20   CPM       Edge      cpm_uart  <-- SCC1 (console)
> > 
> > here is a short extract from /proc/tty/driver/ttyCPM:
> > serinfo:1.0 driver revision:
> > 0: uart:CPM UART mmio:0xFFF00A80 irq:20 tx:14 rx:0 RTS|CTS|DTR|DSR|CD
> > 1: uart:CPM UART mmio:0xFFF00A90 irq:19 tx:0 rx:0 CTS|DSR|CD
> > 2: uart:CPM UART mmio:0xFFF00A00 irq:46 tx:3038 rx:46 RTS|CTS|DTR|DSR|CD
> > 
> > Can anybody help me to get SMCs working?
> > 
> > 
> Check IO ports? IIRC, in 8xx some SoC devices could not work simultaneously because they 
> share some GPIO pins. In any case, if something does not function with CPM UART, IOports stuff is the first thing to check.
> 
> -- 
> Sincerely, 
> Vitaly
> 

Hi,
thnx for hint, you were right, problem was in I/O port configuration. 
I am a bit wondered why is B port for mpc8xx not configured in 2.16.19.2. Or is it  
configured somewhere else? I especially miss this part of code in cpm_uart_cpm1.c:

void smc1_lineif(struct uart_cpm_port *pinfo){
...
#elif defined (CONFIG_MPC86XADS)
       if (!pinfo->is_portb) {
                cp->cp_pbpar |= iobits;
                cp->cp_pbdir &= ~iobits;
                cp->cp_pbodr &= ~iobits;
        } else {
                ((immap_t *)IMAP_ADDR)->im_ioport.iop_papar |= iobits;
                ((immap_t *)IMAP_ADDR)->im_ioport.iop_padir &= ~iobits;
                ((immap_t *)IMAP_ADDR)->im_ioport.iop_paodr &= ~iobits;
        }
#endif
...
}

Regards,
Ladislav.



__________
Mobilné telefóny v slovenskej premiére a najaktuálnejšie informácie - http://mobil.sme.sk/

             reply	other threads:[~2007-02-02 11:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02 10:51 Ladislav Klenovic [this message]
2007-02-02 14:54 ` SMC as UART problem on mpc8xx Vitaly Bordug

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=45C31795.000001.05998@kamasutra \
    --to=poseidon21@post.sk \
    --cc=linuxppc-embedded@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 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).