All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: <vkoul@kernel.org>, <devicetree@vger.kernel.org>,
	<dmaengine@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/2] dmaengine: Add Arm DMA-350 driver
Date: Thu, 17 Apr 2025 18:07:22 +0100	[thread overview]
Message-ID: <20250417180722.00002465@huawei.com> (raw)
In-Reply-To: <6d7d8efefa935d34977b59a74797ab377528db94.1741780808.git.robin.murphy@arm.com>

On Wed, 12 Mar 2025 12:05:10 +0000
Robin Murphy <robin.murphy@arm.com> wrote:

> Add an initial driver for the Arm Corelink DMA-350 controller, to
> support basic mem-to-mem async_tx. The design here leaves room for more
> fun things like peripheral support and scatter-gather chaining to come
> in future.
> 
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
> v2:
>  - Fix build warnings
>  - Limit retries for reading live residue
Drive by review as I was curious...

Few things inline but it's been too long since I last looked
at a DMA driver to give a detailed review.

Jonathan

> +
> +static int d350_probe(struct platform_device *pdev)
> +{



> +
> +	platform_set_drvdata(pdev, dmac);
If you used the managed form of register, I don't think you need this?
> +
> +	ret = dma_async_device_register(&dmac->dma);

This is pretty noisy on most non -ENOMEM errors anyway. Is it worth another
layer of error print?

> +	if (ret)
> +		return dev_err_probe(dev, ret, "Failed to register DMA device\n");
> +
> +	return 0;
> +}
> +
> +static void d350_remove(struct platform_device *pdev)
> +{
> +	struct d350 *dmac = platform_get_drvdata(pdev);
> +
> +	dma_async_device_unregister(&dmac->dma);

dmaenginem_async_device_register() and get rid of remove.

J



> +}



  reply	other threads:[~2025-04-17 17:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12 12:05 [PATCH v2 0/2] dmaengine: Add Arm DMA-350 driver Robin Murphy
2025-03-12 12:05 ` [PATCH v2 1/2] dt-bindings: dma: Add Arm DMA-350 Robin Murphy
2025-03-12 12:05 ` [PATCH v2 2/2] dmaengine: Add Arm DMA-350 driver Robin Murphy
2025-04-17 17:07   ` Jonathan Cameron [this message]
2025-04-17 15:18 ` [PATCH v2 0/2] " 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=20250417180722.00002465@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robin.murphy@arm.com \
    --cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.