From: Woody Wu <narkewoody@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 8250 UART doesn't work
Date: Fri, 7 Dec 2012 03:23:18 +0000 (UTC) [thread overview]
Message-ID: <slrnkc2o7b.2ck.narkewoody@zuhnb712.local.com> (raw)
In-Reply-To: <50C0E737.2000201@zytor.com>
On 2012-12-06, H. Peter Anvin <hpa@zytor.com> wrote:
> On 12/05/2012 11:56 PM, Woody Wu wrote:
>> Hi, list
>>
>> Does anyone here familiar to the serial 8250 driver?
>>
>> I enabled two uart ports in my board definition, but the ports doesn't
>> appear after I loaded the kernel (3.4.19). I discovered, it failed at
>> the UART port auto configuration stage, the exact function is
>> autoconfig(...) in drivers/tty/serial/8250.c.
>>
>
> Sounds like you're using some kind of buggy UART IP... sharing which one
> might help people identify the problem, if they have seen it before.
>
> -hpa
>
The UART controller is EXAR ST16C554D. It claims as a 16550
compatible controller. Each ST16C554D module contains 4 UART, each of
them can be selected via two chip select pad. I think the board
hardware, via a CPLD, make the chip selection transparent to the CPU, so
by a 5-bit address, CPU can addressing individual 8 16550 compatible
registers of each UART.
I am not one hundred percent sure I understood right, but this is all I
can say. You experts can also judge whether this kind of hardware setup
is normal in embedded multi-serial ports solutions.
Many thanks!
--
woody
I can't go back to yesterday - because I was a different person then.
next prev parent reply other threads:[~2012-12-07 3:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 7:56 Woody Wu
2012-12-06 18:43 ` H. Peter Anvin
2012-12-07 3:23 ` Woody Wu [this message]
2012-12-07 10:04 ` Alan Cox
2012-12-08 17:01 ` Woody Wu
2012-12-08 22:52 ` Alan Cox
2012-12-09 6:21 ` Woody Wu
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=slrnkc2o7b.2ck.narkewoody@zuhnb712.local.com \
--to=narkewoody@gmail.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome