mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 04/10] power: supply: max77693: Set charge current limits during init
Date: Fri, 16 Aug 2024 11:54:55 +0200	[thread overview]
Message-ID: <9dbaacdb-5f9c-48d4-a56a-a19ca8809344@kernel.org> (raw)
In-Reply-To: <20240816-max77693-charger-extcon-v4-4-050a0a9bfea0@gmail.com>

On 16/08/2024 10:19, Artur Weber wrote:
> There are two charger current limit registers:
> 
> - Fast charge current limit (which controls current going from the
>   charger to the battery);
> - CHGIN input current limit (which controls current going into the
>   charger through the cable).
> 
> Add functions for setting both of the values, and set them to a
> safe default value of 500mA at initialization.
> 
> The value for the fast charge current limit can be modified by setting
> the constant-charge-current-max-ua DT property of the battery node
> specified in the monitored-battery charger DT property; the CHGIN input
> current limit will be set up later in the charger detection mechanism
> (in the future, the INPUT_CURRENT_LIMIT property could also be made
> writeable for userspace control of the current limit, while keeping
> the actual current limit from the charger to the battery intact
> so that users don't accidentally blow up their batteries with a bad
> value).
> 
> Acked-by: Lee Jones <lee@kernel.org>
> Tested-by: Henrik Grimler <henrik@grimler.se>
> Signed-off-by: Artur Weber <aweber.kernel@gmail.com>
> ---
> Changes in v3:
> - Dropped CHARGER reg in favor of managing the registers directly
> 
> Changes in v2:
> - Squashed mfd include register additions into this commit
> - Changed from custom fast charge current property to monitored-battery
>   (devm_power_supply_register call has been moved up as it is needed by
>   the DT init function now)
> - Changed to adapt to both current limit values being managed by the
>   CHARGER regulator
> ---
>  drivers/power/supply/max77693_charger.c | 82 ++++++++++++++++++++++++++++-----
>  include/linux/mfd/max77693-private.h    |  2 +
>  2 files changed, 73 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/power/supply/max77693_charger.c b/drivers/power/supply/max77693_charger.c
> index 4caac142c428..17975ec69a6a 100644
> --- a/drivers/power/supply/max77693_charger.c
> +++ b/drivers/power/supply/max77693_charger.c
> @@ -26,6 +26,7 @@ struct max77693_charger {
>  	u32 min_system_volt;
>  	u32 thermal_regulation_temp;
>  	u32 batttery_overcurrent;
> +	u32 fast_charge_current;
>  	u32 charge_input_threshold_volt;
>  };
>  
> @@ -596,6 +597,48 @@ static int max77693_set_batttery_overcurrent(struct max77693_charger *chg,
>  			CHG_CNFG_12_B2SOVRC_MASK, data);
>  }
>  
> +static int max77693_set_input_current_limit(struct max77693_charger *chg,
> +		unsigned int uamp)
> +{
> +	unsigned int data;
> +
> +	if (uamp < 60000 || uamp > 2540000) {
> +		dev_err(chg->dev, "Wrong value for input current limit");
> +		return -EINVAL;
> +	};
> +
> +	data = uamp / 20000; /* 20mA steps */
> +
> +	data <<= CHG_CNFG_09_CHGIN_ILIM_SHIFT;
> +
> +	dev_dbg(chg->dev, "Input current limit: %u (0x%x)\n", uamp, data);
> +
> +	return regmap_update_bits(chg->max77693->regmap,
> +			MAX77693_CHG_REG_CHG_CNFG_09,
> +			CHG_CNFG_09_CHGIN_ILIM_MASK, data);
> +}
> +
> +static int max77693_set_fast_charge_current(struct max77693_charger *chg,
> +		unsigned int uamp)
> +{
> +	unsigned int data;
> +
> +	if (uamp > 2100000) {
> +		dev_err(chg->dev, "Wrong value for fast charge current\n");
> +		return -EINVAL;
> +	}
> +
> +	data = uamp / 33300; /* 0.1A/3 steps */
> +
> +	data <<= CHG_CNFG_02_CC_SHIFT;
> +
> +	dev_dbg(chg->dev, "Fast charge current: %u (0x%x)\n", uamp, data);
> +
> +	return regmap_update_bits(chg->max77693->regmap,
> +			MAX77693_CHG_REG_CHG_CNFG_02,
> +			CHG_CNFG_02_CC_MASK, data);
> +}
> +
>  static int max77693_set_charge_input_threshold_volt(struct max77693_charger *chg,
>  		unsigned int uvolt)
>  {
> @@ -673,6 +716,15 @@ static int max77693_reg_init(struct max77693_charger *chg)
>  	if (ret)
>  		return ret;
>  
> +	ret = max77693_set_fast_charge_current(chg, chg->fast_charge_current);
> +	if (ret)
> +		return ret;
> +
> +	ret = max77693_set_input_current_limit(chg,
> +				DEFAULT_FAST_CHARGE_CURRENT);
> +	if (ret)
> +		return ret;
> +
>  	return max77693_set_charge_input_threshold_volt(chg,
>  			chg->charge_input_threshold_volt);
>  }
> @@ -681,6 +733,7 @@ static int max77693_reg_init(struct max77693_charger *chg)
>  static int max77693_dt_init(struct device *dev, struct max77693_charger *chg)
>  {
>  	struct device_node *np = dev->of_node;
> +	struct power_supply_battery_info *battery_info;
>  
>  	if (!np) {
>  		dev_err(dev, "no charger OF node\n");
> @@ -708,11 +761,20 @@ static int max77693_dt_init(struct device *dev, struct max77693_charger *chg)
>  		chg->charge_input_threshold_volt =
>  			DEFAULT_CHARGER_INPUT_THRESHOLD_VOLT;
>  
> +	if (power_supply_get_battery_info(chg->charger, &battery_info) ||
> +			!battery_info->constant_charge_current_max_ua)
> +		chg->fast_charge_current = DEFAULT_FAST_CHARGE_CURRENT;
> +	else
> +		chg->fast_charge_current =
> +			battery_info->constant_charge_current_max_ua;
> +
>  	return 0;
>  }
>  #else /* CONFIG_OF */
>  static int max77693_dt_init(struct device *dev, struct max77693_charger *chg)
>  {
> +	chg->fast_charge_current = DEFAULT_FAST_CHARGE_CURRENT;
> +
>  	return 0;
>  }
>  #endif /* CONFIG_OF */
> @@ -732,6 +794,15 @@ static int max77693_charger_probe(struct platform_device *pdev)
>  	chg->dev = &pdev->dev;
>  	chg->max77693 = max77693;
>  
> +	psy_cfg.drv_data = chg;
> +
> +	chg->charger = devm_power_supply_register(&pdev->dev,
> +						  &max77693_charger_desc,
> +						  &psy_cfg);
> +	if (IS_ERR(chg->charger))
> +		return dev_err_probe(&pdev->dev, PTR_ERR(chg->charger),
> +				     "failed: power supply register\n");

This code move is not explained in the commit msg. At least I could not
find it. Please explain why you need it in the commit msg.

BTW, if you are interested in devices using this driver, have time, in
general care about the code and want to respond to patches, feel free to
add yourself to driver's maintainer entry.



Best regards,
Krzysztof


  reply	other threads:[~2024-08-16  9:55 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 [this message]
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
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=9dbaacdb-5f9c-48d4-a56a-a19ca8809344@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®