public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: khilman@baylibre.com, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org, Sebastian Reichel <sre@kernel.org>,
	Rob Herring <robh@kernel.org>,
	devicetree@vger.kernel.org, Lee Jones <lee@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	tony@atomide.com, linux-omap@vger.kernel.org
Cc: Andreas Kemnade <andreas@kemnade.info>
Subject: [PATCH v5 0/3] power: supply: twl6030/32 charger
Date: Wed, 16 Oct 2024 10:03:11 +0200	[thread overview]
Message-ID: <20241016080314.222674-1-andreas@kemnade.info> (raw)

Add basic support for the charger in the TWL6030/32. Supported is the USB
path. AC path is not handled yet, also there is no entry yet
in /sys/class/power_supply with type battery yet.

Without this series, devices will happily drain battery when running
on mainline.

Changes in v5:
- set fwnode
- drop mfd patch as it is already applied

Changes in v4:
- require compatible in charger node

Changes in v3:
- define charger in toplevel
- s/bci/charger for twl4030

Changes in v2:
- s/bci/charger in mfd schema
- additionalProperties for charger node
- extended example in mfd schema
- no quotes for compatibles in charger schema
- no example in charger schema
- interrupt description in charger schema
- replace device_is_compatible by driver data
- clang compile fix
- removed alias
- style fixes

Andreas Kemnade (3):
  dt-bindings: power: supply: Add TI TWL603X charger
  power: supply: initial support for TWL6030/32
  ARM: dts: ti/omap: use standard node name for twl4030 charger

 .../power/supply/ti,twl6030-charger.yaml      |  48 ++
 arch/arm/boot/dts/ti/omap/twl4030.dtsi        |   2 +-
 drivers/power/supply/Kconfig                  |  10 +
 drivers/power/supply/Makefile                 |   1 +
 drivers/power/supply/twl6030_charger.c        | 581 ++++++++++++++++++
 5 files changed, 641 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/devicetree/bindings/power/supply/ti,twl6030-charger.yaml
 create mode 100644 drivers/power/supply/twl6030_charger.c

-- 
2.39.2


             reply	other threads:[~2024-10-16  8:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16  8:03 Andreas Kemnade [this message]
2024-10-16  8:03 ` [PATCH v5 1/3] dt-bindings: power: supply: Add TI TWL603X charger Andreas Kemnade
2024-10-16  8:03 ` [PATCH v5 2/3] power: supply: initial support for TWL6030/32 Andreas Kemnade
2024-10-16  8:03 ` [PATCH v5 3/3] ARM: dts: ti/omap: use standard node name for twl4030 charger Andreas Kemnade
2024-10-29 23:42   ` Kevin Hilman
2024-10-16 21:41 ` (subset) [PATCH v5 0/3] power: supply: twl6030/32 charger 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=20241016080314.222674-1-andreas@kemnade.info \
    --to=andreas@kemnade.info \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sre@kernel.org \
    --cc=tony@atomide.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