All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Jérôme de Bretagne" <jerome.debretagne@gmail.com>,
	Mario.Limonciello@dell.com
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Darren Hart <dvhart@infradead.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH 0/3] ACPI / sleep: Support power button wakeup from S2I on recent Dell laptops
Date: Mon, 12 Jun 2017 08:54:12 -0700	[thread overview]
Message-ID: <1497282852.195383.56.camel@linux.intel.com> (raw)
In-Reply-To: <CA+kEDGHev9XYQr=BEVZ8od+nX_cQ637eY0cF81_v3auQZvBKRQ@mail.gmail.com>

On Mon, 2017-06-12 at 00:01 +0200, Jérôme de Bretagne wrote:
> Hi Mario, Hi Rafael,
> 
> > 
> > > 
> > > Some assumptions now: either the SCI is ignored erroneously or
> > > it's
> > > not interpreted correctly by the expected driver? I guess that's
> > > the 2
> > > possibilities I'll try to investigate.
> > 
> > Well that's too bad.  Yes, you're correct that the EC has changed
> > between
> > those versions.  Are you testing on or off AC adapter?
> 
> I haven't detected a pattern specific to the state of the AC adapter.
> 
> Good news on another front. By adding some more logs in the
> s2idle-dell-test branch, I've been able to check and confirm that
> notify_handler() from intel-hid.c is actually called upon short power
> key
> press during s2idle on my Latitude 7275.
> 
> However, the system with BIOS 1.1.31 doesn't match (anymore?) the
> current criteria to call pm_wakeup_hard_event introduced in commit:
> 
> platform: x86: intel-hid: Wake up the system from suspend-to-idle
> 7871dc61497a71be93c4f80d43ac109152510e7e
> 
> This ugly 3-line modification I've added on the actual patch here:
> 
> + if (priv->wakeup_mode) {
> +
> + /* Wake up Dell Latitude 7275 BIOS 1.1.31. */
> + if (event == 0xce)
> + pm_wakeup_hard_event(&device->dev);
0xce is a 5 button array press and 0xcf is release.

> +
> + /* Wake up on 5-button array events only. */
> + if (event == 0xc0 || !priv->array)
> + return;
I don't think 0xc0 is any valid 5 button code.

> +
> + if (sparse_keymap_entry_from_scancode(priv->array, event))
> + pm_wakeup_hard_event(&device->dev);
> + else
> + dev_info(&device->dev, "unknown event 0x%x\n", event);
> +
> + return;
> + }
> 
> make the system wake up on a standard short press finally!
> 
> Is the "Wake up on 5-button array events only." assumption broad
> enough to cover the various Intel systems that need this behavior?
For the platforms which supported Win 8.1 only the event should be
handled by vbtn driver.

Thanks,
Srinivas

> 
> Or am I just detecting another ACPI issue in fact that prevents this
> system from setting up properly the 5 button array with BIOS 1.1.31?
> How would you recommend me to test that 2nd assumption?
> 
> Thanks,
> Jérome
> 
> 
> P.S. I've gone in that direction after seeing the following messages
> in
>  /var/log/kernel.log on normal power key press at runtime:
> [ 2727.596359] intel-hid INT33D5:00: unknown event 0xce
> [ 2727.769140] intel-hid INT33D5:00: unknown event 0xcf

  reply	other threads:[~2017-06-12 15:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 23:05 [PATCH 0/3] ACPI / sleep: Support power button wakeup from S2I on recent Dell laptops Jérôme de Bretagne
2017-06-07 23:22 ` Rafael J. Wysocki
2017-06-07 23:38   ` Jérôme de Bretagne
2017-06-07 23:47     ` Rafael J. Wysocki
2017-06-08 22:28 ` Mario.Limonciello
2017-06-08 23:44   ` Jérôme de Bretagne
2017-06-09 16:49     ` Mario.Limonciello
2017-06-09 23:11       ` Jérôme de Bretagne
2017-06-10  0:23         ` Mario.Limonciello
2017-06-11 22:01           ` Jérôme de Bretagne
2017-06-12 15:54             ` Srinivas Pandruvada [this message]
2017-06-12 19:13               ` Rafael J. Wysocki
2017-06-12 19:11             ` Rafael J. Wysocki
2017-06-12 20:00               ` Mario.Limonciello
2017-06-12 20:18                 ` Rafael J. Wysocki
2017-06-12 20:35                 ` Jérôme de Bretagne
2017-06-12 20:34                   ` Rafael J. Wysocki
2017-06-12 22:50                     ` Jérôme de Bretagne
2017-06-12 23:29                       ` Jérôme de Bretagne
2017-06-12 23:52                         ` Rafael J. Wysocki
2017-06-13  0:00                           ` Jérôme de Bretagne
2017-06-13  0:22                             ` Rafael J. Wysocki
2017-06-13 21:11                               ` Jérôme de Bretagne
2017-07-09 16:45                                 ` Jérôme de Bretagne
2017-06-12 23:37                       ` Rafael J. Wysocki
2017-06-12 22:38                   ` Jérôme de Bretagne
  -- strict thread matches above, loose matches on Subject: below --
2017-04-26 21:21 [PATCH 0/5] PM " Rafael J. Wysocki
2017-05-31 23:23 ` [PATCH 0/3] ACPI " Rafael J. Wysocki
2017-06-01 10:43   ` Andy Shevchenko
2017-06-01 11:50     ` Tom Lanyon
2017-06-01 14:59       ` Rafael J. Wysocki
2017-06-02  1:06         ` Tom Lanyon
2017-06-02 23:16           ` Rafael J. Wysocki
2017-06-01 15:00     ` Rafael J. Wysocki

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=1497282852.195383.56.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=Mario.Limonciello@dell.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dvhart@infradead.org \
    --cc=jerome.debretagne@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.