DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Hernan Vargas <hernan.vargas@intel.com>,
	dev@dpdk.org, gakhil@marvell.com, trix@redhat.com
Cc: nicolas.chautru@intel.com, qi.z.zhang@intel.com
Subject: Re: [PATCH v5 4/5] baseband/fpga_5gnr_fec: add AGX100 support
Date: Tue, 6 Feb 2024 16:30:33 +0100	[thread overview]
Message-ID: <14decba4-9888-46df-8804-b2ce5435f1f3@redhat.com> (raw)
In-Reply-To: <20240123165454.104465-5-hernan.vargas@intel.com>



On 1/23/24 17:54, Hernan Vargas wrote:
> Add support for new FPGA variant AGX100 (on Arrow Creek N6000).
> 
> Signed-off-by: Hernan Vargas <hernan.vargas@intel.com>
> ---
>   doc/guides/bbdevs/fpga_5gnr_fec.rst           |   69 +-
>   drivers/baseband/fpga_5gnr_fec/agx100_pmd.h   |  273 ++++
>   .../baseband/fpga_5gnr_fec/fpga_5gnr_fec.h    |   12 +-
>   .../fpga_5gnr_fec/rte_fpga_5gnr_fec.c         | 1230 +++++++++++++++--
>   drivers/baseband/fpga_5gnr_fec/vc_5gnr_pmd.h  |    1 -
>   5 files changed, 1458 insertions(+), 127 deletions(-)
>   create mode 100644 drivers/baseband/fpga_5gnr_fec/agx100_pmd.h
> 

...

> +#endif /* _AGX100_H_ */
> diff --git a/drivers/baseband/fpga_5gnr_fec/fpga_5gnr_fec.h b/drivers/baseband/fpga_5gnr_fec/fpga_5gnr_fec.h
> index 982e956dc819..224684902569 100644
> --- a/drivers/baseband/fpga_5gnr_fec/fpga_5gnr_fec.h
> +++ b/drivers/baseband/fpga_5gnr_fec/fpga_5gnr_fec.h
> @@ -8,6 +8,7 @@
>   #include <stdint.h>
>   #include <stdbool.h>
>   
> +#include "agx100_pmd.h"
>   #include "vc_5gnr_pmd.h"
>   
>   /* Helper macro for logging */
> @@ -131,12 +132,21 @@ struct fpga_5gnr_fec_device {
>   	uint64_t q_assigned_bit_map;
>   	/** True if this is a PF FPGA 5GNR device. */
>   	bool pf_device;
> +	/** Maximum number of possible queues for this device. */
> +	uint8_t total_num_queues;

You missed below comment on v4 review:
"
Introduction of total_num_queues should be in a dedicated patch as a
preliminary rework.
"

> +	/** FPGA Variant. VC_5GNR_FPGA_VARIANT = 0; AGX100_FPGA_VARIANT = 1. */
> +	uint8_t fpga_variant;
>   };
>   


  reply	other threads:[~2024-02-06 15:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 16:54 [PATCH v5 0/5] changes for 24.03 Hernan Vargas
2024-01-23 16:54 ` [PATCH v5 1/5] doc: fix fpga 5gnr configuration values Hernan Vargas
2024-02-06 15:15   ` Maxime Coquelin
2024-01-23 16:54 ` [PATCH v5 2/5] baseband/fpga_5gnr_fec: renaming for consistency Hernan Vargas
2024-01-23 16:54 ` [PATCH v5 3/5] baseband/fpga_5gnr_fec: add Vista Creek variant Hernan Vargas
2024-01-23 16:54 ` [PATCH v5 4/5] baseband/fpga_5gnr_fec: add AGX100 support Hernan Vargas
2024-02-06 15:30   ` Maxime Coquelin [this message]
2024-02-07  8:19     ` Maxime Coquelin
2024-01-23 16:54 ` [PATCH v5 5/5] baseband/fpga_5gnr_fec: cosmetic comment changes Hernan Vargas
2024-02-06 15:38   ` Maxime Coquelin

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=14decba4-9888-46df-8804-b2ce5435f1f3@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hernan.vargas@intel.com \
    --cc=nicolas.chautru@intel.com \
    --cc=qi.z.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).