From: Andi Shyti <andi.shyti@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Wolfram Sang <wsa@kernel.org>, Jon Hunter <jonathanh@nvidia.com>,
Akhil R <akhilrajeev@nvidia.com>,
linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] i2c: tegra: Fix failure during probe deferral cleanup
Date: Thu, 8 Jun 2023 10:39:05 +0200 [thread overview]
Message-ID: <20230608083905.youqz3wt27sqda2f@intel.intel> (raw)
In-Reply-To: <20230608075606.3590744-1-thierry.reding@gmail.com>
Hi Thierry,
On Thu, Jun 08, 2023 at 09:56:06AM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> If the driver fails to obtain a DMA channel, it will initiate cleanup
> and try to release the DMA channel that couldn't be retrieved. This will
> cause a crash because the cleanup will try to dereference an ERR_PTR()-
> encoded error code.
>
> However, there's nothing to clean up at this point yet, so we can avoid
> this by simply propagating the error code.
>
> Fixes: fcc8a89a1c83 ("i2c: tegra: Share same DMA channel for RX and TX")
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> drivers/i2c/busses/i2c-tegra.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
> index f155e9028f94..0eab199900ae 100644
> --- a/drivers/i2c/busses/i2c-tegra.c
> +++ b/drivers/i2c/busses/i2c-tegra.c
> @@ -458,10 +458,8 @@ static int tegra_i2c_init_dma(struct tegra_i2c_dev *i2c_dev)
> * with existing devicetrees.
> */
> i2c_dev->dma_chan = dma_request_chan(i2c_dev->dev, "tx");
> - if (IS_ERR(i2c_dev->dma_chan)) {
> - err = PTR_ERR(i2c_dev->dma_chan);
> - goto err_out;
> - }
> + if (IS_ERR(i2c_dev->dma_chan))
> + return PTR_ERR(i2c_dev->dma_chan);
Actually you are ignoring the case when the driver would use
programmed i/o only as a backup plan.
I think a possible fix could be:
--- a/drivers/i2c/busses/i2c-tegra.c
+++ b/drivers/i2c/busses/i2c-tegra.c
@@ -460,7 +460,7 @@ static int tegra_i2c_init_dma(struct tegra_i2c_dev *i2c_dev)
i2c_dev->dma_chan = dma_request_chan(i2c_dev->dev, "tx");
if (IS_ERR(i2c_dev->dma_chan)) {
err = PTR_ERR(i2c_dev->dma_chan);
- goto err_out;
+ goto err_probe_defer;
}
i2c_dev->dma_dev = i2c_dev->dma_chan->device->dev;
@@ -482,6 +482,7 @@ static int tegra_i2c_init_dma(struct tegra_i2c_dev *i2c_dev)
err_out:
tegra_i2c_release_dma(i2c_dev);
+err_probe_defer:
if (err != -EPROBE_DEFER) {
dev_err(i2c_dev->dev, "cannot use DMA: %d\n", err);
dev_err(i2c_dev->dev, "falling back to PIO\n");
Thank you,
Andi
(BTW, those are not dev_err's but they should be either dev_info
or dev_warn())
>
> i2c_dev->dma_dev = i2c_dev->dma_chan->device->dev;
> i2c_dev->dma_buf_size = i2c_dev->hw->quirks->max_write_len +
> --
> 2.40.1
>
next prev parent reply other threads:[~2023-06-08 8:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 7:56 [PATCH] i2c: tegra: Fix failure during probe deferral cleanup Thierry Reding
2023-06-08 8:39 ` Andi Shyti [this message]
2023-06-08 15:55 ` Thierry Reding
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=20230608083905.youqz3wt27sqda2f@intel.intel \
--to=andi.shyti@kernel.org \
--cc=akhilrajeev@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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