From: Svyatoslav Ryhel <clamor95@gmail.com>
To: Iskren Chernev <me@iskren.info>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Matheus Castello <matheus@castello.eng.br>,
Sebastian Reichel <sre@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Alim Akhtar <alim.akhtar@samsung.com>,
Arnd Bergmann <arnd@arndb.de>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Svyatoslav Ryhel <clamor95@gmail.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Stefan Hansson <newbie13xd@gmail.com>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: [PATCH v3 0/4] Add optional properties to MAX17040
Date: Mon, 31 Jul 2023 10:36:09 +0300 [thread overview]
Message-ID: <20230731073613.10394-1-clamor95@gmail.com> (raw)
Extend properties supported by max17040 fuel gauge if it is accompanied
by different devices.
If max17040 is coupled with a charger, pass charger status since it should
match and max17040 has no dedicated status detection ability.
max17040_get_online can be reused for PRESENT property since if it is
online it must be present.
Finally, max17040 may be coupled with a dedicated thermal sensor which
monitors battery temperature so lets add support for iio channel to match
hw setup. With that said, the driver got dependency on CONFIG_IIO which
was added to Kconfig. All defconfigs apart s5pv210_defconfig have IIO
already enabled so only s5pv210_defconfig needed adjustment.
---
Changes from v2:
- documentation: fixed typo i2c0 > i2c
- added dependency on CONFIG_IIO
- enabled CONFIG_IIO for s5pv210_defconfig to avoid regressions (all other
defconfigs which include max17040 already have IIO enabled)
Changes from v1:
- documentation: dropped monitored-battery and power-supplies (inherited
from inclusion)
- dropped passing charger health as battery health
- dropped patch for simple battery cell support
- switched iio_read_channel_raw to iio_read_channel_processed_scale
- switched iio_channel_get to devm_iio_channel_get
- re-organized implementation of temp channel (implemented in way
*_get_optional functions usually act)
---
Svyatoslav Ryhel (4):
dt-bindings: power: supply: maxim,max17040: update properties
power: max17040: pass status property from supplier
power: max17040: get thermal data from adc if available
ARM: configs: s5pv210_defconfig: enable IIO required by MAX17040
.../bindings/power/supply/maxim,max17040.yaml | 31 +++++++++++++++++++
arch/arm/configs/s5pv210_defconfig | 1 +
drivers/power/supply/Kconfig | 2 +-
drivers/power/supply/max17040_battery.c | 27 ++++++++++++++++
4 files changed, 60 insertions(+), 1 deletion(-)
--
2.39.2
next reply other threads:[~2023-07-31 7:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 7:36 Svyatoslav Ryhel [this message]
2023-07-31 7:36 ` [PATCH v3 1/4] dt-bindings: power: supply: maxim,max17040: update properties Svyatoslav Ryhel
2023-07-31 7:36 ` [PATCH v3 2/4] power: max17040: pass status property from supplier Svyatoslav Ryhel
2023-07-31 7:36 ` [PATCH v3 3/4] power: max17040: get thermal data from adc if available Svyatoslav Ryhel
2023-07-31 7:36 ` [PATCH v3 4/4] ARM: configs: s5pv210_defconfig: enable IIO required by MAX17040 Svyatoslav Ryhel
2023-08-05 22:42 ` Andi Shyti
2023-08-06 8:29 ` Krzysztof Kozlowski
2023-08-07 8:55 ` Andi Shyti
2023-08-07 13:51 ` Krzysztof Kozlowski
2023-09-11 11:39 ` (subset) " Krzysztof Kozlowski
2023-07-31 15:49 ` [PATCH v3 0/4] Add optional properties to MAX17040 Iskren Chernev
2023-09-14 15:42 ` (subset) " 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=20230731073613.10394-1-clamor95@gmail.com \
--to=clamor95@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@microchip.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=matheus@castello.eng.br \
--cc=me@iskren.info \
--cc=newbie13xd@gmail.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).