From: Vinod Koul <vkoul@kernel.org>
To: Robert Marko <robert.marko@sartura.hr>
Cc: ludovic.desroches@microchip.com,
linux-arm-kernel@lists.infradead.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, daniel.machon@microchip.com,
luka.perkov@sartura.hr, Tony Han <tony.han@microchip.com>
Subject: Re: [PATCH RESEND] dmaengine: at_xdmac: get the number of DMA channels from device tree
Date: Tue, 16 Dec 2025 20:48:17 +0530 [thread overview]
Message-ID: <aUF4OS4DsmRlQQt3@vaman> (raw)
In-Reply-To: <20251203121208.1269487-1-robert.marko@sartura.hr>
On 03-12-25, 13:11, Robert Marko wrote:
> From: Tony Han <tony.han@microchip.com>
>
> In case of kernel runs in non-secure mode, the number of DMA channels can
> be got from device tree since the value read from GTYPE register is "0" as
> it's always secured.
>
> As the number of channels can never be negative, update them to the type
> "unsigned".
>
> This is required for LAN969x.
You updated the changelog, but tagged it as resend. It should be v2!
>
> Signed-off-by: Tony Han <tony.han@microchip.com>
> Signed-off-by: Robert Marko <robert.marko@sartura.hr>
> ---
> drivers/dma/at_xdmac.c | 26 +++++++++++++++++++++++---
> 1 file changed, 23 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/dma/at_xdmac.c b/drivers/dma/at_xdmac.c
> index 3fbc74710a13..acabf82e293c 100644
> --- a/drivers/dma/at_xdmac.c
> +++ b/drivers/dma/at_xdmac.c
> @@ -2257,12 +2257,29 @@ static int __maybe_unused atmel_xdmac_runtime_resume(struct device *dev)
> return clk_enable(atxdmac->clk);
> }
>
> +static inline int at_xdmac_get_channel_number(struct platform_device *pdev,
> + u32 reg, u32 *pchannels)
> +{
> + int ret;
> +
> + if (reg) {
> + *pchannels = AT_XDMAC_NB_CH(reg);
> + return 0;
> + }
> +
> + ret = of_property_read_u32(pdev->dev.of_node, "dma-channels", pchannels);
> + if (ret)
> + dev_err(&pdev->dev, "can't get number of channels\n");
Do we need to log error, I thought the API did that...
> +
> + return ret;
> +}
> +
> static int at_xdmac_probe(struct platform_device *pdev)
> {
> struct at_xdmac *atxdmac;
> - int irq, nr_channels, i, ret;
> + int irq, ret;
> void __iomem *base;
> - u32 reg;
> + u32 nr_channels, i, reg;
>
> irq = platform_get_irq(pdev, 0);
> if (irq < 0)
> @@ -2278,7 +2295,10 @@ static int at_xdmac_probe(struct platform_device *pdev)
> * of channels to do the allocation.
> */
> reg = readl_relaxed(base + AT_XDMAC_GTYPE);
> - nr_channels = AT_XDMAC_NB_CH(reg);
> + ret = at_xdmac_get_channel_number(pdev, reg, &nr_channels);
> + if (ret)
> + return ret;
> +
> if (nr_channels > AT_XDMAC_MAX_CHAN) {
> dev_err(&pdev->dev, "invalid number of channels (%u)\n",
> nr_channels);
> --
> 2.52.0
--
~Vinod
next prev parent reply other threads:[~2025-12-16 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 12:11 [PATCH RESEND] dmaengine: at_xdmac: get the number of DMA channels from device tree Robert Marko
2025-12-16 15:18 ` Vinod Koul [this message]
2025-12-30 13:19 ` Robert Marko
2026-01-01 17:41 ` Vinod Koul
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=aUF4OS4DsmRlQQt3@vaman \
--to=vkoul@kernel.org \
--cc=daniel.machon@microchip.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=luka.perkov@sartura.hr \
--cc=robert.marko@sartura.hr \
--cc=tony.han@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).