DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Anoob Joseph <anoobj@marvell.com>, Thomas Monjalon <thomas@monjalon.net>
Cc: Anoob Joseph <anoobj@marvell.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Ankur Dwivedi <adwivedi@marvell.com>,
	Tejasree Kondoj <ktejasree@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Archana Muniganti <marchana@marvell.com>,
	Vidya Sagar Velumuri <vvelumuri@marvell.com>
Subject: Re: [dpdk-dev] [PATCH 02/11] common/cnxk: add CPT dev config routines
Date: Mon, 14 Jun 2021 06:34:23 +0000	[thread overview]
Message-ID: <CO6PR18MB44841F82918ACE684CDE0F76D8319@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1622649385-22652-3-git-send-email-anoobj@marvell.com>

> diff --git a/drivers/common/cnxk/roc_cpt_priv.h
> b/drivers/common/cnxk/roc_cpt_priv.h
> new file mode 100644
> index 0000000..8cb2dbd
> --- /dev/null
> +++ b/drivers/common/cnxk/roc_cpt_priv.h
> @@ -0,0 +1,28 @@
> +/* SPDX-License-Identifier: BSD-3-Clause
> + * Copyright(C) 2021 Marvell.
> + */
> +
> +#ifndef _ROC_CPT_PRIV_H_
> +#define _ROC_CPT_PRIV_H_
> +
> +/* Set number of number of hystbits to 6.
Fix typo
Set number of hystbits to 6.

> + * This will trigger the FC writes whenever
> + * number of outstanding commands in the queue
> + * becomes multiple of 32.
> + */
> +#define CPT_FC_NUM_HYST_BITS 6
> +
> +struct cpt {
> +	struct plt_pci_device *pci_dev;
> +	struct dev dev;

dev is very generic name for a struct, can we make it roc_dev?

> +	uint16_t lf_msix_off[ROC_CPT_MAX_LFS];
> +	uint8_t lf_blkaddr[ROC_CPT_MAX_LFS];
> +} __plt_cache_aligned;
> +
> +static inline struct cpt *
> +roc_cpt_to_cpt_priv(struct roc_cpt *roc_cpt)
> +{
> +	return (struct cpt *)&roc_cpt->reserved[0];
> +}
> +
> +#endif /* _ROC_CPT_PRIV_H_ */


  reply	other threads:[~2021-06-14  6:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 15:56 [dpdk-dev] [PATCH 00/11] Add CPT in Marvell CNXK common driver Anoob Joseph
2021-06-02 15:56 ` [dpdk-dev] [PATCH 01/11] common/cnxk: add CPT HW defines Anoob Joseph
2021-06-14  6:35   ` Akhil Goyal
2021-06-02 15:56 ` [dpdk-dev] [PATCH 02/11] common/cnxk: add CPT dev config routines Anoob Joseph
2021-06-14  6:34   ` Akhil Goyal [this message]
2021-06-02 15:56 ` [dpdk-dev] [PATCH 03/11] common/cnxk: add mbox to configure RXC Anoob Joseph
2021-06-02 15:56 ` [dpdk-dev] [PATCH 04/11] common/cnxk: add CPT LF config Anoob Joseph
2021-06-02 15:56 ` [dpdk-dev] [PATCH 05/11] common/cnxk: add CPT diagnostics Anoob Joseph
2021-06-02 15:56 ` [dpdk-dev] [PATCH 06/11] common/cnxk: add CPT LF flush Anoob Joseph
2021-06-02 15:56 ` [dpdk-dev] [PATCH 07/11] common/cnxk: add SE microcode defines Anoob Joseph
2021-06-02 15:56 ` [dpdk-dev] [PATCH 08/11] common/cnxk: add IE " Anoob Joseph
2021-06-02 15:56 ` [dpdk-dev] [PATCH 09/11] common/cnxk: add AE " Anoob Joseph
2021-06-02 15:56 ` [dpdk-dev] [PATCH 10/11] common/cnxk: add lmtline init Anoob Joseph
2021-06-02 15:56 ` [dpdk-dev] [PATCH 11/11] common/cnxk: add fpm tables Anoob Joseph

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=CO6PR18MB44841F82918ACE684CDE0F76D8319@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=adwivedi@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=ktejasree@marvell.com \
    --cc=marchana@marvell.com \
    --cc=thomas@monjalon.net \
    --cc=vvelumuri@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;
as well as URLs for NNTP newsgroup(s).