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
Subject: Re: [PATCH v4] power/supply: Add ltc4162-l-charger
Date: Thu, 7 Jan 2021 15:35:11 +0100 [thread overview]
Message-ID: <53f764f3-8a0f-92dd-4a22-cd05c785c178@topic.nl> (raw)
In-Reply-To: <20210106151644.jyfpjvazof565mhk@earth.universe>
Met vriendelijke groet / kind regards,
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@topicproducts.com
W: www.topicproducts.com
Please consider the environment before printing this e-mail
On 06-01-2021 16:16, Sebastian Reichel wrote:
> Hi,
>
> On Wed, Jan 06, 2021 at 08:55:57AM +0100, Mike Looijmans wrote:
>> Add support for the LTC4162-L Li-Ion battery charger. The driver allows
>> reading back telemetry and to set some charging options like the input
>> current limit.
>>
>> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
>> ---
>> v2: Use microohm units instead of milliohm
>> Add interrupt support using smbalert
>> Support obtaining cell-count from devicetree
>> v3: Fix overflows in calculations involving resistor values
>> v4: Use attr_grp member to register attributes
>> Report input current/voltage for charger and make battery
>> voltage and current into sysfs attributes
> Fine with me until we have a better way to solve the problem. IIUIC
> you no longer have access to the hardware anyways? But you need to
> document the custom sysfs nodes: Please document them in the
> following file:
>
> Documentation/ABI/testing/sysfs-class-power-ltc4162l
v5 is on its way with a description.
I currently don't have access to the hardware, so these changes were
only compile-tested.
> [...]
>
>> +static int ltc4162l_remove(struct i2c_client *client)
>> +{
>> + struct ltc4162l_info *info = i2c_get_clientdata(client);
>> +
>> + sysfs_remove_group(&info->charger->dev.kobj, <c4162l_attr_group);
>> +
>> + return 0;
>> +}
> power-supply core automatically removes the sysfs groups specified
> in power_supply_config.attr_grp.
Ah, good catch, missed that.
>
> -- Sebastian
--
Mike Looijmans
prev parent reply other threads:[~2021-01-07 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 7:55 Mike Looijmans
2021-01-06 15:16 ` Sebastian Reichel
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.2ff663b7-f328-4158-a5aa-d92c6c556384@emailsignatures365.codetwo.com>
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.0d2bd5fa-15cc-4b27-b94e-83614f9e5b38.90a3859f-b700-411d-bf45-dcf42e1ca00a@emailsignatures365.codetwo.com>
2021-01-07 14:35 ` Mike Looijmans [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=53f764f3-8a0f-92dd-4a22-cd05c785c178@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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
all inboxes | Powered by JetHome®