From: Haojian Zhuang <haojian.zhuang@gmail.com>
To: Stanislav Brabec <utx@penguin.cz>
Cc: Pavel Machek <pavel@ucw.cz>,
dsaxena@laptop.org, alan@linux.intel.com, gregkh@suse.de,
Daniel Mack <daniel@caiaq.de>,
linux-arm-kernel@lists.infradead.org,
Eric <eric.y.miao@gmail.com>,
Haojian Zhuang <haojian.zhuang@marvell.com>,
rpurdie@rpsys.net, lenz@cs.wisc.edu,
kernel list <linux-kernel@vger.kernel.org>,
Dirk@opfer-online.de, arminlitzel@web.de,
Cyril Hrubis <metan@ucw.cz>,
thommycheck@gmail.com, dbaryshkov@gmail.com, omegamoon@gmail.com,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Possible suspend/resume regression in .32-rc?
Date: Thu, 5 Nov 2009 00:06:13 -0500 [thread overview]
Message-ID: <771cded00911042106u39fd3655mae50a89bd419411b@mail.gmail.com> (raw)
In-Reply-To: <1257241821.4269.5.camel@utx.utx.cz>
On Tue, Nov 3, 2009 at 4:50 AM, Stanislav Brabec <utx@penguin.cz> wrote:
> Haojian Zhuang wrote:
>> On Mon, Nov 2, 2009 at 5:57 AM, Stanislav Brabec <utx@penguin.cz> wrote:
>> > Haojian Zhuang wrote:
>> >
>> >> Commit b5b82df6, from May 2007, breaks no_console_suspend on the OLPC
>> >> XO laptop. Basically what happens is that upon returning from resume,
>> >> serial8250_resume_port() will reconfigure the port for high speed
>> >> mode and all console output will be garbled, making debug of the
>> >> resume path painful. This patch modifies uart_resume_port() to
>> >> reset the port to the state it was in before we suspended.
>> >
>> > See my patch waiting for approval in LKML thread
>> > "serial-core: resume serial hardware with no_console_suspend".
>> >
>> > It attempts to fix it, but I was not yet able to test it due to spitz
>> > resume breakage.
>> >
>>
>> Hi Stanislav,
>>
>> At first, your patch can't be applied into my latest codebase. I have
>> to update the patch. But the console resume is still blocked after
>> applied your patch. It works only after I merge some old code back. My
>> modified patch is in below.
>
> Yes, code changed there a bit. I sent rebased patch later in the thread.
> Did you try this one? (Well I did not test it yet - in time of sending
> resume did not work at all on my Zaurus.)
>
> Your patch is a bit different. I'll test both as soon as possible.
>
>
Your latest patch works well in my platform. Thanks a lot.
next prev parent reply other threads:[~2009-11-05 5:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091031013427.GL14091@buzzloop.caiaq.de>
[not found] ` <20091101205449.GT14091@buzzloop.caiaq.de>
2009-11-01 21:33 ` Pavel Machek
2009-11-01 22:03 ` Pavel Machek
2009-11-02 9:22 ` Haojian Zhuang
2009-11-02 9:29 ` Daniel Mack
2009-11-02 9:38 ` Pavel Machek
2009-11-02 9:54 ` Eric Miao
2009-11-02 10:48 ` Haojian Zhuang
2009-11-02 10:51 ` Pavel Machek
2009-11-02 11:18 ` Haojian Zhuang
2009-11-02 11:27 ` Daniel Mack
2009-11-02 12:22 ` Pavel Machek
2009-11-02 9:57 ` Stanislav Brabec
2009-11-03 3:31 ` Haojian Zhuang
2009-11-03 9:50 ` Stanislav Brabec
2009-11-05 5:06 ` Haojian Zhuang [this message]
2010-01-13 11:46 ` Daniel Mack
2010-01-13 13:42 ` Stanislav Brabec
2010-01-13 15:33 ` Greg KH
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=771cded00911042106u39fd3655mae50a89bd419411b@mail.gmail.com \
--to=haojian.zhuang@gmail.com \
--cc=Dirk@opfer-online.de \
--cc=alan@linux.intel.com \
--cc=arminlitzel@web.de \
--cc=daniel@caiaq.de \
--cc=dbaryshkov@gmail.com \
--cc=dsaxena@laptop.org \
--cc=eric.y.miao@gmail.com \
--cc=gregkh@suse.de \
--cc=haojian.zhuang@marvell.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metan@ucw.cz \
--cc=omegamoon@gmail.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.com \
--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®