@@ -404,7 +404,7 @@ static void ab8500_enable_disable_sw_fallback(struct ab8500_charger *di,
404
404
}
405
405
406
406
/**
407
- * ab8500_power_supply_changed - a wrapper with local extentions for
407
+ * ab8500_power_supply_changed - a wrapper with local extensions for
408
408
* power_supply_changed
409
409
* @di: pointer to the ab8500_charger structure
410
410
* @psy: pointer to power_supply_that have changed.
@@ -683,7 +683,7 @@ static int ab8500_charger_max_usb_curr(struct ab8500_charger *di,
683
683
/*
684
684
* Platform only supports USB 2.0.
685
685
* This means that charging current from USB source
686
- * is maximum 500 mA. Every occurence of USB_STAT_*_HOST_*
686
+ * is maximum 500 mA. Every occurrence of USB_STAT_*_HOST_*
687
687
* should set USB_CH_IP_CUR_LVL_0P5.
688
688
*/
689
689
@@ -1379,13 +1379,13 @@ static int ab8500_charger_ac_en(struct ux500_charger *charger,
1379
1379
1380
1380
/*
1381
1381
* Due to a bug in AB8500, BTEMP_HIGH/LOW interrupts
1382
- * will be triggered everytime we enable the VDD ADC supply.
1382
+ * will be triggered every time we enable the VDD ADC supply.
1383
1383
* This will turn off charging for a short while.
1384
1384
* It can be avoided by having the supply on when
1385
1385
* there is a charger enabled. Normally the VDD ADC supply
1386
- * is enabled everytime a GPADC conversion is triggered. We will
1387
- * force it to be enabled from this driver to have
1388
- * the GPADC module independant of the AB8500 chargers
1386
+ * is enabled every time a GPADC conversion is triggered.
1387
+ * We will force it to be enabled from this driver to have
1388
+ * the GPADC module independent of the AB8500 chargers
1389
1389
*/
1390
1390
if (!di -> vddadc_en_ac ) {
1391
1391
ret = regulator_enable (di -> regu );
@@ -1455,7 +1455,7 @@ static int ab8500_charger_ac_en(struct ux500_charger *charger,
1455
1455
if (is_ab8500_1p1_or_earlier (di -> parent )) {
1456
1456
/*
1457
1457
* For ABB revision 1.0 and 1.1 there is a bug in the
1458
- * watchdog logic. That means we have to continously
1458
+ * watchdog logic. That means we have to continuously
1459
1459
* kick the charger watchdog even when no charger is
1460
1460
* connected. This is only valid once the AC charger
1461
1461
* has been enabled. This is a bug that is not handled
@@ -1552,13 +1552,13 @@ static int ab8500_charger_usb_en(struct ux500_charger *charger,
1552
1552
1553
1553
/*
1554
1554
* Due to a bug in AB8500, BTEMP_HIGH/LOW interrupts
1555
- * will be triggered everytime we enable the VDD ADC supply.
1555
+ * will be triggered every time we enable the VDD ADC supply.
1556
1556
* This will turn off charging for a short while.
1557
1557
* It can be avoided by having the supply on when
1558
1558
* there is a charger enabled. Normally the VDD ADC supply
1559
- * is enabled everytime a GPADC conversion is triggered. We will
1560
- * force it to be enabled from this driver to have
1561
- * the GPADC module independant of the AB8500 chargers
1559
+ * is enabled every time a GPADC conversion is triggered.
1560
+ * We will force it to be enabled from this driver to have
1561
+ * the GPADC module independent of the AB8500 chargers
1562
1562
*/
1563
1563
if (!di -> vddadc_en_usb ) {
1564
1564
ret = regulator_enable (di -> regu );
@@ -1582,7 +1582,10 @@ static int ab8500_charger_usb_en(struct ux500_charger *charger,
1582
1582
return - ENXIO ;
1583
1583
}
1584
1584
1585
- /* ChVoltLevel: max voltage upto which battery can be charged */
1585
+ /*
1586
+ * ChVoltLevel: max voltage up to which battery can be
1587
+ * charged
1588
+ */
1586
1589
ret = abx500_set_register_interruptible (di -> dev , AB8500_CHARGER ,
1587
1590
AB8500_CH_VOLT_LVL_REG , (u8 ) volt_index );
1588
1591
if (ret ) {
@@ -2014,7 +2017,7 @@ static void ab8500_charger_check_hw_failure_work(struct work_struct *work)
2014
2017
* Work queue function for kicking the charger watchdog.
2015
2018
*
2016
2019
* For ABB revision 1.0 and 1.1 there is a bug in the watchdog
2017
- * logic. That means we have to continously kick the charger
2020
+ * logic. That means we have to continuously kick the charger
2018
2021
* watchdog even when no charger is connected. This is only
2019
2022
* valid once the AC charger has been enabled. This is
2020
2023
* a bug that is not handled by the algorithm and the
@@ -2262,7 +2265,7 @@ static void ab8500_charger_usb_link_status_work(struct work_struct *work)
2262
2265
* Some chargers that breaks the USB spec is
2263
2266
* identified as invalid by AB8500 and it refuse
2264
2267
* to start the charging process. but by jumping
2265
- * thru a few hoops it can be forced to start.
2268
+ * through a few hoops it can be forced to start.
2266
2269
*/
2267
2270
if (is_ab8500 (di -> parent ))
2268
2271
ret = abx500_get_register_interruptible (di -> dev , AB8500_USB ,
@@ -3214,7 +3217,7 @@ static int ab8500_charger_resume(struct platform_device *pdev)
3214
3217
3215
3218
/*
3216
3219
* For ABB revision 1.0 and 1.1 there is a bug in the watchdog
3217
- * logic. That means we have to continously kick the charger
3220
+ * logic. That means we have to continuously kick the charger
3218
3221
* watchdog even when no charger is connected. This is only
3219
3222
* valid once the AC charger has been enabled. This is
3220
3223
* a bug that is not handled by the algorithm and the
@@ -3483,7 +3486,7 @@ static int ab8500_charger_probe(struct platform_device *pdev)
3483
3486
3484
3487
/*
3485
3488
* For ABB revision 1.0 and 1.1 there is a bug in the watchdog
3486
- * logic. That means we have to continously kick the charger
3489
+ * logic. That means we have to continuously kick the charger
3487
3490
* watchdog even when no charger is connected. This is only
3488
3491
* valid once the AC charger has been enabled. This is
3489
3492
* a bug that is not handled by the algorithm and the
0 commit comments