From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Kai-Heng Feng <kai.heng.feng@canonical.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
jorge.lopez2@hp.com, acelan.kao@canonical.com,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v3] platform/x86/hp: Avoid spurious wakeup on HP ProOne 440
Date: Fri, 6 Sep 2024 21:39:33 +0300 (EEST) [thread overview]
Message-ID: <322162d3-ce9d-27fd-6ac3-204d46e7256e@linux.intel.com> (raw)
In-Reply-To: <3e12ef27-30e4-4b5a-acd6-5d3023a82941@redhat.com>
On Fri, 6 Sep 2024, Hans de Goede wrote:
> On 9/6/24 7:30 AM, Kai-Heng Feng wrote:
> > The HP ProOne 440 has a power saving design that when the display is
> > off, it also cuts the USB touchscreen device's power off.
> >
> > This can cause system early wakeup because cutting the power off the
> > touchscreen device creates a disconnect event and prevent the system
> > from suspending:
> > [ 445.814574] hub 2-0:1.0: hub_suspend
> > [ 445.814652] usb usb2: bus suspend, wakeup 0
> > [ 445.824629] xhci_hcd 0000:00:14.0: Port change event, 1-11, id 11, portsc: 0x202a0
> > [ 445.824639] xhci_hcd 0000:00:14.0: resume root hub
> > [ 445.824651] xhci_hcd 0000:00:14.0: handle_port_status: starting usb1 port polling.
> > [ 445.844039] xhci_hcd 0000:00:14.0: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x20 returns -16
> > [ 445.844058] xhci_hcd 0000:00:14.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1c0 returns -16
> > [ 445.844072] xhci_hcd 0000:00:14.0: PM: failed to suspend async: error -16
> > [ 446.276101] PM: Some devices failed to suspend, or early wake event detected
> >
> > So add a quirk to make sure the following is happening:
> > 1. Let the i915 driver suspend first, to ensure the display is off so
> > system also cuts the USB touchscreen's power.
> > 2. Wait a while to let the USB disconnect event fire and get handled.
> > 3. Since the disconnect event already happened, the xhci's suspend
> > routine won't be interrupted anymore.
> >
> > Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
>
> Thanks, patch looks good to me:
>
> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
>
> Ilpo, do you plan to do another fixes pull-request for 6.11,
> or shall I add this to for-next to target 6.12-rc1 ?
>
> Either way works for me. If you plan to do another fixes
> pull-request, note that I plan to post a v2 of the panasonic
> patches this Monday.
Hi Hans,
I was thinking that perhaps one more is necessary the next week.
--
i.
next prev parent reply other threads:[~2024-09-06 18:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 5:30 [PATCH v3] platform/x86/hp: Avoid spurious wakeup on HP ProOne 440 Kai-Heng Feng
2024-09-06 7:35 ` Hans de Goede
2024-09-06 18:39 ` Ilpo Järvinen [this message]
2024-09-06 19:40 ` Hans de Goede
2024-09-06 14:22 ` Alan Stern
2024-09-09 3:05 ` Kai-Heng Feng
2024-09-09 14:38 ` Alan Stern
2024-09-10 3:33 ` Kai-Heng Feng
2024-09-10 13:13 ` Alan Stern
2024-09-12 6:28 ` Kai-Heng Feng
2024-09-12 15:06 ` Alan Stern
2024-10-05 14:25 ` Hans de Goede
2024-10-07 4:22 ` Kai-Heng Feng
2024-10-07 14:53 ` Mario Limonciello
2024-10-21 13:04 ` 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=322162d3-ce9d-27fd-6ac3-204d46e7256e@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=acelan.kao@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=jorge.lopez2@hp.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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