From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jisheng Zhang <jszhang@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Robin Murphy <robin.murphy@arm.com>
Cc: dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 14/14] dmaengine: dma350: Support ARM DMA-250
Date: Sat, 23 Aug 2025 18:13:14 +0200 [thread overview]
Message-ID: <8995c33a-8ff2-4fec-8849-73f18d04a3ab@kernel.org> (raw)
In-Reply-To: <20250823154009.25992-15-jszhang@kernel.org>
On 23/08/2025 17:40, Jisheng Zhang wrote:
> struct device *dev = &pdev->dev;
> @@ -893,8 +1262,9 @@ static int d350_probe(struct platform_device *pdev)
> r = FIELD_GET(IIDR_VARIANT, reg);
> p = FIELD_GET(IIDR_REVISION, reg);
> if (FIELD_GET(IIDR_IMPLEMENTER, reg) != IMPLEMENTER_ARM ||
> - FIELD_GET(IIDR_PRODUCTID, reg) != PRODUCTID_DMA350)
> - return dev_err_probe(dev, -ENODEV, "Not a DMA-350!");
> + ((FIELD_GET(IIDR_PRODUCTID, reg) != PRODUCTID_DMA350) &&
> + FIELD_GET(IIDR_PRODUCTID, reg) != PRODUCTID_DMA250))
> + return dev_err_probe(dev, -ENODEV, "Not a DMA-350/DMA-250!");
>
> reg = readl_relaxed(base + DMAINFO + DMA_BUILDCFG0);
> nchan = FIELD_GET(DMA_CFG_NUM_CHANNELS, reg) + 1;
> @@ -917,13 +1287,38 @@ static int d350_probe(struct platform_device *pdev)
> return ret;
> }
>
> + if (device_is_compatible(dev, "arm,dma-250")) {
No, don't sprinkle compatibles through driver code. driver match data is
for that.
> + u32 cfg2;
> + int secext_present;
> +
> + dmac->is_d250 = true;
> +
> + cfg2 = readl_relaxed(base + DMAINFO + DMA_BUILDCFG2);
> + secext_present = (cfg2 & DMA_CFG_HAS_TZ) ? 1 : 0;
> + dmac->cntx_mem_size = nchan * 64 * (1 + secext_present);
> + dmac->cntx_mem = dma_alloc_coherent(dev, dmac->cntx_mem_size,
> + &dmac->cntx_mem_paddr,
> + GFP_KERNEL);
> + if (!dmac->cntx_mem)
> + return dev_err_probe(dev, -ENOMEM, "Failed to alloc context memory\n");
> +
> + ret = devm_add_action_or_reset(dev, d250_cntx_mem_release, dmac);
> + if (ret) {
> + dma_free_coherent(dev, dmac->cntx_mem_size,
> + dmac->cntx_mem, dmac->cntx_mem_paddr);
> + return ret;
> + }
> + writel_relaxed(dmac->cntx_mem_paddr, base + DMANSECCTRL + NSEC_CNTXBASE);
> + }
> +
> dma_set_mask_and_coherent(dev, DMA_BIT_MASK(aw));
> coherent = device_get_dma_attr(dev) == DEV_DMA_COHERENT;
>
> reg = readl_relaxed(base + DMAINFO + DMA_BUILDCFG1);
> dmac->nreq = FIELD_GET(DMA_CFG_NUM_TRIGGER_IN, reg);
>
> - dev_dbg(dev, "DMA-350 r%dp%d with %d channels, %d requests\n", r, p, dmac->nchan, dmac->nreq);
> + dev_info(dev, "%s r%dp%d with %d channels, %d requests\n",
> + dmac->is_d250 ? "DMA-250" : "DMA-350", r, p, dmac->nchan, dmac->nreq);
No, don't makek drivers more verbose. Please follow Linux driver
design/coding style - this should be silent on success.
>
> for (int i = min(dw, 16); i > 0; i /= 2) {
> dmac->dma.src_addr_widths |= BIT(i);
> @@ -935,7 +1330,10 @@ static int d350_probe(struct platform_device *pdev)
> dmac->dma.device_alloc_chan_resources = d350_alloc_chan_resources;
> dmac->dma.device_free_chan_resources = d350_free_chan_resources;
> dma_cap_set(DMA_MEMCPY, dmac->dma.cap_mask);
> - dmac->dma.device_prep_dma_memcpy = d350_prep_memcpy;
> + if (dmac->is_d250)
> + dmac->dma.device_prep_dma_memcpy = d250_prep_memcpy;
> + else
> + dmac->dma.device_prep_dma_memcpy = d350_prep_memcpy;
> dmac->dma.device_pause = d350_pause;
> dmac->dma.device_resume = d350_resume;
> dmac->dma.device_terminate_all = d350_terminate_all;
> @@ -971,8 +1369,8 @@ static int d350_probe(struct platform_device *pdev)
> return dch->irq;
>
> dch->has_wrap = FIELD_GET(CH_CFG_HAS_WRAP, reg);
> - dch->has_trig = FIELD_GET(CH_CFG_HAS_TRIGIN, reg) &
> - FIELD_GET(CH_CFG_HAS_TRIGSEL, reg);
> + dch->has_xsizehi = FIELD_GET(CH_CFG_HAS_XSIZEHI, reg);
> + dch->has_trig = FIELD_GET(CH_CFG_HAS_TRIGIN, reg);
>
> /* Fill is a special case of Wrap */
> memset &= dch->has_wrap;
> @@ -994,8 +1392,13 @@ static int d350_probe(struct platform_device *pdev)
> dma_cap_set(DMA_SLAVE, dmac->dma.cap_mask);
> dma_cap_set(DMA_CYCLIC, dmac->dma.cap_mask);
> dmac->dma.device_config = d350_slave_config;
> - dmac->dma.device_prep_slave_sg = d350_prep_slave_sg;
> - dmac->dma.device_prep_dma_cyclic = d350_prep_cyclic;
> + if (dmac->is_d250) {
> + dmac->dma.device_prep_slave_sg = d250_prep_slave_sg;
> + dmac->dma.device_prep_dma_cyclic = d250_prep_cyclic;
> + } else {
> + dmac->dma.device_prep_slave_sg = d350_prep_slave_sg;
> + dmac->dma.device_prep_dma_cyclic = d350_prep_cyclic;
> + }
> }
>
> if (memset) {
> @@ -1019,6 +1422,7 @@ static void d350_remove(struct platform_device *pdev)
>
> static const struct of_device_id d350_of_match[] __maybe_unused = {
> { .compatible = "arm,dma-350" },
> + { .compatible = "arm,dma-250" },
And based on that devices would be compatible...
BTW, incorrect order - 2 < 3.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-23 16:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 15:39 [PATCH 00/14] dmaengine: dma350: Support slave_sg, cyclic and DMA-250 Jisheng Zhang
2025-08-23 15:39 ` [PATCH 01/14] dmaengine: dma350: Fix CH_CTRL_USESRCTRIGIN definition Jisheng Zhang
2025-08-29 10:44 ` Robin Murphy
2025-08-23 15:39 ` [PATCH 02/14] dmaengine: dma350: Add missing dch->coherent setting Jisheng Zhang
2025-08-29 10:52 ` Robin Murphy
2025-08-23 15:39 ` [PATCH 03/14] dmaengine: dma350: Check vchan_next_desc() return value Jisheng Zhang
2025-08-29 10:02 ` Robin Murphy
2025-08-23 15:39 ` [PATCH 04/14] dmaengine: dma350: Check dma_cookie_status() ret code and txstate Jisheng Zhang
2025-08-29 10:42 ` Robin Murphy
2025-08-23 15:40 ` [PATCH 05/14] dmaengine: dma350: Register the DMA controller to DT DMA helpers Jisheng Zhang
2025-08-29 20:37 ` Robin Murphy
2025-08-23 15:40 ` [PATCH 06/14] dmaengine: dma350: Use dmaenginem_async_device_register Jisheng Zhang
2025-08-23 15:40 ` [PATCH 07/14] dmaengine: dma350: Remove redundant err msg if platform_get_irq() fails Jisheng Zhang
2025-08-23 15:40 ` [PATCH 08/14] dt-bindings: dma: dma350: Document interrupt-names Jisheng Zhang
2025-08-23 16:09 ` Krzysztof Kozlowski
2025-08-24 9:49 ` Jisheng Zhang
2025-08-24 10:30 ` Krzysztof Kozlowski
2025-08-24 13:19 ` Jisheng Zhang
2025-08-29 11:08 ` Robin Murphy
2025-08-23 15:40 ` [PATCH 09/14] dmaengine: dma350: Support dma-channel-mask Jisheng Zhang
2025-08-23 16:10 ` Krzysztof Kozlowski
2025-08-24 7:01 ` kernel test robot
2025-08-23 15:40 ` [PATCH 10/14] dmaengine: dma350: Alloc command[] from dma pool Jisheng Zhang
2025-08-29 12:56 ` Robin Murphy
2025-09-01 10:27 ` Dan Carpenter
2025-08-23 15:40 ` [PATCH 11/14] dmaengine: dma350: Support device_prep_slave_sg Jisheng Zhang
2025-08-30 0:00 ` Robin Murphy
2025-08-23 15:40 ` [PATCH 12/14] dmaengine: dma350: Support device_prep_dma_cyclic Jisheng Zhang
2025-08-23 15:40 ` [PATCH 13/14] dt-bindings: dma: dma350: Support ARM DMA-250 Jisheng Zhang
2025-08-23 16:11 ` Krzysztof Kozlowski
2025-08-29 11:16 ` Robin Murphy
2025-08-23 15:40 ` [PATCH 14/14] dmaengine: " Jisheng Zhang
2025-08-23 16:13 ` Krzysztof Kozlowski [this message]
2025-08-24 19:38 ` kernel test robot
2025-08-29 22:24 ` Robin Murphy
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=8995c33a-8ff2-4fec-8849-73f18d04a3ab@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jszhang@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®