devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matheus Castello <matheus@castello.eng.br>
To: sre@kernel.org, krzk@kernel.org, robh+dt@kernel.org
Cc: mark.rutland@arm.com, cw00.choi@samsung.com,
	b.zolnierkie@samsung.com, lee.jones@linaro.org,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Matheus Castello <matheus@castello.eng.br>
Subject: [PATCH v8 0/5] power: supply: MAX17040: Add IRQ for low level and alert SOC changes
Date: Thu,  5 Dec 2019 12:44:05 -0300	[thread overview]
Message-ID: <20191205154410.29462-1-matheus@castello.eng.br> (raw)

This series add IRQ handler for low level SOC alert, define a devicetree
binding attribute to configure the alert level threshold and check for
changes in SOC and power supply status for send uevents.

Max17043/17044 have a pin for alert host about low level state of charge and
this alert can be configured in a threshold from 1% up to 32% of SOC.

Thanks Krzysztof Kozlowski, Lee Jones, Rob Herring and Sebastian Reichel for
your time reviewing it.

Changes since v7:
(Suggested by Sebastian Reichel)
- Fix unrelated change
- Use device_property_read_u32() and simplify the code
- Check the irq and of_device_is_compatible in the first patch

Changes since v6:
(Suggested by Lee Jones)
- Use relative paths in documentation

Matheus Castello (5):
  power: supply: max17040: Add IRQ handler for low SOC alert
  dt-bindings: power: supply: Max17040: Add DT bindings for max17040
    fuel gauge
  devicetree: mfd: max14577: Add reference to max14040_battery.txt
    descriptions
  power: supply: max17040: Config alert SOC low level threshold from FDT
  power: supply: max17040: Send uevent in SOC and status change

 .../devicetree/bindings/mfd/max14577.txt      |   2 +
 .../power/supply/max17040_battery.txt         |  33 +++++
 drivers/power/supply/max17040_battery.c       | 130 +++++++++++++++++-
 3 files changed, 161 insertions(+), 4 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/power/supply/max17040_battery.txt

--
2.24.0.rc2


             reply	other threads:[~2019-12-05 16:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 15:44 Matheus Castello [this message]
2019-12-05 15:44 ` [PATCH v8 1/5] power: supply: max17040: Add IRQ handler for low SOC alert Matheus Castello
2019-12-05 15:44 ` [PATCH v8 2/5] dt-bindings: power: supply: Max17040: Add DT bindings for max17040 fuel gauge Matheus Castello
2019-12-05 15:44 ` [PATCH v8 3/5] devicetree: mfd: max14577: Add reference to max14040_battery.txt descriptions Matheus Castello
2019-12-06  9:16   ` Krzysztof Kozlowski
2019-12-16 10:47   ` Lee Jones
2019-12-05 15:44 ` [PATCH v8 4/5] power: supply: max17040: Config alert SOC low level threshold from FDT Matheus Castello
2019-12-06  9:17   ` Krzysztof Kozlowski
2019-12-05 15:44 ` [PATCH v8 5/5] power: supply: max17040: Send uevent in SOC and status change Matheus Castello
2019-12-19  0:52 ` [PATCH v8 0/5] power: supply: MAX17040: Add IRQ for low level and alert SOC changes Sebastian Reichel

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=20191205154410.29462-1-matheus@castello.eng.br \
    --to=matheus@castello.eng.br \
    --cc=b.zolnierkie@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).