From: Russell King <rmk@arm.linux.org.uk>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: sshtylyov@ru.mvista.com, linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: [PATCH] serial_txx9: forcibly init the spinlock for PCI UART used as a console
Date: Tue, 27 Dec 2005 18:41:52 +0000 [thread overview]
Message-ID: <20051227184152.GA4474@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20051228.003457.74752441.anemo@mba.ocn.ne.jp>
On Wed, Dec 28, 2005 at 12:34:57AM +0900, Atsushi Nemoto wrote:
> Thanks for your comment.
>
> >>>>> On Tue, 27 Dec 2005 16:38:54 +0300, Sergei Shtylylov <sshtylyov@ru.mvista.com> said:
>
> >> The problem is not just only spin_lock_init. The parameters of
> >> "console=" option (baudrate, etc.) are not passed for PCI UART.
>
> sshtylyov> They are -- uart_add_one_port() calls console setup
> sshtylyov> once more when registering PCI UART with serial code.
>
> Yes, you are right. I missed the register_console call in
> uart_add_one_port(). So your patch will fix the problem. But I
> suppose the spinlock should be initialized in serial_core. How about
> this?
I think you're layering work-around on top of work-around on top of
work-around here.
I think the first thing you need to resolve is the way you're
registering your ports. Firstly, if you're solely PCI-based, there's
no need to pre-register all the uart ports at driver initialisation
time. Consequently, there's no need to remove them all when you
remove the module.
Secondly, the upshot of this is that you only call uart_add_one_port()
when you initialise a PCI card.
This should result in a cleaner implementation, and the console will
not be started until you detect the PCI card. Which is the behaviour
you desire in any case.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-12-27 18:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-26 22:24 [PATCH] serial_txx9: forcibly init the spinlock for PCI UART used as a console Sergei Shtylylov
2005-12-27 5:45 ` Atsushi Nemoto
2005-12-27 13:38 ` Sergei Shtylylov
2005-12-27 15:34 ` Atsushi Nemoto
2005-12-27 16:29 ` Sergei Shtylylov
2005-12-27 18:41 ` Russell King [this message]
2005-12-27 18:54 ` Sergei Shtylylov
2005-12-27 19:31 ` Sergei Shtylyov
2005-12-28 4:25 ` Atsushi Nemoto
2005-12-29 16:32 ` Atsushi Nemoto
2006-01-05 15:14 ` Atsushi Nemoto
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=20051227184152.GA4474@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=sshtylyov@ru.mvista.com \
/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