linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] power: supply: ab8500_charger: Fix typos in commit messages
@ 2020-02-26 17:52 Ashish Chavan
  2020-03-06 20:47 ` Sebastian Reichel
  0 siblings, 1 reply; 2+ messages in thread
From: Ashish Chavan @ 2020-02-26 17:52 UTC (permalink / raw)
  To: sre; +Cc: linux-pm, linux-kernel, Ashish Chavan

Trivial fix to spelling mistake in commit messages.

Signed-off-by: Ashish Chavan <ashish.gschavan@gmail.com>
---
 drivers/power/supply/ab8500_charger.c | 35 +++++++++++++++------------
 1 file changed, 19 insertions(+), 16 deletions(-)

diff --git a/drivers/power/supply/ab8500_charger.c b/drivers/power/supply/ab8500_charger.c
index 98b335042ba6..65741bab8552 100644
--- a/drivers/power/supply/ab8500_charger.c
+++ b/drivers/power/supply/ab8500_charger.c
@@ -398,7 +398,7 @@ static void ab8500_enable_disable_sw_fallback(struct ab8500_charger *di,
 }
 
 /**
- * ab8500_power_supply_changed - a wrapper with local extentions for
+ * ab8500_power_supply_changed - a wrapper with local extensions for
  * power_supply_changed
  * @di:	  pointer to the ab8500_charger structure
  * @psy:  pointer to power_supply_that have changed.
@@ -677,7 +677,7 @@ static int ab8500_charger_max_usb_curr(struct ab8500_charger *di,
 	/*
 	 * Platform only supports USB 2.0.
 	 * This means that charging current from USB source
-	 * is maximum 500 mA. Every occurence of USB_STAT_*_HOST_*
+	 * is maximum 500 mA. Every occurrence of USB_STAT_*_HOST_*
 	 * should set USB_CH_IP_CUR_LVL_0P5.
 	 */
 
@@ -1372,13 +1372,13 @@ static int ab8500_charger_ac_en(struct ux500_charger *charger,
 
 		/*
 		 * Due to a bug in AB8500, BTEMP_HIGH/LOW interrupts
-		 * will be triggered everytime we enable the VDD ADC supply.
+		 * will be triggered every time we enable the VDD ADC supply.
 		 * This will turn off charging for a short while.
 		 * It can be avoided by having the supply on when
 		 * there is a charger enabled. Normally the VDD ADC supply
-		 * is enabled everytime a GPADC conversion is triggered. We will
-		 * force it to be enabled from this driver to have
-		 * the GPADC module independant of the AB8500 chargers
+		 * is enabled every time a GPADC conversion is triggered.
+		 * We will force it to be enabled from this driver to have
+		 * the GPADC module independent of the AB8500 chargers
 		 */
 		if (!di->vddadc_en_ac) {
 			ret = regulator_enable(di->regu);
@@ -1448,7 +1448,7 @@ static int ab8500_charger_ac_en(struct ux500_charger *charger,
 		if (is_ab8500_1p1_or_earlier(di->parent)) {
 			/*
 			 * For ABB revision 1.0 and 1.1 there is a bug in the
-			 * watchdog logic. That means we have to continously
+			 * watchdog logic. That means we have to continuously
 			 * kick the charger watchdog even when no charger is
 			 * connected. This is only valid once the AC charger
 			 * has been enabled. This is a bug that is not handled
@@ -1545,13 +1545,13 @@ static int ab8500_charger_usb_en(struct ux500_charger *charger,
 
 		/*
 		 * Due to a bug in AB8500, BTEMP_HIGH/LOW interrupts
-		 * will be triggered everytime we enable the VDD ADC supply.
+		 * will be triggered every time we enable the VDD ADC supply.
 		 * This will turn off charging for a short while.
 		 * It can be avoided by having the supply on when
 		 * there is a charger enabled. Normally the VDD ADC supply
-		 * is enabled everytime a GPADC conversion is triggered. We will
-		 * force it to be enabled from this driver to have
-		 * the GPADC module independant of the AB8500 chargers
+		 * is enabled every time a GPADC conversion is triggered.
+		 * We will force it to be enabled from this driver to have
+		 * the GPADC module independent of the AB8500 chargers
 		 */
 		if (!di->vddadc_en_usb) {
 			ret = regulator_enable(di->regu);
@@ -1575,7 +1575,10 @@ static int ab8500_charger_usb_en(struct ux500_charger *charger,
 			return -ENXIO;
 		}
 
-		/* ChVoltLevel: max voltage upto which battery can be charged */
+		/*
+		 * ChVoltLevel: max voltage up to which battery can be
+		 * charged
+		 */
 		ret = abx500_set_register_interruptible(di->dev, AB8500_CHARGER,
 			AB8500_CH_VOLT_LVL_REG, (u8) volt_index);
 		if (ret) {
@@ -2007,7 +2010,7 @@ static void ab8500_charger_check_hw_failure_work(struct work_struct *work)
  * Work queue function for kicking the charger watchdog.
  *
  * For ABB revision 1.0 and 1.1 there is a bug in the watchdog
- * logic. That means we have to continously kick the charger
+ * logic. That means we have to continuously kick the charger
  * watchdog even when no charger is connected. This is only
  * valid once the AC charger has been enabled. This is
  * a bug that is not handled by the algorithm and the
@@ -2255,7 +2258,7 @@ static void ab8500_charger_usb_link_status_work(struct work_struct *work)
 	 * Some chargers that breaks the USB spec is
 	 * identified as invalid by AB8500 and it refuse
 	 * to start the charging process. but by jumping
-	 * thru a few hoops it can be forced to start.
+	 * through a few hoops it can be forced to start.
 	 */
 	if (is_ab8500(di->parent))
 		ret = abx500_get_register_interruptible(di->dev, AB8500_USB,
@@ -3214,7 +3217,7 @@ static int ab8500_charger_resume(struct platform_device *pdev)
 
 	/*
 	 * For ABB revision 1.0 and 1.1 there is a bug in the watchdog
-	 * logic. That means we have to continously kick the charger
+	 * logic. That means we have to continuously kick the charger
 	 * watchdog even when no charger is connected. This is only
 	 * valid once the AC charger has been enabled. This is
 	 * a bug that is not handled by the algorithm and the
@@ -3451,7 +3454,7 @@ static int ab8500_charger_probe(struct platform_device *pdev)
 
 	/*
 	 * For ABB revision 1.0 and 1.1 there is a bug in the watchdog
-	 * logic. That means we have to continously kick the charger
+	 * logic. That means we have to continuously kick the charger
 	 * watchdog even when no charger is connected. This is only
 	 * valid once the AC charger has been enabled. This is
 	 * a bug that is not handled by the algorithm and the
-- 
2.17.1


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] power: supply: ab8500_charger: Fix typos in commit messages
  2020-02-26 17:52 [PATCH] power: supply: ab8500_charger: Fix typos in commit messages Ashish Chavan
@ 2020-03-06 20:47 ` Sebastian Reichel
  0 siblings, 0 replies; 2+ messages in thread
From: Sebastian Reichel @ 2020-03-06 20:47 UTC (permalink / raw)
  To: Ashish Chavan; +Cc: linux-pm, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 6204 bytes --]

Hi,

On Wed, Feb 26, 2020 at 11:22:23PM +0530, Ashish Chavan wrote:
> Trivial fix to spelling mistake in commit messages.
> 
> Signed-off-by: Ashish Chavan <ashish.gschavan@gmail.com>
> ---

Thanks, queued.

-- Sebastian

>  drivers/power/supply/ab8500_charger.c | 35 +++++++++++++++------------
>  1 file changed, 19 insertions(+), 16 deletions(-)
> 
> diff --git a/drivers/power/supply/ab8500_charger.c b/drivers/power/supply/ab8500_charger.c
> index 98b335042ba6..65741bab8552 100644
> --- a/drivers/power/supply/ab8500_charger.c
> +++ b/drivers/power/supply/ab8500_charger.c
> @@ -398,7 +398,7 @@ static void ab8500_enable_disable_sw_fallback(struct ab8500_charger *di,
>  }
>  
>  /**
> - * ab8500_power_supply_changed - a wrapper with local extentions for
> + * ab8500_power_supply_changed - a wrapper with local extensions for
>   * power_supply_changed
>   * @di:	  pointer to the ab8500_charger structure
>   * @psy:  pointer to power_supply_that have changed.
> @@ -677,7 +677,7 @@ static int ab8500_charger_max_usb_curr(struct ab8500_charger *di,
>  	/*
>  	 * Platform only supports USB 2.0.
>  	 * This means that charging current from USB source
> -	 * is maximum 500 mA. Every occurence of USB_STAT_*_HOST_*
> +	 * is maximum 500 mA. Every occurrence of USB_STAT_*_HOST_*
>  	 * should set USB_CH_IP_CUR_LVL_0P5.
>  	 */
>  
> @@ -1372,13 +1372,13 @@ static int ab8500_charger_ac_en(struct ux500_charger *charger,
>  
>  		/*
>  		 * Due to a bug in AB8500, BTEMP_HIGH/LOW interrupts
> -		 * will be triggered everytime we enable the VDD ADC supply.
> +		 * will be triggered every time we enable the VDD ADC supply.
>  		 * This will turn off charging for a short while.
>  		 * It can be avoided by having the supply on when
>  		 * there is a charger enabled. Normally the VDD ADC supply
> -		 * is enabled everytime a GPADC conversion is triggered. We will
> -		 * force it to be enabled from this driver to have
> -		 * the GPADC module independant of the AB8500 chargers
> +		 * is enabled every time a GPADC conversion is triggered.
> +		 * We will force it to be enabled from this driver to have
> +		 * the GPADC module independent of the AB8500 chargers
>  		 */
>  		if (!di->vddadc_en_ac) {
>  			ret = regulator_enable(di->regu);
> @@ -1448,7 +1448,7 @@ static int ab8500_charger_ac_en(struct ux500_charger *charger,
>  		if (is_ab8500_1p1_or_earlier(di->parent)) {
>  			/*
>  			 * For ABB revision 1.0 and 1.1 there is a bug in the
> -			 * watchdog logic. That means we have to continously
> +			 * watchdog logic. That means we have to continuously
>  			 * kick the charger watchdog even when no charger is
>  			 * connected. This is only valid once the AC charger
>  			 * has been enabled. This is a bug that is not handled
> @@ -1545,13 +1545,13 @@ static int ab8500_charger_usb_en(struct ux500_charger *charger,
>  
>  		/*
>  		 * Due to a bug in AB8500, BTEMP_HIGH/LOW interrupts
> -		 * will be triggered everytime we enable the VDD ADC supply.
> +		 * will be triggered every time we enable the VDD ADC supply.
>  		 * This will turn off charging for a short while.
>  		 * It can be avoided by having the supply on when
>  		 * there is a charger enabled. Normally the VDD ADC supply
> -		 * is enabled everytime a GPADC conversion is triggered. We will
> -		 * force it to be enabled from this driver to have
> -		 * the GPADC module independant of the AB8500 chargers
> +		 * is enabled every time a GPADC conversion is triggered.
> +		 * We will force it to be enabled from this driver to have
> +		 * the GPADC module independent of the AB8500 chargers
>  		 */
>  		if (!di->vddadc_en_usb) {
>  			ret = regulator_enable(di->regu);
> @@ -1575,7 +1575,10 @@ static int ab8500_charger_usb_en(struct ux500_charger *charger,
>  			return -ENXIO;
>  		}
>  
> -		/* ChVoltLevel: max voltage upto which battery can be charged */
> +		/*
> +		 * ChVoltLevel: max voltage up to which battery can be
> +		 * charged
> +		 */
>  		ret = abx500_set_register_interruptible(di->dev, AB8500_CHARGER,
>  			AB8500_CH_VOLT_LVL_REG, (u8) volt_index);
>  		if (ret) {
> @@ -2007,7 +2010,7 @@ static void ab8500_charger_check_hw_failure_work(struct work_struct *work)
>   * Work queue function for kicking the charger watchdog.
>   *
>   * For ABB revision 1.0 and 1.1 there is a bug in the watchdog
> - * logic. That means we have to continously kick the charger
> + * logic. That means we have to continuously kick the charger
>   * watchdog even when no charger is connected. This is only
>   * valid once the AC charger has been enabled. This is
>   * a bug that is not handled by the algorithm and the
> @@ -2255,7 +2258,7 @@ static void ab8500_charger_usb_link_status_work(struct work_struct *work)
>  	 * Some chargers that breaks the USB spec is
>  	 * identified as invalid by AB8500 and it refuse
>  	 * to start the charging process. but by jumping
> -	 * thru a few hoops it can be forced to start.
> +	 * through a few hoops it can be forced to start.
>  	 */
>  	if (is_ab8500(di->parent))
>  		ret = abx500_get_register_interruptible(di->dev, AB8500_USB,
> @@ -3214,7 +3217,7 @@ static int ab8500_charger_resume(struct platform_device *pdev)
>  
>  	/*
>  	 * For ABB revision 1.0 and 1.1 there is a bug in the watchdog
> -	 * logic. That means we have to continously kick the charger
> +	 * logic. That means we have to continuously kick the charger
>  	 * watchdog even when no charger is connected. This is only
>  	 * valid once the AC charger has been enabled. This is
>  	 * a bug that is not handled by the algorithm and the
> @@ -3451,7 +3454,7 @@ static int ab8500_charger_probe(struct platform_device *pdev)
>  
>  	/*
>  	 * For ABB revision 1.0 and 1.1 there is a bug in the watchdog
> -	 * logic. That means we have to continously kick the charger
> +	 * logic. That means we have to continuously kick the charger
>  	 * watchdog even when no charger is connected. This is only
>  	 * valid once the AC charger has been enabled. This is
>  	 * a bug that is not handled by the algorithm and the
> -- 
> 2.17.1
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-03-06 20:47 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-26 17:52 [PATCH] power: supply: ab8500_charger: Fix typos in commit messages Ashish Chavan
2020-03-06 20:47 ` Sebastian Reichel

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).