X86 platform drivers
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Dennis Nezic <dennisn@dennisn.mooo.com>
Cc: Armin Wolf <W_Armin@gmx.de>, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 0/2] platform/x86: Add ACPI quickstart button driver
Date: Thu, 1 Feb 2024 16:03:14 +0100	[thread overview]
Message-ID: <63004059-ce2e-4896-977f-c2c8f1b1316d@redhat.com> (raw)
In-Reply-To: <ZbuxlZq6sGEAlI4n@panther>

Hi,

On 2/1/24 15:58, Dennis Nezic wrote:
> On 01 Feb 15:44, Hans de Goede wrote:
>> Hi Dennis,
>>
>> On 2/1/24 15:09, Dennis Nezic wrote:
>>> On 31 Jan 18:36, Armin Wolf wrote:
>>>> Am 31.01.24 um 18:17 schrieb Dennis Nezic:
>>>>
>>>>> On 31 Jan 18:07, Armin Wolf wrote:
>>>>>> The issue is that you machine does not support runtime button events on the quickstart button,
>>>>>> only wake events.
>>>>>>
>>>>>> Can you check if you can now use the unresponsive button to wake the system?
>>>>> Nope, only the main power button can wake it from a sleep state, those
>>>>> quickstart buttons do nothing.
>>>>
>>>> Can you check if this is still the case when you configure the PNP0C32 ACPI device to be able
>>>> to generate wakeup events (from S5, S4 and S3)?
>>>> Maybe you should unload the quickstart driver for this test.
>>>>
>>>> If the button still does nothing, then it could be that the quickstart device is not handling
>>>> this button. Then we need some new ideas.
>>>
>>> Yea I don't think quickstart/hp-wmi is handling it. As I said, the
>>> behavior is exactly the same as if I didn't have it compiled at all.
>>>
>>> I enabled it via /proc/acpi/wakeup (it was disabled initially) (the
>>> S-state in that file only mentions S5, but I guess that should include
>>> all the less sleepy states too). No effect. I tried with and without the
>>> quickstart device.
>>
>> Perhaps this is simply a hw defect, have you seen the button
>> working under Windows? Maybe at some point some liquid
>> got inside the keyboard around that button?
> 
> Unlikely. I have 2 of these laptops, same behavior. Never saw them with
> Windows.
> 
>> The main keyboard buttons are typically membrane style buttons.
>>
>> But extra media keys might be more remote control style, where
>> there are not rubber domes beneath hard plastic keys, but the
>> keys themselves are rubber, with some carbon conductor on
>> the bottom and they directly connect 2 copper pads on the PCB.
>>
>> These remote style buttons are quite sensitive to dirt getting
>> underneath (just like the buttons in a typical TV remote).
>>
>> Assuming you can get things disassembled easily you may want
>> to try and clean things.
> 
> These ones are more like a phone touchscreen ... it's just a long solid
> plastic sheet, no distinct edges (annoying), with leds underneath. All
> the led's get illuminated when touched, even this mysterious "info" key.

Interesting. If the LED underneath lights up when touching then
I agree that it is unlikely that this is a hw defect.

Regards.

Hans




  reply	other threads:[~2024-02-01 15:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 11:16 [PATCH 0/2] platform/x86: Add ACPI quickstart button driver Armin Wolf
2024-01-31 11:16 ` [PATCH 1/2] platform/x86: Add ACPI quickstart button (PNP0C32) driver Armin Wolf
2024-02-06 10:37   ` Ilpo Järvinen
2024-01-31 11:16 ` [PATCH 2/2] platform/x86: toshiba_acpi: Add quirk for buttons on Z830 Armin Wolf
2024-01-31 15:42 ` [PATCH 0/2] platform/x86: Add ACPI quickstart button driver Dennis Nezic
2024-01-31 17:07   ` Armin Wolf
2024-01-31 17:17     ` Dennis Nezic
2024-01-31 17:36       ` Armin Wolf
2024-02-01 14:09         ` Dennis Nezic
2024-02-01 14:44           ` Hans de Goede
2024-02-01 14:58             ` Dennis Nezic
2024-02-01 15:03               ` Hans de Goede [this message]
2024-03-24 14:55 ` Hans de Goede
2024-03-25 20:01   ` Armin Wolf
2024-03-25 21:37   ` Arvid Norlander
2024-03-27 20:16 ` Hans de Goede

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=63004059-ce2e-4896-977f-c2c8f1b1316d@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=W_Armin@gmx.de \
    --cc=dennisn@dennisn.mooo.com \
    --cc=platform-driver-x86@vger.kernel.org \
    /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