public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Andreas Kemnade <andreas@kemnade.info>,
	Sebastian Reichel <sre@kernel.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] power: supply: bd71828: add input current limit property
Date: Tue, 7 Apr 2026 09:33:25 +0300	[thread overview]
Message-ID: <a4c43b29-a1bf-4709-8521-c21ce4ee3e46@gmail.com> (raw)
In-Reply-To: <20260401-bd-inp-limit-v1-1-689eb22531e2@kemnade.info>

On 02/04/2026 00:17, Andreas Kemnade wrote:
> Add input current property to be able to work around issues created by
> automatic input limiting and have some control.
> Disabling the automatic management is another step.
> 

Hi Andreas!
Long time no chat :)

First of all, thanks for the work you do with the BD71828/79! I do 
admire the effort you're willing to put on it :)

I decided to just take a quick look at the BD71815 and BD72720, which 
can be operated using the same driver. I didn't see similar control on 
BD71815 data-sheet, so I just decided not to dig it further for now.

What comes to the BD72720, there is something:

The BD72720 has a VBUS_INLIM, which is a configurable current limit for 
the bus. This, I believe does NOT directly correspond to the DCIN limit. 
It _probably_ has similar impact when the DCIN is supplied, and when it 
is powerful enough to run the system. However, I believe the VBUS 
current limit is also having an impact when setup is powered from the 
battery, or when it is in "battery assist" -mode, (where the battery is 
used to "complement" the DCIN, if the DCIN isn't strong enough to power 
the system).

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! :)

Yours,
	-- Matti

-- 
---
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland

~~ When things go utterly wrong vim users can always type :help! ~~

      parent reply	other threads:[~2026-04-07  6:33 UTC|newest]

Thread overview: 5+ 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 [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=a4c43b29-a1bf-4709-8521-c21ce4ee3e46@gmail.com \
    --to=mazziesaccount@gmail.com \
    --cc=andreas@kemnade.info \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox