All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Sebastian Reichel <sre@kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v2] power: supply_core: Pass pointer to battery info
Date: Tue, 14 Dec 2021 06:53:35 +0000	[thread overview]
Message-ID: <9bed108f-9600-871f-d126-64f9a8796bee@fi.rohmeurope.com> (raw)
In-Reply-To: <04df0bff-87b0-d39a-4f5c-bbeb7f3e0cd1@gmail.com>

On 12/14/21 08:44, Matti Vaittinen wrote:
> Hi deee Ho peeps,
> 
> On 12/13/21 11:23, Matti Vaittinen wrote:
>> On 12/10/21 07:57, Matti Vaittinen wrote:
>>> On Thu, Dec 9, 2021 at 2:46 AM Linus Walleij 
>>> <linus.walleij@linaro.org> wrote:
>>
>>>> Also I would love if you could test v2 on hardware!
> 

> It appears the patch worked as expected - but it also appears the 
> BD99954 driver does not handle missing info too well... I typoed the 
> trickle-charger current property in DT - and as a result the driver 
> decided -EINVAL to be valid value (just too large) and set the largest 
> current BD99954 supports for trickle-charging... 

I should have looked this more carefully. It appears the BD99954 does 
check for the -EINVAL - but the power_supply_core does not initialize 
the tricklecharge_current_ua to -EINVAL.

> Linus, want to fix this while at it - or do you prefer me to patch the 
> BD99954 with some sanity checks? I think it'd be nice to get the fixes 
> in stable so it might be best to add the sanity checks before changing 
> the battery-info allocation - that might be nicer for the stable folks. 
> (I guess you have plenty of other things to code + some IRL tasks as 
> well ...;] So, I can patch this but it means there is likely to be some 
> conflicts with your series. Hence I thought I'll ask if you wish to add 
> checks for uninitialized battery-info values)

I think this is a trivial thing to fix and won't be too hard a conflict 
to resolve :) So I'll just send a patch

Sorry for the hassle.

So, what it's worth:
Reviewed-By: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Tested-By: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>

-- 
The Linux Kernel guy at ROHM Semiconductors

Matti Vaittinen, Linux device drivers
ROHM Semiconductors, Finland SWDC
Kiviharjunlenkki 1E
90220 OULU
FINLAND

~~ this year is the year of a signature writers block ~~

  reply	other threads:[~2021-12-14  6:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06  0:06 [PATCH v2] power: supply_core: Pass pointer to battery info Linus Walleij
2021-12-08  6:46 ` Matti Vaittinen
2021-12-09  0:46   ` Linus Walleij
2021-12-10  5:57     ` Matti Vaittinen
2021-12-13  9:23       ` Matti Vaittinen
2021-12-13  9:23       ` Matti Vaittinen
2021-12-14  6:44         ` Matti Vaittinen
2021-12-14  6:53           ` Vaittinen, Matti [this message]
2021-12-14  7:49             ` Vaittinen, Matti

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=9bed108f-9600-871f-d126-64f9a8796bee@fi.rohmeurope.com \
    --to=matti.vaittinen@fi.rohmeurope.com \
    --cc=linus.walleij@linaro.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 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.