platform-driver-x86.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: thysupremematrix@tuta.io
To: Hans de Goede <hansg@kernel.org>
Cc: Platform Driver X86 <platform-driver-x86@vger.kernel.org>
Subject: Re: hid.c - need enable_5_button_array=1 for hardware volume buttons
Date: Wed, 9 Jul 2025 18:50:17 +0200 (CEST)	[thread overview]
Message-ID: <OUk54Xd--F-9@tuta.io> (raw)
In-Reply-To: <98f55bc2-c996-4784-b9be-203984b03bc2@kernel.org>

Hi,

Is there any update regarding this? I understand we're all volunteers here, so I don't mind the wait — just want to know if it's getting processed. Also, another note that due to unforeseen circumstances I can't access my laptop for a few days until I reach the city.

Thanks,By Matrix :)



27 Jun 2025, 20:00 by hansg@kernel.org:

> Hi,
>
> On 27-Jun-25 10:45 AM, thysupremematrix@tuta.io wrote:
>
>> Hi,
>> I'm running Arch Linux on my HP ProBook x360 440 G1 but I couldn't get the hardware volume keys to work, though they worked in kernel versions older than 5.5. I found that after some digging, sudo modprobe intel_hid enable_5_button_array=1 seemed to work. The documentation at https://github.com/torvalds/linux/blob/master/drivers/platform/x86/intel/hid.c said to contact this email.
>>
>> I think this affects a lot more HP laptops, I found a forum post on Fedora forum https://discussion.fedoraproject.org/t/hardware-volume-buttons-not-responding-on-hp-laptop/97611 that said that this affected them. Maybe we need to apply the fix to every HP laptop that has volume controls? Thoughts?
>>
>
> Almost every HP laptop will have volume-buttons, but if you
> change your statement to "HP laptops which have a volume
> rocket on the side" then yes it might be a good idea
> to set enable_5_button_array=1 through a quirk on all of them.
>
> So maybe do a DMI match for vendor==HP product_name=*x360* .
>
> But first we should check if we can get the auto-detection to work.
>
> Can you run:
>
> sudo acpidump -o acpidump.txt
>
> And attach the generated acpidump.txt file to your next email ?
>
> Also if you can build your own kernel, can you add some
> debugging prints to drivers/platform/x86/intel/hid.c: 
> button_array_present(), seeing if either of
> the intel_hid_evaluate_method() calls there succeeds and
> if yes then also print the returned caps ?
>
> Regards,
>
> Hans
>


      parent reply	other threads:[~2025-07-09 16:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27  8:45 hid.c - need enable_5_button_array=1 for hardware volume buttons thysupremematrix
2025-06-27 14:30 ` Hans de Goede
     [not found]   ` <OTq-z8M--F-9@tuta.io>
2025-06-29  4:59     ` thysupremematrix
2025-07-09 16:50   ` thysupremematrix [this message]

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=OUk54Xd--F-9@tuta.io \
    --to=thysupremematrix@tuta.io \
    --cc=hansg@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).