mbox series

[0/3] Drop dma-coherent property from SA2UL

Message ID 20221031152520.355653-1-j-choudhary@ti.com (mailing list archive)
Headers show
Series Drop dma-coherent property from SA2UL | expand

Message

Jayesh Choudhary Oct. 31, 2022, 3:25 p.m. UTC 
crypto driver itself is not dma-coherent. It is the system-dma
that moves data and so 'dma-coherent' property should be dropped.

This series drop it from the crypto nodes for the J7 family of
TI SoCs.

DT binding fixes have already been merged[0].

[0]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a536208da6f7d877f1adbad4ff13f63f31f59d91

Jayesh Choudhary (3):
  arm64: dts: ti: k3-am65-main: drop dma-coherent in crypto node
  arm64: dts: ti: k3-j721e-main: drop dma-coherent in crypto node
  arm64: dts: ti: k3-j7200-mcu-wakeup: drop dma-coherent in crypto node

 arch/arm64/boot/dts/ti/k3-am65-main.dtsi        | 1 -
 arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 1 -
 arch/arm64/boot/dts/ti/k3-j721e-main.dtsi       | 1 -
 3 files changed, 3 deletions(-)

Comments

Nishanth Menon Nov. 15, 2022, 8:22 p.m. UTC | #1 
Hi Jayesh Choudhary,

On Mon, 31 Oct 2022 20:55:17 +0530, Jayesh Choudhary wrote:
> crypto driver itself is not dma-coherent. It is the system-dma
> that moves data and so 'dma-coherent' property should be dropped.
> 
> This series drop it from the crypto nodes for the J7 family of
> TI SoCs.
> 
> DT binding fixes have already been merged[0].
> 
> [...]

(note: I picked up Manorit's reviewed-by as well)

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/3] arm64: dts: ti: k3-am65-main: drop dma-coherent in crypto node
      commit: b86833ab3653dbb0dc453eec4eef8615e63de4e2
[2/3] arm64: dts: ti: k3-j721e-main: drop dma-coherent in crypto node
      commit: 26c5012403f3f1fd3bf8f7d3389ee539ae5cc162
[3/3] arm64: dts: ti: k3-j7200-mcu-wakeup: drop dma-coherent in crypto node
      commit: f00f26711d7183f8675c5591ba8daaabe94be452

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant 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.

[1] git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git