public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@corigine.com>
To: Sarath Babu Naidu Gaddam <sarath.babu.naidu.gaddam@amd.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, sbhatta@marvell.com,
	linux@armlinux.org.uk, michal.simek@amd.com,
	radhey.shyam.pandey@amd.com, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, anirudha.sarangi@amd.com,
	harini.katakam@amd.com, git@amd.com
Subject: Re: [PATCH net-next V4 0/3] net: axienet: Introduce dmaengine
Date: Fri, 30 Jun 2023 13:56:44 +0200	[thread overview]
Message-ID: <ZJ7C/Ck02QN7+X2/@corigine.com> (raw)
In-Reply-To: <20230630053844.1366171-1-sarath.babu.naidu.gaddam@amd.com>

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

      parent reply	other threads:[~2023-06-30 11:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30  5:38 [PATCH net-next V4 0/3] net: axienet: Introduce dmaengine Sarath Babu Naidu Gaddam
2023-06-30  5:38 ` [PATCH net-next V4 1/3] dt-bindings: net: xlnx,axi-ethernet: Introduce DMA support Sarath Babu Naidu Gaddam
2023-06-30 16:46   ` Rob Herring
2023-06-30  5:38 ` [PATCH net-next V4 2/3] net: axienet: Preparatory changes for dmaengine support Sarath Babu Naidu Gaddam
2023-06-30  5:38 ` [PATCH net-next V4 3/3] net: axienet: Introduce " Sarath Babu Naidu Gaddam
2023-06-30 11:56 ` Simon Horman [this message]

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=ZJ7C/Ck02QN7+X2/@corigine.com \
    --to=simon.horman@corigine.com \
    --cc=anirudha.sarangi@amd.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=git@amd.com \
    --cc=harini.katakam@amd.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michal.simek@amd.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=radhey.shyam.pandey@amd.com \
    --cc=robh+dt@kernel.org \
    --cc=sarath.babu.naidu.gaddam@amd.com \
    --cc=sbhatta@marvell.com \
    /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