From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stanislav Brabec <utx@penguin.cz>,
linux-kernel@vger.kernel.org, gregkh@suse.de,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] serial-core: resume serial hardware with no_console_suspend
Date: Fri, 25 Sep 2009 08:36:17 +0100 [thread overview]
Message-ID: <20090925073617.GA5856@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20090924170503.37cbe4ed.akpm@linux-foundation.org>
On Thu, Sep 24, 2009 at 05:05:03PM -0700, Andrew Morton wrote:
> On Tue, 15 Sep 2009 15:38:58 +0200
> Stanislav Brabec <utx@penguin.cz> wrote:
>
> > Hardware may need re-initialization to get serial port working after
> > resume. It does not happen with no_console_suspend. Attached patch
> > attempts to fix it.
> >
> > The patch attempts to keep hardware running before suspend and run
> > hardware re-initialization after resume. Maybe simpler approach is
> > possible.
>
> The patch doesn't apply any more and seems like a rather hacky thing to do.
>
> It appears that you have specific serial hardware which doesn't resume
> correctly? If so, that's a bug, so how about we start with a bug
> report/description?
It's something that I did point out when the no_console_suspend patch
appeared, but I was overruled/ignored.
The problem is that on ARM hardware, there is no BIOS to re-initialize
hardware. The kernel has to do restore the entire system hardware
state upon resume. Unfortunately, no_console_suspend not only prevents
the console from being suspended but _also_ resumed.
The result of that is the console UART is left in a totally uninitialized
state.
next prev parent reply other threads:[~2009-09-25 7:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 13:38 Stanislav Brabec
2009-09-25 0:05 ` Andrew Morton
2009-09-25 7:36 ` Russell King - ARM Linux [this message]
2009-09-25 9:55 ` Stanislav Brabec
2009-09-30 21:12 ` Andrew Morton
2009-10-05 23:27 ` Andrew Morton
2009-10-18 15:05 ` Stanislav Brabec
2009-10-18 15:46 ` Stanislav Brabec
2009-10-18 15:49 ` Stanislav Brabec
2009-10-18 19:19 ` Pavel Machek
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=20090925073617.GA5856@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=utx@penguin.cz \
/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
all inboxes | Powered by JetHome®