From: Shubhankar Kuranagatti <shubhankarvk@gmail.com>
To: sre@kernel.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
sanjanasrinidhi1810@gmail.com
Subject: [PATCH] drivers: power: supply: ab8500_charger.c: Add blank line after declaration
Date: Thu, 17 Jun 2021 12:09:46 +0530 [thread overview]
Message-ID: <20210617063946.ziyswdxsk46xw63a@kewl-virtual-machine> (raw)
Added blank line after declaration
Removed repetition of "the" in comment block
Fixed indentation of conditional statement
Replaced spaces with tabs
This is done to manintain uniformity in coding style
Signed-off-by: Shubhankar Kuranagatti <shubhankarvk@gmail.com>
---
drivers/power/supply/ab8500_charger.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/power/supply/ab8500_charger.c b/drivers/power/supply/ab8500_charger.c
index ac77c8882d17..4d71e1a769b2 100644
--- a/drivers/power/supply/ab8500_charger.c
+++ b/drivers/power/supply/ab8500_charger.c
@@ -237,7 +237,7 @@ struct ab8500_charger_max_usb_in_curr {
* @adc_main_charger_c ADC channel for main charger current
* @adc_vbus_v ADC channel for USB charger voltage
* @adc_usb_charger_c ADC channel for USB charger current
- * @bm: Platform specific battery management information
+ * @bm: Platform specific battery management information
* @flags: Structure for information about events triggered
* @usb_state: Structure for usb stack information
* @max_usb_in_curr: Max USB charger input current
@@ -1059,6 +1059,7 @@ static int ab8500_vbus_in_curr_to_regval(struct ab8500_charger *di, int curr)
static int ab8500_charger_get_usb_cur(struct ab8500_charger *di)
{
int ret = 0;
+
switch (di->usb_state.usb_current) {
case 100:
di->max_usb_in_curr.usb_type_max = USB_CH_IP_CUR_LVL_0P09;
@@ -1206,6 +1207,7 @@ static int ab8500_charger_set_current(struct ab8500_charger *di,
}
} else {
bool allow = true;
+
for (i = prev_curr_index + 1; i <= curr_index && allow; i++) {
dev_dbg(di->dev, "curr change_2 to: %x for 0x%02x\n",
(u8)i << shift_value, reg);
@@ -1893,6 +1895,7 @@ static int ab8500_charger_get_ext_psy_data(struct device *dev, void *data)
/* Go through all properties for the psy */
for (j = 0; j < ext->desc->num_properties; j++) {
enum power_supply_property prop;
+
prop = ext->desc->properties[j];
if (power_supply_get_property(ext, prop, &ret))
@@ -1922,7 +1925,7 @@ static int ab8500_charger_get_ext_psy_data(struct device *dev, void *data)
* Due to a asic bug it is necessary to lower the input current to the vbus
* charger when charging with at some specific levels. This issue is only valid
* for below a certain battery voltage. This function makes sure that the
- * the allowed current limit isn't exceeded.
+ * allowed current limit isn't exceeded.
*/
static void ab8500_charger_check_vbat_work(struct work_struct *work)
{
@@ -1958,7 +1961,7 @@ static void ab8500_charger_check_vbat_work(struct work_struct *work)
*/
if (di->vbat < (VBAT_TRESH_IP_CUR_RED + 100) &&
(di->vbat > (VBAT_TRESH_IP_CUR_RED - 100)))
- t = 1;
+ t = 1;
queue_delayed_work(di->charger_wq, &di->check_vbat_work, t * HZ);
}
--
2.17.1
reply other threads:[~2021-06-17 6:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210617063946.ziyswdxsk46xw63a@kewl-virtual-machine \
--to=shubhankarvk@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sanjanasrinidhi1810@gmail.com \
--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).