From: Chanwoo Choi <cw00.choi@samsung.com>
To: Pavel Machek <pavel@ucw.cz>, Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-samsung-soc@vger.kernel.org,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Lukasz Luba <l.luba@partner.samsung.com>,
Markus Reichl <m.reichl@fivetechno.de>
Subject: Re: [PATCH] devfreq: Suspend all devices on system shutdown
Date: Thu, 7 Mar 2019 10:27:02 +0900 [thread overview]
Message-ID: <5621c652-6786-6bbb-ffbd-71567d8d882e@samsung.com> (raw)
In-Reply-To: <20190306231014.GE7915@amd>
Hi Pavel,
On 19. 3. 7. 오전 8:10, Pavel Machek wrote:
> On Fri 2019-01-25 14:54:03, Marek Szyprowski wrote:
>> This way devfreq core ensures that all its devices will be set to safe
>> operation points before reboot operation. There are board on which some
>> aggressive power saving operation points are behind the capabilities of
>> the bootloader to properly reset the hardware and boot the board. This
>> way one can avoid board crash early after reboot.
>>
>> Similar pattern is used in CPUfreq subsystem.
>
> This looks somehow dangerous to me. I guess this will break someone's
> shutdown, and on battery-powered devices, that's quite bad thing to
> do.
This patch executes the devfreq_suspend() for all devfreq devices.
The devfreq_suspend() does the following:
1. (mandatory) stop the polling of governor.
2. (optional) If devfreq device specifies the 'opp-suspend'
property in DT, the devfreq changes the frequency by using
the devfreq->suspend_freq.
If the user of devfreq device doesn't want to change the frequency
during the system shutdown, just don't add the 'opp-suspend' property
in DT. And the devfreq_suspend() will just stop the polling for governor.
Even if on battery-powered devices, I think it is not problem
to stop the polling of governor during the system shutdown.
In my case, I don't know what is dangerous.
Could you explain it more detailed.
>
> Could we explicitely do it only for devices that need it?
> Pavel
>
>
--
Best Regards,
Chanwoo Choi
Samsung Electronics
prev parent reply other threads:[~2019-03-07 1:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190125135414eucas1p2ffc71c63f1a27f67d076dec889954b40@eucas1p2.samsung.com>
2019-01-25 13:54 ` Marek Szyprowski
2019-01-28 1:17 ` Chanwoo Choi
[not found] ` <CGME20190125135414eucas1p2ffc71c63f1a27f67d076dec889954b40@epcms1p4>
2019-01-28 8:05 ` MyungJoo Ham
2019-01-28 11:57 ` Marek Szyprowski
2019-03-06 23:10 ` Pavel Machek
2019-03-07 1:27 ` Chanwoo Choi [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=5621c652-6786-6bbb-ffbd-71567d8d882e@samsung.com \
--to=cw00.choi@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=krzk@kernel.org \
--cc=l.luba@partner.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.reichl@fivetechno.de \
--cc=m.szyprowski@samsung.com \
--cc=myungjoo.ham@samsung.com \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®