From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
amax@us.ibm.com, ralf@linux-mips.org, starvik@axis.com
Subject: Re: [FINAL WARNING] Removal of deprecated serial functions - please update your drivers NOW
Date: Wed, 31 Aug 2005 14:38:10 +0100 [thread overview]
Message-ID: <1125495490.3355.27.camel@localhost.localdomain> (raw)
In-Reply-To: <20050831135258.D1118@flint.arm.linux.org.uk>
On Mer, 2005-08-31 at 13:52 +0100, Russell King wrote:
> The key thing is that port.dev should be set appropriately and the
> relevant calls to serial8250_suspend_port/serial8250_resume_port
> be made (or port.dev should be NULL if no power management is
> expected - in which case it may be managed as a generic platform
> port.)
Thanks. Thats all I needed to know to whack that into shape once I've
put a legacy 32bit build environment back together for this and for
something akpm wants me to fix in another diff.
Power management is umm special. The port will die on suspend/resume via
Linux (via APM seems to be ok) and need a userspace firmware reload to
come back.
next prev parent reply other threads:[~2005-08-31 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 9:33 [FINAL WARNING] Removal of deprecated serial functions - please update your drivers NOW Russell King
2005-08-31 13:00 ` Alan Cox
2005-08-31 12:52 ` Russell King
2005-08-31 13:38 ` Alan Cox [this message]
2005-08-31 15:49 ` Alan Cox
2005-09-01 23:12 ` [2.6 patch] drivers/serial/crisv10.c: remove {,un}register_serial dummies Adrian Bunk
2005-09-02 15:58 ` Russell King
2005-09-07 19:12 ` [FINAL WARNING] Removal of deprecated serial functions - please update your drivers NOW Max Asbock
2005-09-07 19:25 ` Russell King
2005-09-07 20:13 ` Max Asbock
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=1125495490.3355.27.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=amax@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=starvik@axis.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