From: Krzysztof Kozlowski <krzk@kernel.org>
To: Artur Weber <aweber.kernel@gmail.com>,
Chanwoo Choi <cw00.choi@samsung.com>
Cc: 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,
Henrik Grimler <henrik@grimler.se>,
Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>,
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Subject: Re: [PATCH v4 07/10] power: supply: max77693: Set up charge/input current according to cable type
Date: Fri, 16 Aug 2024 12:02:22 +0200 [thread overview]
Message-ID: <5767d188-2b99-4c21-b824-5135cc52b511@kernel.org> (raw)
In-Reply-To: <20240816-max77693-charger-extcon-v4-7-050a0a9bfea0@gmail.com>
On 16/08/2024 10:19, Artur Weber wrote:
> This behavior was observed on a downstream kernel - for chargers, the
> current would be set to a fast charge current value, and it would be
> bumped down for all other cable types.
>
> If we leave only the fast charge current value applied, peripheral mode
> stops working. If we stick to 500mA, charging becomes too slow. So, set
> the charge input current limit accordingly to the cable type.
>
> Tested-by: Henrik Grimler <henrik@grimler.se>
> Signed-off-by: Artur Weber <aweber.kernel@gmail.com>
> ---
> Changes in v3:
> - Re-introduced this commit from v1. It seems to have been accidentally
> rolled into the previous commit in v2.
> ---
> drivers/power/supply/max77693_charger.c | 23 ++++++++++++++++++++---
> 1 file changed, 20 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/power/supply/max77693_charger.c b/drivers/power/supply/max77693_charger.c
> index bf156544fe1b..908fd2a178ee 100644
> --- a/drivers/power/supply/max77693_charger.c
> +++ b/drivers/power/supply/max77693_charger.c
> @@ -716,6 +716,7 @@ static void max77693_charger_extcon_work(struct work_struct *work)
> cable.work);
> struct extcon_dev *edev = chg->cable.edev;
> bool set_charging, set_otg;
> + unsigned int input_current;
> int connector, state;
> int ret;
>
> @@ -728,19 +729,28 @@ static void max77693_charger_extcon_work(struct work_struct *work)
>
> switch (connector) {
> case EXTCON_CHG_USB_SDP:
> - case EXTCON_CHG_USB_DCP:
Why do you move it? Wasn't it added in previous patch?
> case EXTCON_CHG_USB_CDP:
> + case EXTCON_CHG_USB_SLOW:
> + input_current = 500000; /* 500 mA */
> + set_charging = true;
> + set_otg = false;
> +
> + dev_info(chg->dev, "slow charging. connector type: %d\n",
> + connector);
> + break;
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-16 10:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 8:19 [PATCH v4 00/10] power: supply: max77693: Toggle charging/OTG based on extcon status Artur Weber
2024-08-16 8:19 ` [PATCH v4 01/10] dt-bindings: power: supply: max77693: Add monitored-battery property Artur Weber
2024-08-16 8:19 ` [PATCH v4 02/10] dt-bindings: power: supply: max77693: Add maxim,usb-connector property Artur Weber
2024-08-16 8:19 ` [PATCH v4 03/10] power: supply: max77693: Expose input current limit and CC current properties Artur Weber
2024-08-16 9:49 ` Krzysztof Kozlowski
2024-08-16 8:19 ` [PATCH v4 04/10] power: supply: max77693: Set charge current limits during init Artur Weber
2024-08-16 9:54 ` Krzysztof Kozlowski
2024-08-16 14:25 ` Artur Weber
2024-08-16 15:40 ` Krzysztof Kozlowski
2024-08-27 17:14 ` Sebastian Reichel
2024-08-16 8:19 ` [PATCH v4 05/10] power: supply: max77693: Add USB extcon detection for enabling charging Artur Weber
2024-08-16 10:00 ` Krzysztof Kozlowski
2024-08-16 8:19 ` [PATCH v4 06/10] power: supply: max77693: Add support for detecting and enabling OTG Artur Weber
2024-08-16 10:00 ` Krzysztof Kozlowski
2024-08-16 8:19 ` [PATCH v4 07/10] power: supply: max77693: Set up charge/input current according to cable type Artur Weber
2024-08-16 10:02 ` Krzysztof Kozlowski [this message]
2024-08-16 8:19 ` [PATCH v4 08/10] ARM: dts: samsung: exynos4212-tab3: Add battery node with charge current value Artur Weber
2024-08-16 10:03 ` Krzysztof Kozlowski
2024-08-27 16:51 ` Sebastian Reichel
2024-08-16 8:19 ` [PATCH v4 09/10] ARM: dts: samsung: exynos4212-tab3: Add USB connector node Artur Weber
2024-08-16 8:19 ` [PATCH v4 10/10] ARM: dts: samsung: exynos4212-tab3: Drop CHARGER regulator Artur Weber
2024-08-16 10:04 ` Krzysztof Kozlowski
2024-08-27 16:58 ` (subset) [PATCH v4 00/10] power: supply: max77693: Toggle charging/OTG based on extcon status 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=5767d188-2b99-4c21-b824-5135cc52b511@kernel.org \
--to=krzk@kernel.org \
--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=henrik@grimler.se \
--cc=krzk+dt@kernel.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
all inboxes | Powered by JetHome®