From: Pavel Machek <pavel@ucw.cz>
To: Sumeet Pawnikar <sumeet.r.pawnikar@intel.com>
Cc: rjw@rjwysocki.net, rui.zhang@intel.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, andriy.shevchenko@intel.com,
srinivas.pandruvada@linux.intel.com
Subject: Re: [PATCH v2] powercap: Add Power Limit4 support
Date: Tue, 28 Jul 2020 22:40:59 +0200 [thread overview]
Message-ID: <20200728204059.GF1012@bug> (raw)
In-Reply-To: <1594715306-10411-1-git-send-email-sumeet.r.pawnikar@intel.com>
Hi!
> Modern Intel Mobile platforms support power limit4 (PL4), which is
> the SoC package level maximum power limit (in Watts). It can be used
> to preemptively limits potential SoC power to prevent power spikes
> from tripping the power adapter and battery over-current protection.
> This patch enables this feature by exposing package level peak power
> capping control to userspace via RAPL sysfs interface. With this,
> application like DTPF can modify PL4 power limit, the similar way
> of other package power limit (PL1).
> As this feature is not tested on previous generations, here it is
> enabled only for the platform that has been verified to work,
> for safety concerns.
So what happens when the user sets this too high? Battery on fire? Or just sudden
poweroff?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2020-07-28 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 8:28 [PATCH v2] powercap: Add Power Limit4 support Sumeet Pawnikar
2020-07-14 13:21 ` Rafael J. Wysocki
2020-07-15 0:13 ` Srinivas Pandruvada
2020-07-16 5:10 ` Pawnikar, Sumeet R
2020-07-16 5:06 ` Pawnikar, Sumeet R
2020-07-28 20:40 ` Pavel Machek [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=20200728204059.GF1012@bug \
--to=pavel@ucw.cz \
--cc=andriy.shevchenko@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=sumeet.r.pawnikar@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.