linux-kernel - Re: [PATCH] spi: s3c64xx: requests spi-dma channel only during data transfer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 07 Jun 2022 11:46:38 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-arm-kernel@...ts.infradead.org, adithya.kv@...sung.com,
        linux-spi@...r.kernel.org
Cc:     alim.akhtar@...sung.com, linux-kernel@...r.kernel.org,
        andi@...zian.org, krzysztof.kozlowski@...aro.org,
        linux-samsung-soc@...r.kernel.org, pankaj.dubey@...sung.com
Subject: Re: [PATCH] spi: s3c64xx: requests spi-dma channel only during data transfer

On Tue, 24 May 2022 19:31:32 +0530, Adithya K V wrote:
> Current s3c64xx SPI driver acquires DMA channel during driver
> probe and holds on it even when channels are not used
> (no DMA transfer). This is a problem especially when all the
> DMA channels are exhausted (as other IPs on the same DMA
> controller also acquires DMA channel) and if a new IP/Device
> requests for a DMA channel (on the same DMA controller), it won’t
> get DMA channel allocated.
> The said issue can be avoided if s3c64xx driver request and
> release DMA channel before and after data transfer. Let’s modify
> the driver to request and release DMA channel before and after
> DMA mode data transfer.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: s3c64xx: requests spi-dma channel only during data transfer
      commit: f52b03c707444c5a3d1a0b9c5724f93ddc3c588e

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