From: Svyatoslav Ryhel <clamor95@gmail.com>
To: "Sebastian Reichel" <sre@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Aradhya Bhatia" <a-bhatia1@ti.com>,
"Svyatoslav Ryhel" <clamor95@gmail.com>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: [PATCH v3 0/4] power: supply: add support for Pegatron Chagall battery
Date: Tue, 29 Apr 2025 09:17:58 +0300 [thread overview]
Message-ID: <20250429061803.9581-1-clamor95@gmail.com> (raw)
The Pegatron Chagall is an Android tablet utilizing a customized Cypress
CG7153AM microcontroller (MCU) as its battery fuel gauge. It supports a
single-cell battery and features a dual-color charging LED.
---
Changes in v3:
- status update handled via default-trigger
- chagall_battery_prop_offs sorted by chagall_battery_properties
- separated status logic into chagall_battery_get_status helper
- removed controversial POWER_SUPPLY_STATUS_NOT_CHARGING use
- code formatting improvemets
Changes in v2:
- removed CG7153AM mentions in code, documentation and commit messages
- moved schema to power/supply
- left only pegatron,chagall compatible, other is dropped
---
Svyatoslav Ryhel (4):
dt-bindings: vendor-prefixes: add prefix for Pegatron Corporation
dt-bindings: power: supply: Document Pegatron Chagall fuel gauge
power: supply: Add driver for Pegatron Chagall battery
ARM: tegra: chagall: Add embedded controller node
.../power/supply/pegatron,chagall-ec.yaml | 49 +++
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
.../dts/nvidia/tegra30-pegatron-chagall.dts | 16 +
drivers/power/supply/Kconfig | 12 +
drivers/power/supply/Makefile | 1 +
drivers/power/supply/chagall-battery.c | 291 ++++++++++++++++++
6 files changed, 371 insertions(+)
create mode 100644 Documentation/devicetree/bindings/power/supply/pegatron,chagall-ec.yaml
create mode 100644 drivers/power/supply/chagall-battery.c
--
2.48.1
next reply other threads:[~2025-04-29 6:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 6:17 Svyatoslav Ryhel [this message]
2025-04-29 6:17 ` [PATCH v3 1/4] dt-bindings: vendor-prefixes: add prefix for Pegatron Corporation Svyatoslav Ryhel
2025-04-29 6:18 ` [PATCH v3 2/4] dt-bindings: power: supply: Document Pegatron Chagall fuel gauge Svyatoslav Ryhel
2025-04-29 6:18 ` [PATCH v3 3/4] power: supply: Add driver for Pegatron Chagall battery Svyatoslav Ryhel
2025-04-29 22:05 ` Sebastian Reichel
2025-04-30 5:38 ` Svyatoslav Ryhel
2025-04-29 6:18 ` [PATCH v3 4/4] ARM: tegra: chagall: Add embedded controller node Svyatoslav Ryhel
2025-04-29 22:04 ` (subset) [PATCH v3 0/4] power: supply: add support for Pegatron Chagall battery Sebastian Reichel
2025-07-11 15:11 ` Thierry Reding
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=20250429061803.9581-1-clamor95@gmail.com \
--to=clamor95@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=a-bhatia1@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=thierry.reding@gmail.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