On Fri, Jun 30, 2023 at 11:08:41AM +0530, Sarath Babu Naidu Gaddam wrote: > The axiethernet driver can use the dmaengine framework to communicate > with the xilinx DMAengine driver(AXIDMA, MCDMA). The inspiration behind > this dmaengine adoption is to reuse the in-kernel xilinx dma engine > driver[1] and remove redundant dma programming sequence[2] from the > ethernet driver. This simplifies the ethernet driver and also makes > it generic to be hooked to any complaint dma IP i.e AXIDMA, MCDMA > without any modification. > > The dmaengine framework was extended for metadata API support during > the axidma RFC[3] discussion. However, it still needs further > enhancements to make it well suited for ethernet usecases. > > Backward compatibility support: > To support backward compatibility, we are planning to use below approach, > 1) Use "dmas" property as an optional for now to differentiate > dmaengine based ethernet Driver or built-in dma ethernet driver. > Will move this property to required property some time later. > 2) after some time, will introduce a new compatible string to support > the dmaengine method, This new compatible name will use different > APIs for init and data transfer. > > Comments, suggestions, thoughts to implement remaining functional > features are very welcome! Hi Sarath, unfortunately this series doesn't apply on net-next. net-next is currently closed. So please provide a v5 once it reposts, after 10th July. On the other hand, RFCs are welcome any time. See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development -- pw-bot: changes-requested
