From: Alexander Dahl <ada@thorsis.com>
To: "Csókás, Bence" <csokas.bence@prolan.hu>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Varshini Rajendran <varshini.rajendran@microchip.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/2] spi: atmel-quadspi: Add support for sama7g5 QSPI
Date: Fri, 10 Jan 2025 08:56:29 +0100 [thread overview]
Message-ID: <20250110-paycheck-irregular-bcddab1276c7@thorsis.com> (raw)
In-Reply-To: <20241128174316.3209354-3-csokas.bence@prolan.hu>
Hello,
found another suspicious area regarding pm_runtime in
atmel_qspi_probe(), see below (irrelevant stuff dropped this time) …
Am Thu, Nov 28, 2024 at 06:43:15PM +0100 schrieb Csókás, Bence:
> From: Tudor Ambarus <tudor.ambarus@microchip.com>
>
[…]
> @@ -726,18 +1411,32 @@ static int atmel_qspi_probe(struct platform_device *pdev)
> "failed to enable the QSPI system clock\n");
> goto disable_pclk;
> }
> + } else if (aq->caps->has_gclk) {
> + /* Get the QSPI generic clock */
> + aq->gclk = devm_clk_get(&pdev->dev, "gclk");
> + if (IS_ERR(aq->gclk)) {
> + dev_err(&pdev->dev, "missing Generic clock\n");
> + err = PTR_ERR(aq->gclk);
> + goto disable_pclk;
> + }
> + }
> +
> + if (aq->caps->has_dma) {
> + err = atmel_qspi_dma_init(ctrl);
> + if (err == -EPROBE_DEFER)
> + goto disable_qspick;
> }
>
> /* Request the IRQ */
> irq = platform_get_irq(pdev, 0);
> if (irq < 0) {
> err = irq;
> - goto disable_qspick;
> + goto dma_release;
> }
> err = devm_request_irq(&pdev->dev, irq, atmel_qspi_interrupt,
> 0, dev_name(&pdev->dev), aq);
> if (err)
> - goto disable_qspick;
> + goto dma_release;
>
> pm_runtime_set_autosuspend_delay(&pdev->dev, 500);
> pm_runtime_use_autosuspend(&pdev->dev);
> @@ -745,7 +1444,9 @@ static int atmel_qspi_probe(struct platform_device *pdev)
> pm_runtime_enable(&pdev->dev);
> pm_runtime_get_noresume(&pdev->dev);
>
> - atmel_qspi_init(aq);
> + err = atmel_qspi_init(aq);
> + if (err)
> + goto dma_release;
This error handling leads to unbalanced pm_runtime right? The block
below rolls back pm_runtime before jumping to 'dma_release', this here
does not.
> err = spi_register_controller(ctrl);
> if (err) {
> @@ -753,13 +1454,16 @@ static int atmel_qspi_probe(struct platform_device *pdev)
> pm_runtime_disable(&pdev->dev);
> pm_runtime_set_suspended(&pdev->dev);
> pm_runtime_dont_use_autosuspend(&pdev->dev);
> - goto disable_qspick;
> + goto dma_release;
> }
This hunk got it right?
> pm_runtime_mark_last_busy(&pdev->dev);
> pm_runtime_put_autosuspend(&pdev->dev);
>
> return 0;
>
> +dma_release:
> + if (aq->caps->has_dma)
> + atmel_qspi_dma_release(aq);
> disable_qspick:
> clk_disable_unprepare(aq->qspick);
> disable_pclk:
> @@ -768,6 +1472,44 @@ static int atmel_qspi_probe(struct platform_device *pdev)
> return err;
> }
I think this is another issue of forwarding porting. The pm_runtime
stuff was added in mainline after the original patch was forked of,
and not entirely considered when porting?
Greets
Alex
next prev parent reply other threads:[~2025-01-10 7:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 17:43 [PATCH v3 0/2] spi: atmel-quadspi: Refactor to allow supporting SAMA7G5 O/QSPI Csókás, Bence
2024-11-28 17:43 ` [PATCH v3 1/2] spi: atmel-quadspi: Create `atmel_qspi_ops` to support newer SoC families Csókás, Bence
2024-11-28 17:43 ` [PATCH v3 2/2] spi: atmel-quadspi: Add support for sama7g5 QSPI Csókás, Bence
2024-12-18 9:32 ` Alexander Dahl
2025-01-09 16:27 ` Alexander Dahl
2025-01-09 16:41 ` Mark Brown
2025-01-10 10:40 ` Alexander Dahl
2025-01-14 17:13 ` Csókás Bence
2025-01-10 7:56 ` Alexander Dahl [this message]
2025-01-14 17:21 ` Csókás Bence
2024-12-17 18:27 ` [PATCH v3 0/2] spi: atmel-quadspi: Refactor to allow supporting SAMA7G5 O/QSPI Mark Brown
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=20250110-paycheck-irregular-bcddab1276c7@thorsis.com \
--to=ada@thorsis.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=csokas.bence@prolan.hu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=tudor.ambarus@microchip.com \
--cc=varshini.rajendran@microchip.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;
as well as URLs for NNTP newsgroup(s).