public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Liao Chang <liaochang1@huawei.com>
To: <andi.shyti@kernel.org>, <florian.fainelli@broadcom.com>,
	<rjui@broadcom.com>, <sbranden@broadcom.com>,
	<bcm-kernel-feedback-list@broadcom.com>,
	<yangyicong@hisilicon.com>, <aisheng.dong@nxp.com>,
	<shawnguo@kernel.org>, <s.hauer@pengutronix.de>,
	<kernel@pengutronix.de>, <festevam@gmail.com>,
	<linux-imx@nxp.com>, <kblaiech@nvidia.com>, <asmaa@nvidia.com>,
	<loic.poulain@linaro.org>, <rfoss@kernel.org>, <ardb@kernel.org>,
	<gcherian@marvell.com>
Cc: <linux-i2c@vger.kernel.org>,
	<linux-rpi-kernel@lists.infradead.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-arm-msm@vger.kernel.org>, <liaochang1@huawei.com>
Subject: [PATCH 2/9] i2c: mlxbf: Use dev_err_probe in probe function
Date: Fri, 28 Jul 2023 09:31:41 +0800	[thread overview]
Message-ID: <20230728013148.1720978-3-liaochang1@huawei.com> (raw)
In-Reply-To: <20230728013148.1720978-1-liaochang1@huawei.com>

Use the dev_err_probe function instead of dev_err in the probe function
so that the printed messge includes the return value and also handles
-EPROBE_DEFER nicely.

Signed-off-by: Liao Chang <liaochang1@huawei.com>
---
 drivers/i2c/busses/i2c-mlxbf.c | 44 ++++++++++++----------------------
 1 file changed, 15 insertions(+), 29 deletions(-)

diff --git a/drivers/i2c/busses/i2c-mlxbf.c b/drivers/i2c/busses/i2c-mlxbf.c
index ae66bdd1b737..b5f2aa2fc1db 100644
--- a/drivers/i2c/busses/i2c-mlxbf.c
+++ b/drivers/i2c/busses/i2c-mlxbf.c
@@ -2323,10 +2323,8 @@ static int mlxbf_i2c_probe(struct platform_device *pdev)
 
 		ret = mlxbf_i2c_init_resource(pdev, &priv->smbus,
 					      MLXBF_I2C_SMBUS_RES);
-		if (ret < 0) {
-			dev_err(dev, "Cannot fetch smbus resource info");
-			return ret;
-		}
+		if (ret < 0)
+			return dev_err_probe(dev, ret, "Cannot fetch smbus resource info");
 
 		priv->timer->io = priv->smbus->io;
 		priv->mst->io = priv->smbus->io + MLXBF_I2C_MST_ADDR_OFFSET;
@@ -2334,10 +2332,8 @@ static int mlxbf_i2c_probe(struct platform_device *pdev)
 	} else {
 		ret = mlxbf_i2c_init_resource(pdev, &priv->timer,
 					      MLXBF_I2C_SMBUS_TIMER_RES);
-		if (ret < 0) {
-			dev_err(dev, "Cannot fetch timer resource info");
-			return ret;
-		}
+		if (ret < 0)
+			return dev_err_probe(dev, ret, "Cannot fetch timer resource info");
 
 		ret = mlxbf_i2c_init_resource(pdev, &priv->mst,
 					      MLXBF_I2C_SMBUS_MST_RES);
@@ -2348,25 +2344,19 @@ static int mlxbf_i2c_probe(struct platform_device *pdev)
 
 		ret = mlxbf_i2c_init_resource(pdev, &priv->slv,
 					      MLXBF_I2C_SMBUS_SLV_RES);
-		if (ret < 0) {
-			dev_err(dev, "Cannot fetch slave resource info");
-			return ret;
-		}
+		if (ret < 0)
+			return dev_err_probe(dev, ret, "Cannot fetch slave resource info");
 	}
 
 	ret = mlxbf_i2c_init_resource(pdev, &priv->mst_cause,
 				      MLXBF_I2C_MST_CAUSE_RES);
-	if (ret < 0) {
-		dev_err(dev, "Cannot fetch cause master resource info");
-		return ret;
-	}
+	if (ret < 0)
+		return dev_err_probe(dev, ret, "Cannot fetch cause master resource info");
 
 	ret = mlxbf_i2c_init_resource(pdev, &priv->slv_cause,
 				      MLXBF_I2C_SLV_CAUSE_RES);
-	if (ret < 0) {
-		dev_err(dev, "Cannot fetch cause slave resource info");
-		return ret;
-	}
+	if (ret < 0)
+		return dev_err_probe(dev, ret, "Cannot fetch cause slave resource info");
 
 	adap = &priv->adap;
 	adap->owner = THIS_MODULE;
@@ -2397,11 +2387,9 @@ static int mlxbf_i2c_probe(struct platform_device *pdev)
 	 * does not really hurt, then keep the code as is.
 	 */
 	ret = mlxbf_i2c_init_master(pdev, priv);
-	if (ret < 0) {
-		dev_err(dev, "failed to initialize smbus master %d",
-			priv->bus);
-		return ret;
-	}
+	if (ret < 0)
+		return dev_err_probe(dev, ret, "failed to initialize smbus master %d",
+				     priv->bus);
 
 	mlxbf_i2c_init_timings(pdev, priv);
 
@@ -2413,10 +2401,8 @@ static int mlxbf_i2c_probe(struct platform_device *pdev)
 	ret = devm_request_irq(dev, irq, mlxbf_i2c_irq,
 			       IRQF_SHARED | IRQF_PROBE_SHARED,
 			       dev_name(dev), priv);
-	if (ret < 0) {
-		dev_err(dev, "Cannot get irq %d\n", irq);
-		return ret;
-	}
+	if (ret < 0)
+		return dev_err_probe(dev, ret, "Cannot get irq %d\n", irq);
 
 	priv->irq = irq;
 
-- 
2.25.1


  parent reply	other threads:[~2023-07-28  1:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  1:31 [PATCH 0/9] Use dev_err_probe in i2c probe function Liao Chang
2023-07-28  1:31 ` [PATCH 1/9] i2c: bcm2835: Use dev_err_probe in " Liao Chang
2023-07-28 15:53   ` Florian Fainelli
2023-07-28  1:31 ` Liao Chang [this message]
2023-08-01 21:33   ` [PATCH 2/9] i2c: mlxbf: " Andi Shyti
2023-07-28  1:31 ` [PATCH 3/9] i2c: xlp9xx: " Liao Chang
2023-08-01 21:35   ` Andi Shyti
2023-07-28  1:31 ` [PATCH 4/9] i2c: hisi: " Liao Chang
2023-08-01 13:11   ` Yicong Yang
2023-07-28  1:31 ` [PATCH 5/9] i2c: qcom-cci: " Liao Chang
2023-08-01 21:38   ` Andi Shyti
2023-08-18 11:06   ` Dmitry Baryshkov
2023-08-21 20:37     ` Harshit Mogalapalli
2023-08-21 23:08       ` Dmitry Baryshkov
2023-07-28  1:31 ` [PATCH 6/9] i2c: pxa: " Liao Chang
2023-08-01 21:40   ` Andi Shyti
2023-07-28  1:31 ` [PATCH 7/9] i2c: dln2: " Liao Chang
2023-08-01 21:41   ` Andi Shyti
2023-07-28  1:31 ` [PATCH 8/9] i2c: imx-lpi2c: " Liao Chang
2023-07-28  5:55   ` Uwe Kleine-König
2023-07-31  2:16     ` Liao, Chang
2023-07-31  7:34       ` Uwe Kleine-König
2023-08-01  1:23         ` Liao, Chang
2023-07-28  1:31 ` [PATCH 9/9] i2c: synquacer: " Liao Chang
2023-08-01 21:44   ` Andi Shyti
2023-08-02  7:03     ` Liao, Chang
  -- strict thread matches above, loose matches on Subject: below --
2023-08-02  9:57 [PATCH v2 0/9] Use dev_err_probe in i2c " Liao Chang
2023-08-02  9:57 ` [PATCH 2/9] i2c: mlxbf: Use dev_err_probe in " Liao Chang
2023-08-04 22:11   ` Andi Shyti

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=20230728013148.1720978-3-liaochang1@huawei.com \
    --to=liaochang1@huawei.com \
    --cc=aisheng.dong@nxp.com \
    --cc=andi.shyti@kernel.org \
    --cc=ardb@kernel.org \
    --cc=asmaa@nvidia.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=festevam@gmail.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=gcherian@marvell.com \
    --cc=kblaiech@nvidia.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=loic.poulain@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=rjui@broadcom.com \
    --cc=s.hauer@pengutronix.de \
    --cc=sbranden@broadcom.com \
    --cc=shawnguo@kernel.org \
    --cc=yangyicong@hisilicon.com \
    /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