All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Reichel <sre@kernel.org>
To: Iskren Chernev <iskren.chernev@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	Jonathan Bakker <xc-racer2@live.ca>,
	Vladimir Barinov <vladimir.barinov@cogentembedded.com>
Subject: Re: [PATCH v5 0/7] power: supply: max17040 support compatible devices
Date: Sat, 3 Oct 2020 21:12:29 +0200	[thread overview]
Message-ID: <20201003191229.dmxov4itycdhs4hy@earth.universe> (raw)
In-Reply-To: <20200922114237.1803628-1-iskren.chernev@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]

Hi,

On Tue, Sep 22, 2020 at 02:42:30PM +0300, Iskren Chernev wrote:
> The max17040 fuel gauge is part of a family of 8 chips that have very
> similar mode of operations and registers.
> 
> This patch set adds:
> - compatible strings for all supported devices and handles the minor
>   differences between them;
> - handling for devices reporting double capacity via maxim,double-soc;
> - handling for setting rcomp, a compensation value for more accurate
>   reading, affected by battery chemistry and operating temps;
> - suppot for SOC alerts (capacity changes by +/- 1%), to prevent polling
>   every second;
> - improved max17040 driver with regmap and devm_
> 
> The datasheets of the supported devices are linked [0] [1] [2] [3].
> 
> [0] https://datasheets.maximintegrated.com/en/ds/MAX17040-MAX17041.pdf
> [1] https://datasheets.maximintegrated.com/en/ds/MAX17043-MAX17044.pdf
> [2] https://datasheets.maximintegrated.com/en/ds/MAX17048-MAX17049.pdf
> [3] https://datasheets.maximintegrated.com/en/ds/MAX17058-MAX17059.pdf
> 
> v4: https://lkml.org/lkml/2020/9/6/237
> v3: https://lkml.org/lkml/2020/6/24/874
> v2: https://lkml.org/lkml/2020/6/18/260
> v1: https://lkml.org/lkml/2020/6/8/682
> 
> Changes from v4:
> - fix warning reported by kernel test robot <lkp@intel.com> for v4
>   patch 4/7
> - ensure all patches have Sign-off-by matching author (was violated
>   for v4 patch 2/7)

Thanks, queued.

-- Sebastian

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2020-10-03 19:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 11:42 [PATCH v5 0/7] power: supply: max17040 support compatible devices Iskren Chernev
2020-09-22 11:42 ` [PATCH v5 1/7] power: supply: max17040: Use devm_ to automate remove Iskren Chernev
2020-09-22 11:42 ` [PATCH v5 2/7] power: supply: max17040: Use regmap i2c Iskren Chernev
2020-09-22 11:42 ` [PATCH v5 3/7] dt-bindings: power: supply: Extend max17040 compatibility Iskren Chernev
2020-09-22 11:42 ` [PATCH v5 4/7] power: supply: max17040: Support compatible devices Iskren Chernev
2020-09-22 11:42 ` [PATCH v5 5/7] dt-bindings: power: supply: max17040: Add maxim,rcomp Iskren Chernev
2020-09-22 11:42 ` [PATCH v5 6/7] power: supply: max17040: Support setting rcomp Iskren Chernev
2020-09-22 11:42 ` [PATCH v5 7/7] power: supply: max17040: Support soc alert Iskren Chernev
2020-10-03 19:12 ` Sebastian Reichel [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=20201003191229.dmxov4itycdhs4hy@earth.universe \
    --to=sre@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=iskren.chernev@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=vladimir.barinov@cogentembedded.com \
    --cc=xc-racer2@live.ca \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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.