mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: Alan Stern <stern@rowland.harvard.edu>, Oliver Neukum <oneukum@suse.com>
Cc: Evan Green <evgreen@chromium.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Mathias Nyman <mathias.nyman@intel.com>,
	Rajat Jain <rajatja@chromium.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Razvan Heghedus <heghedus.razvan@gmail.com>,
	Wei Ming Chen <jj251510319013@gmail.com>,
	Youngjin Jang <yj84.jang@samsung.com>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 0/2] USB: Quiesce interrupts across pm freeze
Date: Tue, 19 Apr 2022 17:51:38 +0200	[thread overview]
Message-ID: <8321b2c6-5bdb-2853-6812-50cd4e4d1bc7@suse.com> (raw)
In-Reply-To: <Yl7Iz/lGk3fITzMK@rowland.harvard.edu>



On 19.04.22 16:35, Alan Stern wrote:
> On Tue, Apr 19, 2022 at 09:05:53AM +0200, Oliver Neukum wrote:
>
>
> We have a set of quirky devices that need HID_QUIRK_ALWAYS_POLL.
> They have the nasty firmware bug that, if you suspend them without
> remote wakeup, they will crash or reset themselves.
> I am afraid that has an obvious relevance to your cool patches.
> I am not completely sure how to deal with this. It seems to me that the
> quirk will need to be shifted from HID to core USB and thaw() needs to
> be translated into usb_device_reset() + reset_resume() for them,
> but I am not really sure about the optimal mechanism.
> We may not need to do anything.  This patch specifically addresses 
> hibernation, not system suspend or runtime suspend.  A device crashing 
> or resetting during hibernation is not at all unusual; we should be able 
> to handle such cases properly.
>
> The THAW part of suspend-to-hibernation is used only for writing the 
> memory image to permanent storage.  I doubt that a malfunctioning HID 
> device would interfere with this process.
>
True, if and only if all goes well. At the time thaw() has run writing
the image to disk can still fail. In that case the devices will still
be needed.

    Regards
        Oliver


  reply	other threads:[~2022-04-19 15:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 21:00 Evan Green
2022-04-18 21:00 ` [PATCH v2 1/2] USB: core: Disable remote wakeup for freeze/quiesce Evan Green
2022-04-19 14:41   ` Alan Stern
2022-04-20 19:30     ` Evan Green
2022-04-18 21:00 ` [PATCH v2 2/2] USB: hcd-pci: Fully suspend across freeze/thaw cycle Evan Green
2022-04-19 14:43   ` Alan Stern
2022-04-19  7:05 ` [PATCH v2 0/2] USB: Quiesce interrupts across pm freeze Oliver Neukum
2022-04-19 14:35   ` Alan Stern
2022-04-19 15:51     ` Oliver Neukum [this message]
2022-04-19 17:49       ` Alan Stern
2022-04-20  8:47         ` Oliver Neukum
2022-04-20 14:09           ` Alan Stern

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=8321b2c6-5bdb-2853-6812-50cd4e4d1bc7@suse.com \
    --to=oneukum@suse.com \
    --cc=bhelgaas@google.com \
    --cc=evgreen@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heghedus.razvan@gmail.com \
    --cc=jj251510319013@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rajatja@chromium.org \
    --cc=stern@rowland.harvard.edu \
    --cc=tglx@linutronix.de \
    --cc=yj84.jang@samsung.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

Powered by JetHome