From: Henrik Grimler <henrik@grimler.se>
To: Artur Weber <aweber.kernel@gmail.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Sebastian Reichel <sre@kernel.org>, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
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,
~postmarketos/upstreaming@lists.sr.ht,
Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>,
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3 00/10] power: supply: max77693: Toggle charging/OTG based on extcon status
Date: Thu, 1 Aug 2024 08:22:53 +0200 [thread overview]
Message-ID: <20240801062253.GA2681@l14.localdomain> (raw)
In-Reply-To: <20240729-max77693-charger-extcon-v3-0-02315a6869d4@gmail.com>
Hi Artur,
On Mon, Jul 29, 2024 at 07:47:34PM +0200, Artur Weber wrote:
> This patchset does the following:
>
> - Add CURRENT_MAX and INPUT_CURRENT_MAX power supply properties to
> expose the "fast charge current" (maximum current from charger to
> battery) and "CHGIN input current limit" (maximum current from
> external supply to charger).
>
> - Add functions for toggling charging and OTG modes.
>
> - Add an extcon-based handler that enables charging or OTG depending
> on the cable type plugged in. The extcon device to use for cable
> detection can be specified in the device tree, and is entirely
> optional.
>
> The extcon listener implementation is inspired by the rt5033 charger
> driver (commit 8242336dc8a8 ("power: supply: rt5033_charger: Add cable
> detection and USB OTG supply")).
Tested on exynos4412-i9305 (after applying the changes in patch 8 - 10
to exynos4412-midas.dtsi). It works well, device correctly identifies
a usb cable connected to charger or a usb cable connected to computer,
and sets a limit of 1.8 A and 0.5 A in the two cases.
I did notice that device does not always detect cable insertion, so I
can occassionally get two de-attach events in a row. Cable was
inserted between 428 and 462 in below log snippet:
[ 389.458399] max77693-muic max77693-muic: external connector is attached(chg_type:0x3, prev_chg_type:0x3)
[ 389.469765] max77693-charger max77693-charger: fast charging. connector type: 6
[ 428.151857] max77693-muic max77693-muic: external connector is detached(chg_type:0x3, prev_chg_type:0x0)
[ 428.160319] max77693-charger max77693-charger: not charging. connector type: 13
[ 462.156048] max77693-muic max77693-muic: external connector is detached(chg_type:0x0, prev_chg_type:0x0)
[ 469.881925] max77693-muic max77693-muic: external connector is attached(chg_type:0x3, prev_chg_type:0x3)
[ 469.890049] max77693-charger max77693-charger: fast charging. connector type: 6
but this is probably an issue in extcon driver though rather than
charger.
I have not tested so that MHL still works, as I do not have access to
that cable at the moment, will try it in a few days.
Best regards
Henrik Grimler
> Signed-off-by: Artur Weber <aweber.kernel@gmail.com>
>
> v3 no longer uses the CHARGER regulator to manage the power status, and
> that's for two reasons:
>
> - Regulator enable/disable behavior was interfering with how the power
> supply driver worked (we occasionally got "unbalanced disables"
> errors when switching charging state, despite checking for the
> regulator status with regulator_is_enabled() - the CHARGER reg would
> report as enabled despite the enable count being 0).
> This broke OTG insertion if the OTG cable was plugged in first, and
> sometimes caused warnings on unsuspend.
>
> - Changing the charging values directly in the power supply driver is
> less opaque and lets us avoid bringing in a dependency on regulators.
>
> It also splits the current limits back into two properties:
> INPUT_CURRENT_LIMIT and CONSTANT_CHARGE_CURRENT_MAX. Again, there are
> two reasons for this split:
>
> - They are two separate current controls, one for USB->charger and one
> for charger->battery, and they have different limits (0-2.1A for CC
> vs 60mA-2.58A for input). Given that the power supply core has the
> properties for both values separately, it's more logical to present
> them as such.
>
> - It's safer to keep these separate; CONSTANT_CHARGE_CURRENT_MAX is
> pretty explicitly only set *once* - at probe time with a safe value
> specified in the DT. This way, INPUT_CURRENT_LIMIT is safer to modify
> since in the event of an invalid value the CC current will hold back
> the extra current thus preventing damage to the battery.
>
> The latter is relevant as I'm working on a follow-up patchset that
> allows for controlling the charging parameters using power supply
> properties/sysfs properties rather than the CHARGER regulator.
>
> Note that the CHARGER regulator gets disabled automatically if it's
> not used, which will disable charging if it was auto-enabled by the
> extcon code. This can be worked around by re-attaching the cable, or
> more properly by removing the CHARGER regulator from DT for devices
> that use the extcon-based charger management, as has been done in the
> Galaxy Tab 3 8.0 DTSI.
>
> See v1 for old description:
>
> https://lore.kernel.org/r/20240530-max77693-charger-extcon-v1-0-dc2a9e5bdf30@gmail.com
> ---
> Changes in v3:
> - Drop uses of CHARGER regulator, manage registers directly in power
> supply driver instead
> - Link to v2: https://lore.kernel.org/r/20240715-max77693-charger-extcon-v2-0-0838ffbb18c3@gmail.com
>
> Changes in v2:
> - Changed to use monitored-battery for charge current value
> - Both current limit variables are now set by the CHARGER regulator
> - Link to v1: https://lore.kernel.org/r/20240530-max77693-charger-extcon-v1-0-dc2a9e5bdf30@gmail.com
>
> ---
> Artur Weber (10):
> dt-bindings: power: supply: max77693: Add monitored-battery property
> dt-bindings: power: supply: max77693: Add maxim,usb-connector property
> power: supply: max77693: Expose input current limit and CC current properties
> power: supply: max77693: Set charge current limits during init
> power: supply: max77693: Add USB extcon detection for enabling charging
> power: supply: max77693: Add support for detecting and enabling OTG
> power: supply: max77693: Set up charge/input current according to cable type
> ARM: dts: samsung: exynos4212-tab3: Add battery node with charge current value
> ARM: dts: samsung: exynos4212-tab3: Add USB connector node
> ARM: dts: exynos4212-tab3: Drop CHARGER regulator
>
> .../bindings/power/supply/maxim,max77693.yaml | 15 +
> arch/arm/boot/dts/samsung/exynos4212-tab3.dtsi | 22 +-
> drivers/power/supply/Kconfig | 1 +
> drivers/power/supply/max77693_charger.c | 302 ++++++++++++++++++++-
> include/linux/mfd/max77693-private.h | 12 +
> 5 files changed, 337 insertions(+), 15 deletions(-)
> ---
> base-commit: 0c3836482481200ead7b416ca80c68a29cfdaabd
> change-id: 20240525-max77693-charger-extcon-9ebb7bad83ce
>
> Best regards,
> --
> Artur Weber <aweber.kernel@gmail.com>
>
next prev parent reply other threads:[~2024-08-01 6:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 17:47 [PATCH v3 00/10] power: supply: max77693: Toggle charging/OTG based on extcon status Artur Weber
2024-07-29 17:47 ` [PATCH v3 01/10] dt-bindings: power: supply: max77693: Add monitored-battery property Artur Weber
2024-07-29 17:47 ` [PATCH v3 02/10] dt-bindings: power: supply: max77693: Add maxim,usb-connector property Artur Weber
2024-07-29 17:47 ` [PATCH v3 03/10] power: supply: max77693: Expose input current limit and CC current properties Artur Weber
2024-07-29 17:47 ` [PATCH v3 04/10] power: supply: max77693: Set charge current limits during init Artur Weber
2024-07-29 17:47 ` [PATCH v3 05/10] power: supply: max77693: Add USB extcon detection for enabling charging Artur Weber
2024-07-29 17:47 ` [PATCH v3 06/10] power: supply: max77693: Add support for detecting and enabling OTG Artur Weber
2024-07-29 17:47 ` [PATCH v3 07/10] power: supply: max77693: Set up charge/input current according to cable type Artur Weber
2024-07-29 17:47 ` [PATCH v3 08/10] ARM: dts: samsung: exynos4212-tab3: Add battery node with charge current value Artur Weber
2024-09-28 12:54 ` Krzysztof Kozlowski
2024-07-29 17:47 ` [PATCH v3 09/10] ARM: dts: samsung: exynos4212-tab3: Add USB connector node Artur Weber
2024-07-29 17:47 ` [PATCH v3 10/10] ARM: dts: exynos4212-tab3: Drop CHARGER regulator Artur Weber
2024-08-01 6:22 ` Henrik Grimler [this message]
2024-08-04 10:59 ` [PATCH v3 00/10] power: supply: max77693: Toggle charging/OTG based on extcon status Henrik Grimler
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=20240801062253.GA2681@l14.localdomain \
--to=henrik@grimler.se \
--cc=GNUtoo@cyberdimension.org \
--cc=alim.akhtar@samsung.com \
--cc=aweber.kernel@gmail.com \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.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=robh@kernel.org \
--cc=sre@kernel.org \
--cc=wolfgit@wiedmeyer.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox