mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: Rob Herring <robh@kernel.org>
Cc: sre@kernel.org, devicetree@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: power/supply: Add ltc4162-l-charger
Date: Mon, 26 Oct 2020 16:08:02 +0100	[thread overview]
Message-ID: <5fd054f4-cb7b-7b2f-4827-a8171b6d54d1@topic.nl> (raw)
In-Reply-To: <20201026144331.GA123160@bogus>


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 26-10-2020 15:43, Rob Herring wrote:
> On Wed, Oct 21, 2020 at 04:10:30PM +0200, 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.
>>
>> This adds the devicetree bindings.
>>
>> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
>> ---
>>   .../bindings/power/supply/ltc4162-l.yaml      | 60 +++++++++++++++++++
>>   1 file changed, 60 insertions(+)
>>   create mode 100644 Documentation/devicetree/bindings/power/supply/ltc4162-l.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/power/supply/ltc4162-l.yaml b/Documentation/devicetree/bindings/power/supply/ltc4162-l.yaml
>> new file mode 100644
>> index 000000000000..a23dd6f3fae0
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/power/supply/ltc4162-l.yaml
>> @@ -0,0 +1,60 @@
>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>> +# Copyright (C) 2020 Topic Embedded Products
>> +%YAML 1.2
>> +---
>> +$id: "http://devicetree.org/schemas/power/supply/ltc4162-l.yaml#"
>> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
>> +
>> +title: Linear Technology (Analog Devices) LTC4162-L Charger
>> +
>> +maintainers:
>> +  - Mike Looijmans <mike.looijmans@topic.nl>
>> +
>> +description: |
>> +  The LTC ® 4162-L is an advanced monolithic synchronous step-down switching
>> +  battery charger and PowerPath (TM) manager that seamlessly manages power
>> +  distribution between input sources such as wall adapters, backplanes, solar
>> +  panels, etc., and a rechargeable Lithium-Ion/Polymer battery.
>> +
>> +  Specifications about the charger can be found at:
>> +    https://www.analog.com/en/products/ltc4162-s.html
>> +
>> +properties:
>> +  compatible:
>> +    enum:
>> +      - lltc,ltc4162-l
>> +
>> +  reg:
>> +    maxItems: 1
>> +    description: I2C address of the charger.
>> +
>> +  lltc,rsnsb:
>> +    $ref: /schemas/types.yaml#/definitions/uint32
>> +    description: Battery sense resistor in milli Ohm.
>> +    minimum: 1
>> +
>> +  lltc,rsnsi:
>> +    $ref: /schemas/types.yaml#/definitions/uint32
>> +    description: Input current sense resistor in milli Ohm.
>> +    minimum: 1
> These should have a unit suffix as defined in property-units.txt.
> There's not one for milli Ohms, does micro Ohms give you enough range?
> If not, you can add it though that's discouraged simply so that we don't
> have differring units in each binding for the same thing.

Micro Ohms is fine, might even be beneficial. Expected values are in the 
10 milliohm range. Sorry to have missed that. I'll adapt the driver to 
use this value without overflowing.



-- 
Mike Looijmans


      parent reply	other threads:[~2020-10-26 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 14:10 Mike Looijmans
2020-10-26 14:43 ` Rob Herring
     [not found]   ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.dc7cfc2e-6cf2-4369-b27f-f3a949d4638b@emailsignatures365.codetwo.com>
     [not found]     ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.0d2bd5fa-15cc-4b27-b94e-83614f9e5b38.a8ff2286-c81b-46a6-ad61-108358632253@emailsignatures365.codetwo.com>
2020-10-26 15:08       ` 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=5fd054f4-cb7b-7b2f-4827-a8171b6d54d1@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=robh@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

all inboxes | Powered by JetHome®