From: Saravanan Sekar <sravanhome@gmail.com>
To: sre@kernel.org, lee.jones@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, jic23@kernel.org,
lars@metafoo.de, andy.shevchenko@gmail.com
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-iio@vger.kernel.org, Saravanan Sekar <sravanhome@gmail.com>
Subject: [PATCH v5 4/8] power: supply: fix wrong interpretation of register value
Date: Sat, 29 Oct 2022 11:29:56 +0200 [thread overview]
Message-ID: <20221029093000.45451-5-sravanhome@gmail.com> (raw)
In-Reply-To: <20221029093000.45451-1-sravanhome@gmail.com>
fix the switch cases to match the register value.
Signed-off-by: Saravanan Sekar <sravanhome@gmail.com>
---
drivers/power/supply/mp2629_charger.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/power/supply/mp2629_charger.c b/drivers/power/supply/mp2629_charger.c
index bf9c27b463a8..46d620bd23b9 100644
--- a/drivers/power/supply/mp2629_charger.c
+++ b/drivers/power/supply/mp2629_charger.c
@@ -284,10 +284,10 @@ static int mp2629_charger_battery_get_prop(struct power_supply *psy,
val->intval = POWER_SUPPLY_STATUS_DISCHARGING;
break;
case 0x01:
- case 0x10:
+ case 0x02:
val->intval = POWER_SUPPLY_STATUS_CHARGING;
break;
- case 0x11:
+ case 0x03:
val->intval = POWER_SUPPLY_STATUS_FULL;
}
break;
@@ -305,7 +305,7 @@ static int mp2629_charger_battery_get_prop(struct power_supply *psy,
case 0x01:
val->intval = POWER_SUPPLY_CHARGE_TYPE_TRICKLE;
break;
- case 0x10:
+ case 0x02:
val->intval = POWER_SUPPLY_CHARGE_TYPE_STANDARD;
break;
default:
--
2.32.0
next prev parent reply other threads:[~2022-10-29 9:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 9:29 [PATCH v5 0/8] Add support for mp2733 battery charger Saravanan Sekar
2022-10-29 9:29 ` [PATCH v5 1/8] iio: adc: mp2629: fix wrong comparison of channel Saravanan Sekar
2022-10-29 12:28 ` Jonathan Cameron
2022-10-29 9:29 ` [PATCH v5 2/8] mfd: mp2629: fix failed to get iio channel by device name Saravanan Sekar
2022-10-29 9:29 ` [PATCH v5 3/8] iio: adc: mp2629: fix potential array out of bound access Saravanan Sekar
2022-10-29 12:30 ` Jonathan Cameron
2022-10-29 9:29 ` Saravanan Sekar [this message]
2022-10-29 22:52 ` [PATCH v5 4/8] power: supply: fix wrong interpretation of register value Andy Shevchenko
2022-10-29 9:29 ` [PATCH v5 5/8] mfd: mp2629: Add support for mps mp2733 battery charger Saravanan Sekar
2022-10-29 12:36 ` Jonathan Cameron
2022-10-29 9:29 ` [PATCH v5 6/8] iio: adc: mp2629: restrict input voltage mask for mp2629 Saravanan Sekar
2022-10-29 12:35 ` Jonathan Cameron
2022-10-29 9:29 ` [PATCH v5 7/8] power: supply: Add support for mp2733 battery charger Saravanan Sekar
2022-10-29 9:30 ` [PATCH v5 8/8] power: supply: mp2629: Add USB fast charge settings Saravanan Sekar
2022-10-29 22:02 ` [PATCH v5 0/8] Add support for mp2733 battery charger Sebastian Reichel
2022-10-29 22:11 ` saravanan sekar
2022-11-04 1:54 ` Krzysztof Kozlowski
2022-11-04 7:13 ` saravanan sekar
2022-11-04 12:58 ` Krzysztof Kozlowski
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=20221029093000.45451-5-sravanhome@gmail.com \
--to=sravanhome@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sre@kernel.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).