linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: apeksha.gupta@nxp.com
Cc: LnxRevLi@nxp.com, davem@davemloft.net, hemant.agrawal@nxp.com,
	kuba@kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, nipun.gupta@nxp.com,
	qiangqing.zhang@nxp.com, sachin.saxena@nxp.com,
	Michael Walle <michael@walle.cc>
Subject: Re: [PATCH 0/5] drivers/net: add NXP FEC-UIO driver
Date: Thu, 11 Nov 2021 12:06:42 +0100	[thread overview]
Message-ID: <20211111110642.3340300-1-michael@walle.cc> (raw)
In-Reply-To: <20211110054838.27907-1-apeksha.gupta@nxp.com>

[linux-devel@linux.nxdi.nxp.com doesn't exist in the public, which is quite
annoying when you reply to an email and the MTA doesn't accept it due to
invalid domains]

> This patch series introduce the fec-uio driver, supported for the inbuilt
> NIC found in the NXP i.MX 8M Mini SoC. Basic hardware initialization is
> performed in kernel via userspace input/output(UIO) to support FEC
> ethernet device detection in user space.

Could you elaborate for what this driver is needed? Doesn't the imx8mm
already have a network driver? What is the difference between them?

As a user, I couldn't find what this is all about, neither in this
commit message nor in the Kconfig help text.

> Userspace PMD uses standard UIO interface to access kernel for PHY
> initialisation and for mapping the allocated memory of register &
> buffer descriptor with DPDK which gives access to non-cacheable memory
> for buffer descriptor.
> 
> Module fec-uio.ko will get generated.
> imx8mm-evk-dpdk.dtb is required to support fec-uio driver.

-michael

      parent reply	other threads:[~2021-11-11 11:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10  5:48 [PATCH 0/5] drivers/net: add NXP FEC-UIO driver Apeksha Gupta
2021-11-10  5:48 ` [PATCH 1/5] dt-bindings: add binding for fec-uio Apeksha Gupta
2021-11-10  5:48 ` [PATCH 2/5] net: fec: fec-uio driver Apeksha Gupta
2021-11-10 22:06   ` Andrew Lunn
2021-11-10  5:48 ` [PATCH 3/5] ARM64: defconfig: Add config for fec-uio Apeksha Gupta
2021-11-10  5:48 ` [PATCH 4/5] MAINTAINERS: add new file Apeksha Gupta
2021-11-10  5:48 ` [PATCH 5/5] arm64: dts: imx8mm-evk-dpdk: dts for fec-uio driver Apeksha Gupta
2021-11-10 22:11   ` Andrew Lunn
2021-11-11 11:06 ` Michael Walle [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=20211111110642.3340300-1-michael@walle.cc \
    --to=michael@walle.cc \
    --cc=LnxRevLi@nxp.com \
    --cc=apeksha.gupta@nxp.com \
    --cc=davem@davemloft.net \
    --cc=hemant.agrawal@nxp.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nipun.gupta@nxp.com \
    --cc=qiangqing.zhang@nxp.com \
    --cc=sachin.saxena@nxp.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;
as well as URLs for NNTP newsgroup(s).