From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Jan Dabros <jsd@semihalf.com>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
andriy.shevchenko@linux.intel.com
Cc: wsa@kernel.org, upstream@semihalf.com
Subject: Re: [PATCH -next] i2c: designware: Add helper to remove redundancy
Date: Thu, 10 Mar 2022 16:52:09 +0200 [thread overview]
Message-ID: <5612fbbe-a42b-997e-2375-6d5f0c53bdea@linux.intel.com> (raw)
In-Reply-To: <20220310142236.192811-1-jsd@semihalf.com>
On 3/10/22 16:22, Jan Dabros wrote:
> Simplify code by adding an extra static function for sending I2C
> requests and verifying results.
>
> Signed-off-by: Jan Dabros <jsd@semihalf.com>
> ---
> drivers/i2c/busses/i2c-designware-amdpsp.c | 44 ++++++++++++----------
> 1 file changed, 24 insertions(+), 20 deletions(-)
>
Do I remember correctly was this suggested by Andy? I.e. to give kudos
to him if that was the case:
Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> diff --git a/drivers/i2c/busses/i2c-designware-amdpsp.c b/drivers/i2c/busses/i2c-designware-amdpsp.c
> index c64e459afb5c..cc758792f150 100644
> --- a/drivers/i2c/busses/i2c-designware-amdpsp.c
> +++ b/drivers/i2c/busses/i2c-designware-amdpsp.c
> @@ -229,6 +229,26 @@ static int psp_send_i2c_req(enum psp_i2c_req_type i2c_req_type)
> return ret;
> }
>
> +static int psp_send_i2c_req_check_err(enum psp_i2c_req_type request)
> +{
> + int status;
> +
> + status = psp_send_i2c_req(request);
> + if (status) {
> + if (status == -ETIMEDOUT)
> + dev_err(psp_i2c_dev, "Timed out waiting for PSP to %s I2C bus\n",
> + (request == PSP_I2C_REQ_ACQUIRE) ?
> + "release" : "acquire");
> + 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;
> + }
> +
Does it make sense to have these inside the psp_send_i2c_req() and get
rid of this new middle function? I mean psp_send_i2c_req() is called now
only from here so can it do these common error prints and set
"psp_i2c_mbox_fail = true"?
Jarkko
next prev parent reply other threads:[~2022-03-10 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 14:22 [PATCH -next] i2c: designware: Add helper to remove redundancy Jan Dabros
2022-03-10 14:52 ` Jarkko Nikula [this message]
2022-03-10 21:57 ` Jan Dąbroś
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=5612fbbe-a42b-997e-2375-6d5f0c53bdea@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andriy.shevchenko@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