From: Ken MacLeod <ken@bitsko.slc.ut.us>
To: linuxppc-embedded@ozlabs.org
Subject: cpm_uart initializes scm/scc for console only?
Date: 03 Jun 2005 22:14:19 -0500 [thread overview]
Message-ID: <871x7i3jas.fsf@bitsko.slc.ut.us> (raw)
We're tracking down an issue trying to use both SMC1 and SMC2 as
ttyCPM devices. SMC1 as console (and ttyCPM/0) is working fine,
but it appears that SMC2 is not being completely initialized.
It looks as though the cause is that cpm_uart_init_smc (or
cpm_uart_init_scc) is only called from cpm_uart_console_setup[1],
ie. only when CONFIG_SERIAL_CPM_CONSOLE is set, and then only for the
one port that is defined as the console.
It looks like cpu_uart_init_smc/scc should be called at some point for
all ports that are defined for use, but there's no other place it's
called from.
Before we try fixing the wrong thing, is this (using multiple SMC/SCC
ports "out of the box") known to work? Is there a reason why calling
cpu_uart_init_smc/scc wouldn't have been implemented?
This was found with Linux 2.6.10 and I've reviewed the updates through
2.6.12-rc5 and the patch tracking system.
Sanity check much appreciated,
-- Ken
[1] http://lxr.linux.no/source/drivers/serial/cpm_uart/cpm_uart_core.c#L1079
reply other threads:[~2005-06-04 3:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=871x7i3jas.fsf@bitsko.slc.ut.us \
--to=ken@bitsko.slc.ut.us \
--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).