From: Andrew Morton <akpm@linux-foundation.org>
To: Stanislav Brabec <utx@penguin.cz>
Cc: linux@arm.linux.org.uk, linux-kernel@vger.kernel.org,
gregkh@suse.de, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] serial-core: resume serial hardware with no_console_suspend
Date: Wed, 30 Sep 2009 14:12:55 -0700 [thread overview]
Message-ID: <20090930141255.49b6caa0.akpm@linux-foundation.org> (raw)
In-Reply-To: <1253872547.13257.18.camel@hammer.suse.cz>
On Fri, 25 Sep 2009 11:55:47 +0200
Stanislav Brabec <utx@penguin.cz> wrote:
> Russell King - ARM Linux wrote:
> > 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.
>
> Yes, but no_console_suspend itself is a bit hacky. You need to save
> console state but keep it running as long as possible afterwards and
> resume it after return from the sleep.
>
> I was not sure, what exactly should be skipped and what must be run, so
> I experimented a bit.
>
> Not calling hardware suspend/resume (current implementation) breaks
> serial port in hardware that need resume.
>
> Calling of resume without suspend seems to be dangerous. Not calling
> suspend at all and standard initialization on resume would probably
> reset the port setting and maybe cause memory leak.
>
> > > 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?
>
> The hardware resumes correctly. But no_console_suspend breaks its
> resume.
>
> > 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.
>
> Exactly, my ARM hardware is PXA270 on Zaurus SL-C3200.
hm, ho hum.
Could you please redo/retest/resend the patch against the current
kernel? Someone went and renamed everything and it doesn't apply at
all any more.
next prev parent reply other threads:[~2009-09-30 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 13:38 [PATCH] serial-core: resume serial hardware with no_console_suspend Stanislav Brabec
2009-09-25 0:05 ` Andrew Morton
2009-09-25 7:36 ` Russell King - ARM Linux
2009-09-25 9:55 ` Stanislav Brabec
2009-09-30 21:12 ` Andrew Morton [this message]
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=20090930141255.49b6caa0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--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