linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Subject: Re: [PATCH v3 2/2] power: supply: ltc3350-charger: Add driver
Date: Mon, 15 Apr 2024 15:08:01 +0200	[thread overview]
Message-ID: <cda9f2ff-d13f-4421-ad10-72ab29fa0024@topic.nl> (raw)
In-Reply-To: <lxxwadaf2mrghy2kygm3cucb7ygl5qu4dxnmpbancrm2hwjm4g@5eudactyudca>

On 14-04-2024 19:29, Sebastian Reichel wrote:
> [+cc Nicolas]
>
> Hello Mike,
>
> On Fri, Apr 12, 2024 at 08:53:58AM +0200, Mike Looijmans wrote:
>>> please share output of
>>> ./tools/testing/selftests/power_supply/test_power_supply_properties.sh
>>> below the fold with your next submission. It's useful for verifying,
>>> that you got the unit scaling correct for the standard properties :)
>> Will do. Did a quick run on the driver as it is now, that yields the
>> following output:
>>
>> (Any thoughts on the "arithmetic syntax error" messages?)
> The script contains some bash specific shell extensions and should
> use /bin/bash instead of /bin/sh in the shebang. Just call it with
> /bin/bash ./tools/testing/... and you should get rid of them :)

Yeah, installing full bash (instead of busybox ash) on the board fixes 
these messages.


>
> Nicolas, do you want to send a fix for that to Shuah with Reported-by
> from Mike?
>
> [...]
>
>> # Reported: '1' ()
>> ok 6 ltc3350.sysfs.online
> [...]
>
>> # Reported: '711600' uA (711.6 mA)
>> ok 24 ltc3350.sysfs.current_now
> So it's full, but still getting charged with 0.7 Amps at ~23V
> (i.e. 16W)? That seems quite high.

The "current" is also feeding the system, not just the capacitors. 
(panel backlight being the main consumer)

I modeled the current into the caps as 
POWER_SUPPLY_PROP_CONSTANT_CHARGE_CURRENT but in retrospect, that may 
not be the right place.  Maybe that should be the "CURRENT_NOW" of the 
battery component?




...


-- 
Mike Looijmans
System Expert

TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands

T: +31 (0) 499 33 69 69
E: mike.looijmans@topic.nl
W: www.topic.nl




  reply	other threads:[~2024-04-15 13:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.66250b05-de15-4489-babe-49dcb09de02a@emailsignatures365.codetwo.com>
2024-04-09 13:54 ` [PATCH v3 1/2] dt-bindings: power: supply: ltc3350-charger: Add bindings Mike Looijmans
     [not found]   ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.dab85cfc-973d-4930-8fea-324aa26b5801@emailsignatures365.codetwo.com>
2024-04-09 13:54     ` [PATCH v3 2/2] power: supply: ltc3350-charger: Add driver Mike Looijmans
2024-04-10  7:56       ` Sebastian Reichel
2024-04-12  6:53         ` Mike Looijmans
2024-04-14 17:29           ` Sebastian Reichel
2024-04-15 13:08             ` Mike Looijmans [this message]
2024-04-15 15:34             ` Nícolas F. R. A. Prado

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=cda9f2ff-d13f-4421-ad10-72ab29fa0024@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nfraprado@collabora.com \
    --cc=sebastian.reichel@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).