linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xu Yilun <yilun.xu@intel.com>
To: Tianfei Zhang <tianfei.zhang@intel.com>
Cc: hao.wu@intel.com, trix@redhat.com, mdf@kernel.org,
	linux-fpga@vger.kernel.org, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org,
	Matthew Gerlach <matthew.gerlach@linux.intel.com>
Subject: Re: [PATCH v2] uio: dfl: add HSSI feature id
Date: Sat, 16 Apr 2022 22:47:52 +0800	[thread overview]
Message-ID: <20220416144752.GA301222@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <20220412062353.53984-1-tianfei.zhang@intel.com>

On Tue, Apr 12, 2022 at 02:23:53AM -0400, Tianfei Zhang wrote:
> From: Matthew Gerlach <matthew.gerlach@linux.intel.com>
> 
> Add the feature id of the OFS HSSI (High Speed Serial Interface)
> subsystem to table of ids supported by the uio_dfl driver. HSSI
> subsystem consists of harden/soft Ethernet MAC to support various
> ethernet usages and PCS/FEC/PMA direct modes for non-ethernet usages.
> 
> We leverage the uio_dfl driver to access the HSSI subsystem on user space,
> because the HSSI subsystem was designed for specific purposes and does

Could you explain what's the main difference between this MAC and other
MACs, which prevents it from fitting into net kernel subsystem?

For FME_FEATURE_ID_ETH_GROUP, it is not designed as the full functional
ethernet controller. It is specially developed for the Intel N3000 NIC.
Since it is an FPGA based card, it is designed for the users to runtime
reload part of the MAC layer logic developed by themselves, while the ETH
GROUP is another part of the MAC which is not expected to be reloaded by
customers, but it provides some configurations for software to work with
the user logic.

And what's the difference for the FME_FEATURE_ID_OFS_HSSI?

Thanks,
Yilun

> not fit into the standard MAC and net kernel subsystems.
> 
> The Feature ID table of DFL can be found:
> https://github.com/OPAE/dfl-feature-id
> 
> Signed-off-by: Matthew Gerlach <matthew.gerlach@linux.intel.com>
> Signed-off-by: Tianfei Zhang <tianfei.zhang@intel.com>
> ---
> v2: add HSSI introduction and the git repo of Feature ID table.
> ---
>  drivers/uio/uio_dfl.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/uio/uio_dfl.c b/drivers/uio/uio_dfl.c
> index 89c0fc7b0cbc..660e1d0bf6b9 100644
> --- a/drivers/uio/uio_dfl.c
> +++ b/drivers/uio/uio_dfl.c
> @@ -45,9 +45,11 @@ static int uio_dfl_probe(struct dfl_device *ddev)
>  }
>  
>  #define FME_FEATURE_ID_ETH_GROUP	0x10
> +#define FME_FEATURE_ID_OFS_HSSI		0x15
>  
>  static const struct dfl_device_id uio_dfl_ids[] = {
>  	{ FME_ID, FME_FEATURE_ID_ETH_GROUP },
> +	{ FME_ID, FME_FEATURE_ID_OFS_HSSI },
>  	{ }
>  };
>  MODULE_DEVICE_TABLE(dfl, uio_dfl_ids);
> -- 
> 2.26.2

  reply	other threads:[~2022-04-16 14:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12  6:23 [PATCH v2] uio: dfl: add HSSI feature id Tianfei Zhang
2022-04-16 14:47 ` Xu Yilun [this message]
2022-04-19  8:17   ` Zhang, Tianfei
2022-04-18  1:32 ` Wu, Hao
2022-04-19  8:25   ` Zhang, Tianfei
2022-04-19 17:52     ` matthew.gerlach
2022-04-26  2:31       ` Wu, Hao
2022-04-26 17:54         ` matthew.gerlach

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=20220416144752.GA301222@yilunxu-OptiPlex-7050 \
    --to=yilun.xu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.gerlach@linux.intel.com \
    --cc=mdf@kernel.org \
    --cc=tianfei.zhang@intel.com \
    --cc=trix@redhat.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).