From: Andreas Kemnade <andreas@kemnade.info>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Sebastian Reichel <sre@kernel.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] power: supply: bd71828: add input current limit property
Date: Wed, 15 Apr 2026 22:13:58 +0200 [thread overview]
Message-ID: <20260415221358.59574987@kemnade.info> (raw)
In-Reply-To: <a4c43b29-a1bf-4709-8521-c21ce4ee3e46@gmail.com>
On Tue, 7 Apr 2026 09:33:25 +0300
Matti Vaittinen <mazziesaccount@gmail.com> wrote:
> I am afraid I don't know your use-case for the control of the DCIN input
> limit well enough to decide, if the BD72720 would need something similar
> - or if the VBUS_INLIM should be tied to the same knob. If you have the
> enthusiasm to write some more words ... I am keen on learning! :)
Justification for this patch is mostly: there is a standard interface
for this functionality and the chip has that functionality.
The bigger picture: Attach a power source with changing properties causes
mess. To repreduce issues at my desk, I have played around with a labor power
supply with changeable current limitation, turining it down to zero (so
power is off) then turning it on slowly again, no charging will happen. My
usual way around such a problem is to clear DCIN_ILIM_EN (will add a sysfs
attribute for that) and set some conservative current.
Regards,
Andreas
next prev parent reply other threads:[~2026-04-15 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 21:17 [PATCH] power: supply: bd71828: add input current limit property Andreas Kemnade
2026-04-02 22:54 ` Sebastian Reichel
2026-04-07 5:34 ` Matti Vaittinen
2026-04-07 5:48 ` Matti Vaittinen
2026-04-07 6:33 ` Matti Vaittinen
2026-04-15 20:13 ` Andreas Kemnade [this message]
2026-04-17 7:33 ` Matti Vaittinen
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=20260415221358.59574987@kemnade.info \
--to=andreas@kemnade.info \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox