From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Linus Torvalds <torvalds@osdl.org>, Dave Jones <davej@redhat.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Jesse Brandeburg <jesse.brandeburg@gmail.com>,
Andrew Morton <akpm@osdl.org>,
stern@rowland.harvard.edu, linux-kernel@vger.kernel.org,
cpufreq@www.linux.org.uk
Subject: Re: Linux v2.6.18-rc3
Date: Wed, 2 Aug 2006 23:05:33 +0100 [thread overview]
Message-ID: <20060802220533.GB19669@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20060802213834.GB17599@flint.arm.linux.org.uk>
On Wed, Aug 02, 2006 at 10:38:34PM +0100, Russell King wrote:
> On Wed, Aug 02, 2006 at 02:18:55PM -0700, Linus Torvalds wrote:
> > The serial layer should use set_termios() when users set the termios state
> > (surprise surprise), not to emulate suspend/restore.
>
> Yes Linus, you're obviously right. Would you mind re-engineering this
> while I'm away for the next few days. For _ALL_ serial drivers, not
> just 8250. Thanks.
BTW, you'll need to replicate some of the quirk behaviour on some 8250
compatible UARTs when restoring registers - you can't blindly write
the registers in any one particular order.
Some UARTs have side effects which reset some features if you do that
(eg, TI16750 UARTs with 64 byte FIFOs need a different register writing
order from everything else, otherwise it turns off the 64-byte FIFOs.)
Others require you to write a sequence of values to a register, etc.
Okay, consider me gone from this point forwards for the next few days.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
prev parent reply other threads:[~2006-08-02 22:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0607292320490.4168@g5.osdl.org>
[not found] ` <4807377b0607302113i4e984ff6j1ebae5562148907c@mail.gmail.com>
2006-07-31 4:27 ` Linux v2.6.18-rc3 Andrew Morton
2006-07-31 14:54 ` Alan Stern
2006-07-31 15:11 ` Andrew Morton
2006-07-31 15:59 ` Alan Stern
2006-07-31 20:34 ` Alan Stern
2006-08-02 4:31 ` Jesse Brandeburg
2006-08-02 4:59 ` Andrew Morton
2006-08-02 19:57 ` Jesse Brandeburg
2006-08-02 20:16 ` Rafael J. Wysocki
2006-08-02 20:23 ` Russell King
2006-08-02 20:26 ` Rafael J. Wysocki
2006-08-02 20:32 ` Dave Jones
2006-08-02 20:58 ` Russell King
2006-08-02 21:01 ` Dave Jones
2006-08-02 21:18 ` Linus Torvalds
2006-08-02 21:38 ` Russell King
2006-08-02 22:04 ` Linus Torvalds
2006-08-02 22:05 ` Russell King [this message]
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=20060802220533.GB19669@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.com \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@osdl.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