public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: Peng Fan <peng.fan@oss.nxp.com>
Cc: Vinod Koul <vkoul@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Jiada Wang <jiada_wang@mentor.com>,
	dmaengine@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 02/10] dmaengine: imx-sdma: fix spba-bus handling for i.MX8M
Date: Fri, 12 Sep 2025 10:48:09 +0200	[thread overview]
Message-ID: <20250912084809.e6atdywisk4ywlr6@pengutronix.de> (raw)
In-Reply-To: <20250912030223.GB5808@nxa18884-linux.ap.freescale.net>

Hi Peng,

On 25-09-12, Peng Fan wrote:
> Hi Marco,
> 
> On Thu, Sep 11, 2025 at 11:56:43PM +0200, Marco Felsch wrote:
> >Starting with i.MX8M* devices there are multiple spba-busses so we can't
> >just search the whole DT for the first spba-bus match and take it.
> >Instead we need to check for each device to which bus it belongs and
> >setup the spba_{start,end}_addr accordingly per sdma_channel.
> 
> Could you please explain a bit why it is per sdma_channel, not per sdma_engine?

Well first, the sdma-slave/user defines which SPBA bus is used.
Furthermore not all users have to be part of the same SPBA bus or be
part of a SPBA bus at all. E.g. the i.mx8mm.dtsi sdma1 engine is used
by uart4 (not part of a SPBA bus) and uart1/2/3 (part of the
spba-bus@30800000).

I know that the use-case: "The SDMA engine can serve for multiple users
which are not part of the same SPBA bus" is not yet used but having the
code in place makes the driver more future proof.

Therefore I think having the SPBA addresses per user is correct.

Regards,
  Marco

> As I understand, all the channels belong to a sdma engine should use same
> spba_{start,end}_addr.
> 
> Thanks,
> Peng
> 


  reply	other threads:[~2025-09-12  8:48 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11 21:56 [PATCH v2 00/10] i.MX SDMA cleanups and fixes Marco Felsch
2025-09-11 21:56 ` [PATCH v2 01/10] dmaengine: imx-sdma: fix missing of_dma_controller_free() Marco Felsch
2025-09-12  2:59   ` Peng Fan
2025-09-12 14:39   ` Frank Li
2025-09-11 21:56 ` [PATCH v2 02/10] dmaengine: imx-sdma: fix spba-bus handling for i.MX8M Marco Felsch
2025-09-12  3:02   ` Peng Fan
2025-09-12  8:48     ` Marco Felsch [this message]
2025-09-12 15:18   ` Frank Li
2025-09-12 15:27     ` Marco Felsch
2025-09-12 16:57       ` Frank Li
2025-10-01 10:31         ` Marco Felsch
2025-09-16  2:01   ` Peng Fan
2026-04-02  3:33   ` Shengjiu Wang
2025-09-11 21:56 ` [PATCH v2 03/10] dmaengine: imx-sdma: drop legacy device_node np check Marco Felsch
2025-09-12  3:04   ` Peng Fan
2025-09-11 21:56 ` [PATCH v2 04/10] dmaengine: imx-sdma: sdma_remove minor cleanups Marco Felsch
2025-09-12  3:06   ` Peng Fan
2025-09-11 21:56 ` [PATCH v2 05/10] dmaengine: imx-sdma: cosmetic cleanup Marco Felsch
2025-09-12  3:09   ` Peng Fan
2025-09-11 21:56 ` [PATCH v2 06/10] dmaengine: imx-sdma: make use of devm_kzalloc for script_addrs Marco Felsch
2025-09-12  4:00   ` Peng Fan
2025-09-11 21:56 ` [PATCH v2 07/10] dmaengine: imx-sdma: make use of devm_clk_get_prepared() Marco Felsch
2025-09-12  4:02   ` Peng Fan
2025-09-11 21:56 ` [PATCH v2 08/10] dmaengine: imx-sdma: make use of devm_add_action_or_reset to unregiser the dma_device Marco Felsch
2025-09-12  4:02   ` Peng Fan
2025-09-12 14:49   ` Frank Li
2025-09-12 15:25     ` Marco Felsch
2025-09-12 16:37       ` Frank Li
2025-09-12 16:49         ` Marco Felsch
2025-09-11 21:56 ` [PATCH v2 09/10] dmaengine: imx-sdma: make use of devm_add_action_or_reset to unregiser the dma-controller Marco Felsch
2025-09-12  4:06   ` Peng Fan
2025-09-12 14:50   ` Frank Li
2025-09-12 15:28     ` Marco Felsch
2025-09-12 16:39       ` Frank Li
2025-09-11 21:56 ` [PATCH v2 10/10] dmaengine: imx-sdma: make use of dev_err_probe() Marco Felsch
2025-09-12  4:07   ` Peng Fan
2026-02-25 15:59 ` [PATCH v2 00/10] i.MX SDMA cleanups and fixes Frank Li
2026-02-25 17:05   ` Marco Felsch

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=20250912084809.e6atdywisk4ywlr6@pengutronix.de \
    --to=m.felsch@pengutronix.de \
    --cc=dmaengine@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=jiada_wang@mentor.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@oss.nxp.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --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