public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jan Dabros <jsd@semihalf.com>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
	jarkko.nikula@linux.intel.com, wsa@kernel.org,
	upstream@semihalf.com
Subject: Re: [PATCH v2 -next] i2c: designware: Remove code duplication
Date: Fri, 11 Mar 2022 19:01:12 +0200	[thread overview]
Message-ID: <YiuAWFtg1ApWQMxR@smile.fi.intel.com> (raw)
In-Reply-To: <20220310220932.140973-1-jsd@semihalf.com>

On Thu, Mar 10, 2022 at 11:09:32PM +0100, Jan Dabros wrote:
> Simplify code by moving common part to one function.

LGTM
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

> Signed-off-by: Jan Dabros <jsd@semihalf.com>
> Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> v1->v2:
> * Add kudos for Andy who suggested this change
> * Get rid of extra function and move common code to psp_send_i2c_req
> * Update commit message and commit title
>   (was "i2c:designware: Add helper to remove redundancy")
>  drivers/i2c/busses/i2c-designware-amdpsp.c | 35 ++++++++++------------
>  1 file changed, 15 insertions(+), 20 deletions(-)
> 
> diff --git a/drivers/i2c/busses/i2c-designware-amdpsp.c b/drivers/i2c/busses/i2c-designware-amdpsp.c
> index c64e459afb5c..5c32255c3239 100644
> --- a/drivers/i2c/busses/i2c-designware-amdpsp.c
> +++ b/drivers/i2c/busses/i2c-designware-amdpsp.c
> @@ -214,17 +214,28 @@ static int psp_send_i2c_req(enum psp_i2c_req_type i2c_req_type)
>  				PSP_I2C_REQ_RETRY_DELAY_US,
>  				PSP_I2C_REQ_RETRY_CNT * PSP_I2C_REQ_RETRY_DELAY_US,
>  				0, req);
> -	if (ret)
> +	if (ret) {
> +		dev_err(psp_i2c_dev, "Timed out waiting for PSP to %s I2C bus\n",
> +			(i2c_req_type == PSP_I2C_REQ_ACQUIRE) ?
> +			"release" : "acquire");
>  		goto cleanup;
> +	}
>  
>  	ret = status;
> -	if (ret)
> +	if (ret) {
> +		dev_err(psp_i2c_dev, "PSP communication error\n");
>  		goto cleanup;
> +	}
>  
>  	dev_dbg(psp_i2c_dev, "Request accepted by PSP after %ums\n",
>  		jiffies_to_msecs(jiffies - start));
>  
>  cleanup:
> +	if (ret) {
> +		dev_err(psp_i2c_dev, "Assume i2c bus is for exclusive host usage\n");
> +		psp_i2c_mbox_fail = true;
> +	}
> +
>  	kfree(req);
>  	return ret;
>  }
> @@ -249,16 +260,8 @@ static int psp_acquire_i2c_bus(void)
>  	};
>  
>  	status = psp_send_i2c_req(PSP_I2C_REQ_ACQUIRE);
> -	if (status) {
> -		if (status == -ETIMEDOUT)
> -			dev_err(psp_i2c_dev, "Timed out waiting for PSP to release I2C bus\n");
> -		else
> -			dev_err(psp_i2c_dev, "PSP communication error\n");
> -
> -		dev_err(psp_i2c_dev, "Assume i2c bus is for exclusive host usage\n");
> -		psp_i2c_mbox_fail = true;
> +	if (status)
>  		goto cleanup;
> -	}
>  
>  	psp_i2c_sem_acquired = jiffies;
>  	psp_i2c_access_count++;
> @@ -294,16 +297,8 @@ static void psp_release_i2c_bus(void)
>  
>  	/* Send a release command to PSP */
>  	status = psp_send_i2c_req(PSP_I2C_REQ_RELEASE);
> -	if (status) {
> -		if (status == -ETIMEDOUT)
> -			dev_err(psp_i2c_dev, "Timed out waiting for PSP to acquire I2C bus\n");
> -		else
> -			dev_err(psp_i2c_dev, "PSP communication error\n");
> -
> -		dev_err(psp_i2c_dev, "Assume i2c bus is for exclusive host usage\n");
> -		psp_i2c_mbox_fail = true;
> +	if (status)
>  		goto cleanup;
> -	}
>  
>  	dev_dbg(psp_i2c_dev, "PSP semaphore held for %ums\n",
>  		jiffies_to_msecs(jiffies - psp_i2c_sem_acquired));
> -- 
> 2.31.0
> 

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2022-03-11 17:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 22:09 [PATCH v2 -next] i2c: designware: Remove code duplication Jan Dabros
2022-03-11  8:24 ` Jarkko Nikula
2022-03-11 17:01 ` Andy Shevchenko [this message]
2022-03-11 20:51 ` Wolfram Sang
2022-03-14  8:56   ` Jan Dąbroś
2022-03-14  9:03   ` Jarkko Nikula

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=YiuAWFtg1ApWQMxR@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=jsd@semihalf.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=upstream@semihalf.com \
    --cc=wsa@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