All of lore.kernel.org
 help / color / mirror / Atom feed
From: paulo@nlink.com.br (Paulo Fragoso)
To: linux-arm-kernel@lists.infradead.org
Subject: External serial 8250/16550
Date: Tue, 24 May 2011 01:31:05 -0300	[thread overview]
Message-ID: <4DDB3489.2020809@nlink.com.br> (raw)
In-Reply-To: <4DD579EB.50609@nlink.com.br>

On 19-05-2011 17:13, Paulo Fragoso wrote:
>
> This explain constant output on COMA from TL16C2550 and COMB is 
> detected at boot time but doesn't work.
>
> I will research what can be happening but what can be wrong with NCS1 
> and NCS2?

All is working at boot time and NCS1 was correctly programed in bootstrap.

But no data out at serial line I'm testing enabling getty in inittab.

NCS1, NCS2, IOW and IOR are working how expected by the SMC config:

static struct sam9_smc_config tms_uart_smc_config = {
     .ncs_read_setup   = 0,
     .nrd_setup        = 2,
     .ncs_write_setup  = 0,
     .nwe_setup        = 2,

     .ncs_read_pulse   = 5,
     .nrd_pulse        = 4,
     .ncs_write_pulse  = 4,
     .nwe_pulse        = 3,

     .read_cycle       = 10,
     .write_cycle      = 9,

     .mode             = AT91_SMC_READMODE | AT91_SMC_WRITEMODE | 
AT91_SMC_EXNWMODE_DISABLE | AT91_SMC_DBW_8 | AT91_SMC_BAT_WRITE,
     .tdf_cycles       = 3,
};

Why isn't there any data on TX for COMA or COMB?

Paulo.

  reply	other threads:[~2011-05-24  4:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-24 15:57 External serial 8250/16550 Paulo Fragoso
2011-04-26 16:39 ` Andrew Victor
2011-05-06 12:57   ` Paulo Fragoso
2011-05-10  3:24     ` Paulo Fragoso
2011-05-12  2:23       ` Paulo Fragoso
2011-05-19 20:13         ` Paulo Fragoso
2011-05-24  4:31           ` Paulo Fragoso [this message]
2011-05-24 13:46             ` Christian Gagneraud

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=4DDB3489.2020809@nlink.com.br \
    --to=paulo@nlink.com.br \
    --cc=linux-arm-kernel@lists.infradead.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.