From: Pavel Machek <pavel@ucw.cz>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-pm@vger.kernel.org, sre@kernel.org,
Sameer Nanda <snanda@chromium.org>,
bleung@chromium.org, rjw@rjwysocki.net, gwendal@chromium.org,
linux-kernel@vger.kernel.org, Len Brown <len.brown@intel.com>,
groeck@chromium.org, Adam.Thomson.Opensource@diasemi.com,
kernel@collabora.com
Subject: Re: [RESEND PATCH v3 1/2] power: supply: add input voltage limit property
Date: Tue, 16 Apr 2019 09:19:41 +0200 [thread overview]
Message-ID: <20190416071941.GB14538@amd> (raw)
In-Reply-To: <20190415220049.14924-1-enric.balletbo@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
Hi!
> This patch exposes a new property, similar to input current limit, to
> re-configure the maximum voltage from the external supply at runtime
> based on system-level knowledge or user input.
Well, and I suspect it should expose input power limit, not input
voltage limit.
DC-DC convertor efficiency normally does not much depend on input
voltage....
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-04-16 7:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 22:00 [RESEND PATCH v3 1/2] power: supply: add input voltage limit property Enric Balletbo i Serra
2019-04-15 22:00 ` [RESEND PATCH v3 2/2] power: supply: cros: allow to set input voltage and current limit Enric Balletbo i Serra
2019-04-16 7:19 ` Pavel Machek [this message]
2019-04-16 8:42 ` [RESEND PATCH v3 1/2] power: supply: add input voltage limit property Enric Balletbo i Serra
2019-05-02 21:01 ` Sebastian Reichel
2019-05-02 21:12 ` Pavel Machek
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=20190416071941.GB14538@amd \
--to=pavel@ucw.cz \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=kernel@collabora.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=snanda@chromium.org \
--cc=sre@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 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.