From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Andrei Stefanescu <andrei.stefanescu@microchip.com>,
Heiko Stuebner <heiko@sntech.de>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Tony Lindgren <tony@atomide.com>,
Linus Walleij <linus.walleij@linaro.org>,
Brendan Higgins <brendanhiggins@google.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Andreas Kemnade <andreas@kemnade.info>,
"Angelo G. Del Regno" <kholk11@gmail.com>,
Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>,
linux-samsung-soc@vger.kernel.org, linux-omap@vger.kernel.org,
Axel Lin <axel.lin@ingics.com>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Markus Reichl <m.reichl@fivetechno.de>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Chen-Yu Tsai <wens@csie.org>, Andy Gross <agross@kernel.org>,
markus.laine@fi.rohmeurope.com,
Adam Thomson <Adam.Thomson.Opensource@diasemi.com>,
devicetree@vger.kernel.org,
Charles Keepax <ckeepax@opensource.cirrus.com>,
mazziesaccount@gmail.com, linux-arm-msm@vger.kernel.org,
Richard Fitzgerald <rf@opensource.cirrus.com>,
Mark Brown <broonie@kernel.org>,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-arm-kernel@lists.infradead.org,
Support Opensource <support.opensource@diasemi.com>,
Baolin Wang <baolin.wang@linaro.org>,
Sangbeom Kim <sbkim73@samsung.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-pm@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, mikko.mutanen@fi.rohmeurope.com,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
patches@opensource.cirrus.com
Subject: Re: [PATCH v8 07/10] power: supply: bd70528: use linear ranges
Date: Sun, 5 Apr 2020 05:37:22 +0200 [thread overview]
Message-ID: <20200405033722.4co4bnrz5whykrrq@earth.universe> (raw)
In-Reply-To: <4a70a243cc169ddb2c2ea3a78a4550a51dadd8fd.1585902279.git.matti.vaittinen@fi.rohmeurope.com>
[-- Attachment #1.1: Type: text/plain, Size: 8395 bytes --]
Hi,
On Fri, Apr 03, 2020 at 11:47:21AM +0300, Matti Vaittinen wrote:
> Change the bd70528 to use common linear_range code instead of
> implementing a copy of it in this driver.
>
> Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> ---
Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com>
-- Sebastian
>
> No changes since v7
>
> drivers/power/supply/Kconfig | 1 +
> drivers/power/supply/bd70528-charger.c | 144 ++++++++++---------------
> 2 files changed, 56 insertions(+), 89 deletions(-)
>
> diff --git a/drivers/power/supply/Kconfig b/drivers/power/supply/Kconfig
> index 9a5591ab90d0..8781c674ed07 100644
> --- a/drivers/power/supply/Kconfig
> +++ b/drivers/power/supply/Kconfig
> @@ -695,6 +695,7 @@ config CHARGER_UCS1002
> config CHARGER_BD70528
> tristate "ROHM bd70528 charger driver"
> depends on MFD_ROHM_BD70528
> + select LINEAR_RANGES
> default n
> help
> Say Y here to enable support for getting battery status
> diff --git a/drivers/power/supply/bd70528-charger.c b/drivers/power/supply/bd70528-charger.c
> index 3b820110ecfa..7a805faeee83 100644
> --- a/drivers/power/supply/bd70528-charger.c
> +++ b/drivers/power/supply/bd70528-charger.c
> @@ -72,6 +72,7 @@
> #include <linux/module.h>
> #include <linux/platform_device.h>
> #include <linux/power_supply.h>
> +#include <linux/linear_range.h>
>
> #define CHG_STAT_SUSPEND 0x0
> #define CHG_STAT_TRICKLE 0x1
> @@ -335,38 +336,37 @@ static int bd70528_get_present(struct bd70528_psy *bdpsy, int *val)
> return 0;
> }
>
> -struct bd70528_linear_range {
> - int min;
> - int step;
> - int vals;
> - int low_sel;
> -};
> -
> -static const struct bd70528_linear_range current_limit_ranges[] = {
> +static const struct linear_range current_limit_ranges[] = {
> {
> .min = 5,
> .step = 1,
> - .vals = 36,
> - .low_sel = 0,
> + .min_sel = 0,
> + .max_sel = 0x22,
> },
> {
> .min = 40,
> .step = 5,
> - .vals = 5,
> - .low_sel = 0x23,
> + .min_sel = 0x23,
> + .max_sel = 0x26,
> },
> {
> .min = 60,
> .step = 20,
> - .vals = 8,
> - .low_sel = 0x27,
> + .min_sel = 0x27,
> + .max_sel = 0x2d,
> },
> {
> .min = 200,
> .step = 50,
> - .vals = 7,
> - .low_sel = 0x2e,
> - }
> + .min_sel = 0x2e,
> + .max_sel = 0x34,
> + },
> + {
> + .min = 500,
> + .step = 0,
> + .min_sel = 0x35,
> + .max_sel = 0x3f,
> + },
> };
>
> /*
> @@ -374,18 +374,18 @@ static const struct bd70528_linear_range current_limit_ranges[] = {
> * voltage for low temperatures. The driver currently only reads
> * the charge current at room temperature. We do set both though.
> */
> -static const struct bd70528_linear_range warm_charge_curr[] = {
> +static const struct linear_range warm_charge_curr[] = {
> {
> .min = 10,
> .step = 10,
> - .vals = 20,
> - .low_sel = 0,
> + .min_sel = 0,
> + .max_sel = 0x12
> },
> {
> .min = 200,
> .step = 25,
> - .vals = 13,
> - .low_sel = 0x13,
> + .min_sel = 0x13,
> + .max_sel = 0x1f
> },
> };
>
> @@ -398,56 +398,6 @@ static const struct bd70528_linear_range warm_charge_curr[] = {
> #define MAX_WARM_CHG_CURR_SEL 0x1f
> #define MIN_CHG_CURR_SEL 0x0
>
> -static int find_value_for_selector_low(const struct bd70528_linear_range *r,
> - int selectors, unsigned int sel,
> - unsigned int *val)
> -{
> - int i;
> -
> - for (i = 0; i < selectors; i++) {
> - if (r[i].low_sel <= sel && r[i].low_sel + r[i].vals >= sel) {
> - *val = r[i].min + (sel - r[i].low_sel) * r[i].step;
> - return 0;
> - }
> - }
> - return -EINVAL;
> -}
> -
> -/*
> - * For BD70528 voltage/current limits we happily accept any value which
> - * belongs the range. We could check if value matching the selector is
> - * desired by computing the range min + (sel - sel_low) * range step - but
> - * I guess it is enough if we use voltage/current which is closest (below)
> - * the requested?
> - */
> -static int find_selector_for_value_low(const struct bd70528_linear_range *r,
> - int selectors, unsigned int val,
> - unsigned int *sel, bool *found)
> -{
> - int i;
> - int ret = -EINVAL;
> -
> - *found = false;
> - for (i = 0; i < selectors; i++) {
> - if (r[i].min <= val) {
> - if (r[i].min + r[i].step * r[i].vals >= val) {
> - *found = true;
> - *sel = r[i].low_sel + (val - r[i].min) /
> - r[i].step;
> - ret = 0;
> - break;
> - }
> - /*
> - * If the range max is smaller than requested
> - * we can set the max supported value from range
> - */
> - *sel = r[i].low_sel + r[i].vals;
> - ret = 0;
> - }
> - }
> - return ret;
> -}
> -
> static int get_charge_current(struct bd70528_psy *bdpsy, int *ma)
> {
> unsigned int sel;
> @@ -463,9 +413,9 @@ static int get_charge_current(struct bd70528_psy *bdpsy, int *ma)
>
> sel &= BD70528_MASK_CHG_CHG_CURR;
>
> - ret = find_value_for_selector_low(&warm_charge_curr[0],
> - ARRAY_SIZE(warm_charge_curr), sel,
> - ma);
> + ret = linear_range_get_value_array(&warm_charge_curr[0],
> + ARRAY_SIZE(warm_charge_curr),
> + sel, ma);
> if (ret) {
> dev_err(bdpsy->dev,
> "Unknown charge current value 0x%x\n",
> @@ -491,10 +441,9 @@ static int get_current_limit(struct bd70528_psy *bdpsy, int *ma)
>
> sel &= BD70528_MASK_CHG_DCIN_ILIM;
>
> - ret = find_value_for_selector_low(¤t_limit_ranges[0],
> - ARRAY_SIZE(current_limit_ranges), sel,
> - ma);
> -
> + ret = linear_range_get_value_array(¤t_limit_ranges[0],
> + ARRAY_SIZE(current_limit_ranges),
> + sel, ma);
> if (ret) {
> /* Unspecified values mean 500 mA */
> *ma = 500;
> @@ -588,15 +537,28 @@ static int set_charge_current(struct bd70528_psy *bdpsy, int ma)
> goto set;
> }
>
> - ret = find_selector_for_value_low(&warm_charge_curr[0],
> - ARRAY_SIZE(warm_charge_curr), ma,
> - ®, &found);
> +/*
> + * For BD70528 voltage/current limits we happily accept any value which
> + * belongs the range. We could check if value matching the selector is
> + * desired by computing the range min + (sel - sel_low) * range step - but
> + * I guess it is enough if we use voltage/current which is closest (below)
> + * the requested?
> + */
> +
> + ret = linear_range_get_selector_low_array(warm_charge_curr,
> + ARRAY_SIZE(warm_charge_curr),
> + ma, ®, &found);
> if (ret) {
> + dev_err(bdpsy->dev,
> + "Unsupported charge current %u mA\n", ma);
> reg = MIN_CHG_CURR_SEL;
> goto set;
> }
> if (!found) {
> - /* There was a gap in supported values and we hit it */
> + /*
> + * There was a gap in supported values and we hit it.
> + * Yet a smaller value was found so we use it.
> + */
> dev_warn(bdpsy->dev,
> "Unsupported charge current %u mA\n", ma);
> }
> @@ -648,17 +610,21 @@ static int set_current_limit(struct bd70528_psy *bdpsy, int ma)
> goto set;
> }
>
> - ret = find_selector_for_value_low(¤t_limit_ranges[0],
> - ARRAY_SIZE(current_limit_ranges), ma,
> - ®, &found);
> + ret = linear_range_get_selector_low_array(current_limit_ranges,
> + ARRAY_SIZE(current_limit_ranges),
> + ma, ®, &found);
> if (ret) {
> + dev_err(bdpsy->dev, "Unsupported current limit %umA\n", ma);
> reg = MIN_CURR_LIMIT_SEL;
> goto set;
> }
> if (!found) {
> - /* There was a gap in supported values and we hit it ?*/
> - dev_warn(bdpsy->dev, "Unsupported current limit %umA\n",
> - ma);
> + /*
> + * There was a gap in supported values and we hit it.
> + * We found a smaller value from ranges and use it.
> + * Warn user though.
> + */
> + dev_warn(bdpsy->dev, "Unsupported current limit %umA\n", ma);
> }
>
> set:
> --
> 2.21.0
>
>
> --
> Matti Vaittinen, Linux device drivers
> ROHM Semiconductors, Finland SWDC
> Kiviharjunlenkki 1E
> 90220 OULU
> FINLAND
>
> ~~~ "I don't think so," said Rene Descartes. Just then he vanished ~~~
> Simon says - in Latin please.
> ~~~ "non cogito me" dixit Rene Descarte, deinde evanescavit ~~~
> Thanks to Simon Glass for the translation =]
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-04-05 3:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 8:36 [PATCH v8 00/10] Support ROHM BD99954 charger IC Matti Vaittinen
2020-04-03 8:41 ` [PATCH v8 01/10] dt-bindings: battery: add new battery parameters Matti Vaittinen
2020-04-05 3:28 ` Sebastian Reichel
2020-04-03 8:45 ` [PATCH v8 02/10] dt_bindings: ROHM BD99954 Charger Matti Vaittinen
2020-04-05 3:30 ` Sebastian Reichel
2020-04-03 8:45 ` [PATCH v8 03/10] lib: add linear ranges helpers Matti Vaittinen
2020-04-03 9:37 ` Andy Shevchenko
2020-04-03 8:46 ` [PATCH v8 04/10] lib/test_linear_ranges: add a test for the 'linear_ranges' Matti Vaittinen
2020-04-03 8:46 ` [PATCH v8 05/10] power: supply: bd70528: rename linear_range to avoid collision Matti Vaittinen
2020-04-05 3:33 ` Sebastian Reichel
2020-04-06 9:21 ` Vaittinen, Matti
2020-04-03 8:46 ` [PATCH v8 06/10] regulator: use linear_ranges helper Matti Vaittinen
2020-04-03 8:47 ` [PATCH v8 07/10] power: supply: bd70528: use linear ranges Matti Vaittinen
2020-04-05 3:37 ` Sebastian Reichel [this message]
2020-04-03 8:47 ` [PATCH v8 08/10] power: supply: add battery parameters Matti Vaittinen
2020-04-05 3:35 ` Sebastian Reichel
2020-04-03 8:48 ` [PATCH v8 09/10] power: supply: Support ROHM bd99954 charger Matti Vaittinen
2020-04-03 9:41 ` Andy Shevchenko
2020-04-05 3:22 ` Sebastian Reichel
2020-04-06 9:59 ` Vaittinen, Matti
2020-04-03 8:48 ` [PATCH v8 10/10] power: supply: Fix Kconfig help text indentiation Matti Vaittinen
2020-04-05 3:35 ` Sebastian Reichel
2020-04-03 10:07 ` [PATCH v8 00/10] Support ROHM BD99954 charger IC Vaittinen, Matti
2020-04-03 11:02 ` andriy.shevchenko
2020-04-03 11:13 ` Vaittinen, Matti
2020-04-03 11:50 ` andriy.shevchenko
2020-04-03 11:51 ` andriy.shevchenko
2020-04-03 12:01 ` Mark Brown
2020-04-03 12:30 ` Vaittinen, Matti
2020-04-03 12:31 ` Mark Brown
2020-04-05 3:27 ` Sebastian Reichel
2020-04-06 5:22 ` Vaittinen, Matti
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=20200405033722.4co4bnrz5whykrrq@earth.universe \
--to=sebastian.reichel@collabora.com \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=agross@kernel.org \
--cc=andreas@kemnade.info \
--cc=andrei.stefanescu@microchip.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=axel.lin@ingics.com \
--cc=b.zolnierkie@samsung.com \
--cc=baolin.wang@linaro.org \
--cc=bgolaszewski@baylibre.com \
--cc=bjorn.andersson@linaro.org \
--cc=brendanhiggins@google.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.clement@bootlin.com \
--cc=heiko@sntech.de \
--cc=hsin-hsiung.wang@mediatek.com \
--cc=kholk11@gmail.com \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.reichl@fivetechno.de \
--cc=mark.rutland@arm.com \
--cc=markus.laine@fi.rohmeurope.com \
--cc=matthias.bgg@gmail.com \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=mikko.mutanen@fi.rohmeurope.com \
--cc=patches@opensource.cirrus.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rf@opensource.cirrus.com \
--cc=robh+dt@kernel.org \
--cc=sbkim73@samsung.com \
--cc=support.opensource@diasemi.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=vkoul@kernel.org \
--cc=wens@csie.org \
/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;
as well as URLs for NNTP newsgroup(s).