From: pingshuo <pingshuo@uniontech.com>
To: Pavel Machek <pavel@ucw.cz>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Len Brown <len.brown@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hibernation:stop resume screen during hibernation
Date: Thu, 24 Jun 2021 10:06:19 +0800 [thread overview]
Message-ID: <f1ac4975-775e-93c4-c3a7-8b3438b6373d@uniontech.com> (raw)
In-Reply-To: <20210622134703.GA12358@duo.ucw.cz>
>> The display will be woken up during hibernation.
>
> That actually depends on its driver.
>
>> if the computer equipment is poor, it will cause the screen to flicker.
>> Skip to resume the display devices in "thaw".
> But this patch looks like a proof of concept rather than a proper solution.
>This needs to be done more carefully.
When entering hibernation, the display screen will be off first, then
will be on (the image data is written to the disk at this time), and
finally the display screen will be off again.
> If you want to deal with PCI devices, that needs to happen at the PCI
bus type level in the first place
what is the "PCI bus type level" mean ? Do you mean to modify it in
dev->bus or dev-> bus -> pm?
We tested different graphics cards,like amdgpu, radeon,i915,nvidia,
this issue occurs during entering hibernation.
Based on the above test, several graphics cards will be resumed and the
screen is on, so we add code here.
Did you have any idea if these code is added in here ?
Please answer a question for me.
Resuming device is to write the image to the disk. Is it necessary to
wake up all devices? Why not just wake up the devices related to writing
image?
Anticipate your response.
thanks,
pingshuo
next prev parent reply other threads:[~2021-06-24 2:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 12:45 [PATCH] hibernation:stop resume screen during hibernation pingshuo
2021-06-22 13:06 ` Rafael J. Wysocki
2021-06-22 13:47 ` Pavel Machek
2021-06-24 2:06 ` pingshuo [this message]
2021-06-22 13:19 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2021-06-22 8:38 pingshuo
2021-06-22 10:22 ` Greg KH
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=f1ac4975-775e-93c4-c3a7-8b3438b6373d@uniontech.com \
--to=pingshuo@uniontech.com \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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).