From: Bibek Kumar Patro <quic_bibekkum@quicinc.com>
To: Pavan Kondeti <quic_pkondeti@quicinc.com>
Cc: <mani@kernel.org>, <miquel.raynal@bootlin.com>, <richard@nod.at>,
<vigneshr@ti.com>, <linux-mtd@lists.infradead.org>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel@quicinc.com>, <quic_charante@quicinc.com>,
<quic_kaushalk@quicinc.com>
Subject: Re: [PATCH] mtd: nand: qcom: Fix the node for nand unmap resource
Date: Mon, 11 Sep 2023 19:07:04 +0530 [thread overview]
Message-ID: <8cdf46d5-62a9-40da-8db4-e888bfd5c8f3@quicinc.com> (raw)
In-Reply-To: <ff77c3ce-d635-4501-8348-5b7adff9a16c@quicinc.com>
On 9/8/2023 3:52 PM, Pavan Kondeti wrote:
> On Thu, Sep 07, 2023 at 02:58:54PM +0530, Bibek Kumar Patro wrote:
>> While unmapping the nand resource in case of err_core_clk
>> the dev node being passed is res_start instead of nand->dma_base
>
> It is not not dev not but addr argument.
>
>> (where the iova returned from map operation is stored) causing
>> failure in unmap operation. Hence modifying the unmap operation
>> to pass the nand->base_dma instead of res_start.
>>
>
> Pls simplify this commit description. I think, it was a simple copy/paste
> mistake. I would write
>
> "Fix addr argument to dma_unmap_resource() in the error path of probe.
> The addr argument should be dma address not physical address."
>
Thanks for this suggestion Pavan, this looks simplified and easier to
understand the bug. Incorporated this in next revision.
>> Signed-off-by: Bibek Kumar Patro <quic_bibekkum@quicinc.com>
>> ---
>> drivers/mtd/nand/raw/qcom_nandc.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/mtd/nand/raw/qcom_nandc.c b/drivers/mtd/nand/raw/qcom_nandc.c
>> index f583022755a2..e085a0f588eb 100644
>> --- a/drivers/mtd/nand/raw/qcom_nandc.c
>> +++ b/drivers/mtd/nand/raw/qcom_nandc.c
>> @@ -3322,7 +3322,7 @@ static int qcom_nandc_probe(struct platform_device *pdev)
>> err_aon_clk:
>> clk_disable_unprepare(nandc->core_clk);
>> err_core_clk:
>> - dma_unmap_resource(dev, res->start, resource_size(res),
>> + dma_unmap_resource(dev, nandc->base_dma, resource_size(res),
>> DMA_BIDIRECTIONAL, 0);
>> dev_err(&pdev->dev, "DEBUG: probe failed for nandc module\n");
>> return ret;
>
> Since you are fixing a bug introduced by a previous commit, you should
> add Fixes tag like below. Refer to Documentation [1].
>
> Fixes: 7330fc505af4 ("mtd: rawnand: qcom: stop using phys_to_dma()")
>
> [1] https://docs.kernel.org/process/submitting-patches.html#using-reported-by-tested-by-reviewed-by-suggested-by-and-fixes
Thanks very much for the inputs, addressed this in next revision.
Thanks & regards,
Bibek
>
> Thanks,
> Pavan
next prev parent reply other threads:[~2023-09-11 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 9:28 [PATCH] mtd: nand: qcom: Fix the node for nand unmap resource Bibek Kumar Patro
2023-09-08 10:22 ` Pavan Kondeti
2023-09-11 13:37 ` Bibek Kumar Patro [this message]
2023-09-09 6:03 ` Manivannan Sadhasivam
2023-09-11 12:46 ` Bibek Kumar Patro
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=8cdf46d5-62a9-40da-8db4-e888bfd5c8f3@quicinc.com \
--to=quic_bibekkum@quicinc.com \
--cc=kernel@quicinc.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mani@kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=quic_charante@quicinc.com \
--cc=quic_kaushalk@quicinc.com \
--cc=quic_pkondeti@quicinc.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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