public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH 2/2] i2c: qcom-geni: Simplify error handling in probe function
Date: Thu, 12 Dec 2024 22:02:01 +0530	[thread overview]
Message-ID: <c4a8393c-37f5-4115-a67f-2a4e98b6648a@quicinc.com> (raw)
In-Reply-To: <fd45ts4bgcaaoydvvkq52c3r65dhrmbe4ig3oxp7pqtmrckdwd@wnyfmzlfhgs5>

Thanks Andi !

On 12/12/2024 7:15 PM, Andi Shyti wrote:
> Hi Mukesh,
> 
>>> diff --git a/drivers/i2c/busses/i2c-qcom-geni.c b/drivers/i2c/busses/i2c-qcom-geni.c
>>> index 01db24188e29..3fc85595a4aa 100644
>>> --- a/drivers/i2c/busses/i2c-qcom-geni.c
>>> +++ b/drivers/i2c/busses/i2c-qcom-geni.c
>>> @@ -867,14 +867,13 @@ static int geni_i2c_probe(struct platform_device *pdev)
>>>    	ret = geni_se_resources_on(&gi2c->se);
>>>    	if (ret) {
>>> -		clk_disable_unprepare(gi2c->core_clk);
>>> -		return dev_err_probe(dev, ret, "Error turning on resources\n");
>>> +		dev_err_probe(dev, ret, "Error turning on resources\n");
>>> +		goto err_clk;
>>>    	}
>>>    	proto = geni_se_read_proto(&gi2c->se);
>>>    	if (proto != GENI_SE_I2C) {
>>> -		geni_se_resources_off(&gi2c->se);
>>> -		clk_disable_unprepare(gi2c->core_clk);
>>> -		return dev_err_probe(dev, -ENXIO, "Invalid proto %d\n", proto);
>>> +		dev_err_probe(dev, -ENXIO, "Invalid proto %d\n", proto);
>> Suggestive comment, can we make this second patch as first patch ? So that
>> we can have both above lines reduced in this patch.
> 
> I'm sorry, I missed this comment. I tried to swap it and there is
> not much reduction in line changes[*].
> 
> The reason I chose this order is to avoid changing the same line
> on both the patches, like here[**].
> 
> If it's not binding for you, I would keep the ordering.
> 
Sure, it's perfectly fine to me. No worries.
> Thanks again a lot for looking into this,
> Andi
> 
> [*] https://paste.debian.net/1339486/
> [**] https://paste.debian.net/1339488/
> 
>>> +		goto err_off;
>>>    	}
>>>    	if (desc && desc->no_dma_support)
>>> @@ -886,11 +885,8 @@ static int geni_i2c_probe(struct platform_device *pdev)
>>>    		/* FIFO is disabled, so we can only use GPI DMA */
>>>    		gi2c->gpi_mode = true;
>>>    		ret = setup_gpi_dma(gi2c);
>>> -		if (ret) {
>>> -			geni_se_resources_off(&gi2c->se);
>>> -			clk_disable_unprepare(gi2c->core_clk);
>>> -			return ret;
>>> -		}
>>> +		if (ret)
>>> +			goto err_off;
>>>    		dev_dbg(dev, "Using GPI DMA mode for I2C\n");
>>>    	} else {
>>> @@ -902,10 +898,8 @@ static int geni_i2c_probe(struct platform_device *pdev)
>>>    			tx_depth = desc->tx_fifo_depth;
>>>    		if (!tx_depth) {
>>> -			geni_se_resources_off(&gi2c->se);
>>> -			clk_disable_unprepare(gi2c->core_clk);
>>> -			return dev_err_probe(dev, -EINVAL,
>>> -					     "Invalid TX FIFO depth\n");
>>> +			dev_err_probe(dev, -EINVAL, "Invalid TX FIFO depth\n");
>>> +			goto err_off;
>>>    		}
>>>    		gi2c->tx_wm = tx_depth - 1;
>>> @@ -944,8 +938,16 @@ static int geni_i2c_probe(struct platform_device *pdev)
>>>    	return 0;
>> return ret here ? yes, we need to initialize ret = 0.
>>> +err_off:
>> can we rename as err_resources ?
>>> +	geni_se_resources_off(&gi2c->se);
>>> +err_clk:
>>> +	clk_disable_unprepare(gi2c->core_clk);
>>> +
>>> +	return ret;
>>> +
>>>    err_dma:
>>>    	release_gpi_dma(gi2c);
>>> +
>>>    	return ret;
>>>    }
>>


      reply	other threads:[~2024-12-12 16:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10 23:10 [PATCH 0/2] Qcom Geni exit path cleanups Andi Shyti
2024-12-10 23:10 ` [PATCH 1/2] i2c: qcom-geni: Use dev_err_probe in the probe function Andi Shyti
2024-12-10 23:10 ` [PATCH 2/2] i2c: qcom-geni: Simplify error handling in " Andi Shyti
2024-12-11  3:56   ` Mukesh Kumar Savaliya
2024-12-11  6:56     ` Andi Shyti
2024-12-11  7:06       ` Mukesh Kumar Savaliya
2024-12-11  9:09         ` Andi Shyti
2024-12-12 13:45     ` Andi Shyti
2024-12-12 16:32       ` Mukesh Kumar Savaliya [this message]

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=c4a8393c-37f5-4115-a67f-2a4e98b6648a@quicinc.com \
    --to=quic_msavaliy@quicinc.com \
    --cc=andi.shyti@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.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