diff options
| author | Daniel Lezcano <daniel.lezcano@oss.qualcomm.com> | 2026-08-21 17:39:49 +0200 |
|---|---|---|
| committer | Sebastian Reichel <sebastian.reichel@collabora.com> | 2026-10-04 18:52:44 +0200 |
| commit | 23a00d8fb0452a4b182f4fea01e244f47758f4ee (patch) | |
| tree | d1d52f34f7cc1ebd3a6a8a19db36f5c5b42e1230 /rust/kernel/alloc | |
| parent | 455e49c6700c8111d492923952a1fe3b98da0195 (diff) | |
power: supply: Fix power limit documentation
The documentation for the input current and voltage limits recommends
using those properties for problems that can be solved using a power
limit. This contradicts the recommendation to prefer input_power_limit
for such cases.
Similarly, the input_power_limit documentation recommends using the
current or voltage limits for problems that can be solved with a power
limit, which conveys the opposite of the intended meaning.
Fix the wording to clarify that input_power_limit should be preferred
whenever a power limit can address the problem, while current or
voltage limits should be used when it cannot.
Signed-off-by: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
Link: https://patch.msgid.link/20260821153949.2914201-1-daniel.lezcano@oss.qualcomm.com
Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Diffstat (limited to 'rust/kernel/alloc')
0 files changed, 0 insertions, 0 deletions
