X86 platform drivers
 help / color / mirror / Atom feed
From: Maxim Mikityanskiy <maxtram95@gmail.com>
To: "Lopez, Jorge A (Security)" <jorge.lopez2@hp.com>
Cc: "Alex Hung" <alexhung@gmail.com>,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Mark Gross" <markgross@kernel.org>,
	"platform-driver-x86@vger.kernel.org"
	<platform-driver-x86@vger.kernel.org>,
	"Kai-Heng Feng" <kai.heng.feng@canonical.com>,
	"Mario Limonciello" <mario.limonciello@amd.com>,
	"Barnabás Pőcze" <pobrn@protonmail.com>,
	"Rishit Bansal" <rishitbansal0@gmail.com>,
	"Enver Balalic" <balalic.enver@gmail.com>
Subject: Re: Firmware upgrade broke SW_TABLET_MODE on HP Dragonfly G2
Date: Tue, 7 Feb 2023 18:49:33 +0200	[thread overview]
Message-ID: <Y+KBHcOwGMG5Z+zA@mail.gmail.com> (raw)
In-Reply-To: <PH0PR84MB1953959E3B2E51839A529CBFA8DB9@PH0PR84MB1953.NAMPRD84.PROD.OUTLOOK.COM>

On Tue, Feb 07, 2023 at 04:14:18PM +0000, Lopez, Jorge A (Security) wrote:
> Hi Maxim,
> 
> Thank you for the detailed debugging and information.  
> 
> The BIOS upgrade should have not affected the tablet mode behaviour.  Unfortunately, HP does not have an official process to support HP Dragonfly G2 under Linux that I am aware of with exception of a few HP team members.  Nonetheless, this is unacceptable, and I will forward the information to the BIOS team for them to investigate.
> Personally, I work in a different team so I will try to get a patch out depending on BIOS team response.  

Thanks a lot Jorge, you are really helpful! Let's see what the BIOS team
says then, please keep me updated.

> 
> 
> 
> Regards,
> 
> Jorge Lopez
> Hewlett-Packard 
> 
> "Once you stop learning, you start dying"
> Albert Einstein
> 
> > -----Original Message-----
> > From: Maxim Mikityanskiy <maxtram95@gmail.com>
> > Sent: Tuesday, February 7, 2023 8:07 AM
> > To: Lopez, Jorge A (Security) <jorge.lopez2@hp.com>; Alex Hung
> > <alexhung@gmail.com>; Hans de Goede <hdegoede@redhat.com>; Mark
> > Gross <markgross@kernel.org>; platform-driver-x86@vger.kernel.org
> > Cc: Kai-Heng Feng <kai.heng.feng@canonical.com>; Mario Limonciello
> > <mario.limonciello@amd.com>; Barnabás Pőcze <pobrn@protonmail.com>;
> > Rishit Bansal <rishitbansal0@gmail.com>; Enver Balalic
> > <balalic.enver@gmail.com>
> > Subject: Firmware upgrade broke SW_TABLET_MODE on HP Dragonfly G2
> > 
> > CAUTION: External Email
> > 
> > Hello,
> > 
> > I use HP Dragonfly G2, Arch linux, kernel 6.1.9, and I upgraded the firmware
> > from 1.9.1 to 1.11 (using fwupdmgr/LVFS), and this upgrade broke tablet
> > mode detection on my laptop. I did some debugging, and that's what I
> > found:
> > 
> > 1. On both firmware versions: hp-wmi registers SW_TABLET_MODE, but
> > never reports events. Although HPWMI_EVENT_GUID is present on my
> > system, hp_wmi_notify never gets any events of any kind. Good thing is that
> > at least hp_wmi_get_tablet_mode (/sys/devices/platform/hp-wmi/tablet)
> > works on my laptop.
> > 
> > 2. "Intel HID switches" is the device that reports actual SW_TABLET_MODE
> > events on firmware 1.9.1, but not anymore on firmware 1.11.
> > SW_TABLET_MODE is registered after the first event (by auto_add_switch,
> > on firmware 1.9.1 only).
> > 
> > 3. SW_TABLET_MODE reported by "Intel HID switches" (on firmware 1.9.1)
> > differs from /sys/devices/platform/hp-wmi/tablet, when the laptop is not
> > fully folded, but put into a stand position (the hinge is open more than
> > 180°, the keyboard faces the table). The reason is because hp-wmi only
> > treats system_device_mode[0] == 6 as tablet, but 5 (stand mode) isn't
> > included, while "Intel HID switches" report SW_TABLET_MODE = 1 in the
> > stand mode.
> > 
> > I'm pretty sure about my findings, I flashed each of these two firmware
> > versions again and tested what happens in hp-wmi and intel/hid, of course
> > without changing any software versions.
> > 
> > Regarding point 3, I can send a patch for hp-wmi, but it's not going to be
> > useful for my laptop because of point 1, and I can't be fully sure it doesn't
> > break other HP laptops (unless Jorge confirms?).
> > 
> > Now back to the main topic. There are two directions that I see:
> > 
> > 1. Fix the regression in the firmware and make Intel HID switches work
> > again. Unfortunately, I didn't have success reporting the firmware bug via
> > HP customer support, and they don't seem to admit the bug or even having
> > uploaded their firmware to LVFS. If Jorge (or anyone else on the mailing list)
> > could give me some contact of a person responsible for firmware on LVFS or
> > the proper way to file a bug report, I would highly appreciate it. Maybe Alex
> > has an idea why intel/hid could stop working?
> > 
> > 2. Somehow tweak hp-wmi to start getting events on my laptop and switch
> > to SW_TABLET_MODE reports from hp-wmi (also fixing the stand mode
> > reports). For this, I would need help from Jorge (or someone who knows HP
> > laptop internals), I don't have ideas why it might be broken for me.
> > 
> > I will appreciate any help, and I'm happy to provide additional information
> > if needed.
> > 
> > Thanks,
> > Max
> 

  reply	other threads:[~2023-02-07 16:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 14:07 Firmware upgrade broke SW_TABLET_MODE on HP Dragonfly G2 Maxim Mikityanskiy
2023-02-07 16:14 ` Lopez, Jorge A (Security)
2023-02-07 16:49   ` Maxim Mikityanskiy [this message]
2023-02-08 17:32 ` Richard Hughes
     [not found]   ` <PH0PR84MB1953825BC90B268904C6C7E5A8D89@PH0PR84MB1953.NAMPRD84.PROD.OUTLOOK.COM>
2023-02-08 20:09     ` Richard Hughes
2023-02-08 21:43       ` Maxim Mikityanskiy
2023-04-24 10:37         ` Richard Hughes
2023-04-24 14:18           ` Lopez, Jorge A (Security)
2023-04-25 15:05             ` Lopez, Jorge A (Security)
2023-04-27 16:36               ` Maxim Mikityanskiy
2023-04-27 19:26                 ` Lopez, Jorge A (Security)
2023-05-01 13:58                   ` Maxim Mikityanskiy

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=Y+KBHcOwGMG5Z+zA@mail.gmail.com \
    --to=maxtram95@gmail.com \
    --cc=alexhung@gmail.com \
    --cc=balalic.enver@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=jorge.lopez2@hp.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=mario.limonciello@amd.com \
    --cc=markgross@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=pobrn@protonmail.com \
    --cc=rishitbansal0@gmail.com \
    /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