mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Kieran Clancy <clancy.kieran@gmail.com>
Cc: Stefan Biereigel <stefan@biereigel.de>,
	Juan Manuel Cabo <juanmanuel.cabo@gmail.com>,
	Stefan Biereigel <security@biereigel-wb.de>,
	Lan Tianyu <lantianyu1986@gmail.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-kernel@vger kernel org" <linux-kernel@vger.kernel.org>,
	Len Brown <lenb@kernel.org>, San Zamoyski <san@plusnet.pl>,
	"D. Jansen" <dennis.jansen@web.de>,
	"Maurizio D'Addona" <mauritiusdadd@gmail.com>
Subject: Re: [REGRESSION 3.14-rc6] Samsung N150 lid does not "open" after suspend to RAM.
Date: Wed, 26 Mar 2014 16:01:56 +0100	[thread overview]
Message-ID: <4534478.UfDZjzQsar@vostro.rjw.lan> (raw)
In-Reply-To: <CAGf84QJU+RKXV4AyQ7QBTKjpdPm3AYLtWTFio+-r3j8wyoEokA@mail.gmail.com>

On Thursday, March 27, 2014 01:08:58 AM Kieran Clancy wrote:
> On Wed, Mar 26, 2014 at 9:12 PM, Stefan Biereigel <stefan@biereigel.de> wrote:
> >
> > I don't know if it is a valid idea, but maybe it would be ok to process
> > events after resume in general, and only throw away events on those
> > platforms that continue to log events while in standby (Samsung 5/7/9)?
> 
> We can give it a shot!
> 
> It may even be that on Samsung 5/7/9 there is no harm in processing
> the events instead of discarding them.
> 
> Here's a patch that we can try for that:
> 
> http://kieranclancy.com/tmp/2014/03/ec_clear_process.patch

Can you please send patches inline so that it's more convenient to
comment them if need be?

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2014-03-26 14:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24  7:50 Stefan Biereigel
2014-03-24  9:30 ` Lan Tianyu
2014-03-24 11:19   ` Stefan Biereigel
2014-03-25  9:34     ` Lan Tianyu
2014-03-25  9:43       ` Stefan Biereigel
2014-03-25 13:23       ` Kieran Clancy
2014-03-25 13:53         ` Juan Manuel Cabo
2014-03-25 16:07           ` Stefan Biereigel
2014-03-25 16:38         ` Stefan Biereigel
2014-03-25 20:24         ` Stefan Biereigel
2014-03-25 20:41           ` Juan Manuel Cabo
2014-03-25 22:56             ` Juan Manuel Cabo
2014-03-26 10:42               ` Stefan Biereigel
2014-03-26 14:38                 ` Kieran Clancy
2014-03-26 15:01                   ` Rafael J. Wysocki [this message]
2014-03-26 19:56                   ` Stefan Biereigel
2014-03-26 22:36                     ` Kieran Clancy
2014-03-26 22:41                       ` Stefan Biereigel
     [not found]                   ` <CAM6oVw2v9ptr0c08uPiB_3z3e41VO+Vp3OhoHXiBxagAOfPBZA@mail.gmail.com>
2014-04-01  9:53                     ` Kieran Clancy
2014-04-01 11:36                       ` Nicolas Porcel
2014-04-01 11:58                         ` Kieran Clancy
2014-04-01 12:18                           ` Nicolas Porcel
2014-04-01 18:02                             ` Nicolas Porcel

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=4534478.UfDZjzQsar@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=clancy.kieran@gmail.com \
    --cc=dennis.jansen@web.de \
    --cc=juanmanuel.cabo@gmail.com \
    --cc=lantianyu1986@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mauritiusdadd@gmail.com \
    --cc=san@plusnet.pl \
    --cc=security@biereigel-wb.de \
    --cc=stefan@biereigel.de \
    /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®