From: paulo@nlink.com.br (Paulo Fragoso)
To: linux-arm-kernel@lists.infradead.org
Subject: External serial 8250/16550
Date: Thu, 19 May 2011 17:13:31 -0300 [thread overview]
Message-ID: <4DD579EB.50609@nlink.com.br> (raw)
In-Reply-To: <4DCB449C.8060808@nlink.com.br>
Em 11/05/2011 23:23, Paulo Fragoso escreveu:
> On 10-05-2011 00:24, Paulo Fragoso wrote:
> I have one doubt about new-style UART initialization, how can I
> initialize a board using AT91sam9 with two internal USART and two
> external 8250 UART at same time?
>
> For example:
>
> /* DGBU on ttyS0. (Rx & Tx only) */
> at91_register_uart(0, 0, 0);
>
> /* USART0 on ttyS1. (Rx, Tx, RTS, CTS) */
> at91_register_uart(AT91SAM9G45_ID_US0, 1, ATMEL_UART_CTS | ATMEL_UART_RTS);
>
> /* USART1 on ttyS2. (Rx, Tx, RTS, CTS) */
> at91_register_uart(AT91SAM9G45_ID_US1, 2, ATMEL_UART_CTS | ATMEL_UART_RTS);
>
> If I wish to put two more 8250 external serial in sequence (ttyS3 and
> ttyS4) which ID will be used at at91_register_uart function?
>
> Looking at91_register_uart function all structs pdev are defined
> internaly, how I will define serila8250 platform_device and pass at
> at91_register_uart function?
I discovered NCS1 is always on level 0 (selected) and NCS2 is always on
level 1, those lines never change its state after boot, and they were
configured correctly:
sam9_smc_configure(1, &tms_uart_smc_config);
sam9_smc_configure(2, &tms_uart_smc_config);
Entire file is here:
http://users.nlink.com.br/~paulo/TMS/20110519/board-sweda_tms2.c
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?
Thanks,
Paulo.
next prev parent reply other threads:[~2011-05-19 20:13 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 [this message]
2011-05-24 4:31 ` Paulo Fragoso
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=4DD579EB.50609@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.