[PATCH] spi: rockchip-sfc: Fix DMA-API usage

[Mark Brown]

On Fri, 03 Oct 2025 13:42:39 +0200, Marek Szyprowski wrote:
> Use DMA-API dma_map_single() call for getting the DMA address of the
> transfer buffer instead of hacking with virt_to_phys().
> 
> This fixes the following DMA-API debug warning:
> ------------[ cut here ]------------
> DMA-API: rockchip-sfc fe300000.spi: device driver tries to sync DMA memory it has not allocated [device address=0x000000000cf70000] [size=288 bytes]
> WARNING: kernel/dma/debug.c:1106 at check_sync+0x1d8/0x690, CPU#2: systemd-udevd/151
> Modules linked in: ...
> Hardware name: Hardkernel ODROID-M1 (DT)
> pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> pc : check_sync+0x1d8/0x690
> lr : check_sync+0x1d8/0x690
> ..
> Call trace:
>  check_sync+0x1d8/0x690 (P)
>  debug_dma_sync_single_for_cpu+0x84/0x8c
>  __dma_sync_single_for_cpu+0x88/0x234
>  rockchip_sfc_exec_mem_op+0x4a0/0x798 [spi_rockchip_sfc]
>  spi_mem_exec_op+0x408/0x498
>  spi_nor_read_data+0x170/0x184
>  spi_nor_read_sfdp+0x74/0xe4
>  spi_nor_parse_sfdp+0x120/0x11f0
>  spi_nor_sfdp_init_params_deprecated+0x3c/0x8c
>  spi_nor_scan+0x690/0xf88
>  spi_nor_probe+0xe4/0x304
>  spi_mem_probe+0x6c/0xa8
>  spi_probe+0x94/0xd4
>  really_probe+0xbc/0x298
>  ...
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: rockchip-sfc: Fix DMA-API usage
      commit: ee795e82e10197c070efd380dc9615c73dffad6c

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark