DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Harman Kalra <hkalra@marvell.com>, Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] common/octeontx2: upgrade mbox definition to version 9
Date: Tue, 22 Sep 2020 14:24:46 +0530	[thread overview]
Message-ID: <CALBAE1MpKsQrO_OMpB-htr-GXiCP+uiL31iB+SVHdFbVcmd4-A@mail.gmail.com> (raw)
In-Reply-To: <1600278499-15104-1-git-send-email-hkalra@marvell.com>

On Wed, Sep 16, 2020 at 11:18 PM Harman Kalra <hkalra@marvell.com> wrote:
>
> Update mail box data structures to sync with af driver mbox
> changes done to retrieve VF's base steering rule.
>
> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
> Signed-off-by: Harman Kalra <hkalra@marvell.com>

Applied to dpdk-next-net-mrvl/master. Thanks


> ---
>  drivers/common/octeontx2/otx2_mbox.h | 10 +++++++++-
>  1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/common/octeontx2/otx2_mbox.h b/drivers/common/octeontx2/otx2_mbox.h
> index 34b1d0663..5d66caebd 100644
> --- a/drivers/common/octeontx2/otx2_mbox.h
> +++ b/drivers/common/octeontx2/otx2_mbox.h
> @@ -90,7 +90,7 @@ struct mbox_msghdr {
>  #define OTX2_MBOX_RSP_SIG (0xbeef)
>         /* Signature, for validating corrupted msgs */
>         uint16_t __otx2_io sig;
> -#define OTX2_MBOX_VERSION (0x0007)
> +#define OTX2_MBOX_VERSION (0x0009)
>         /* Version of msg's structure for this ID */
>         uint16_t __otx2_io ver;
>         /* Offset of next msg within mailbox region */
> @@ -245,6 +245,8 @@ M(NPC_MCAM_READ_ENTRY,        0x600f, npc_mcam_read_entry,                  \
>  M(NPC_SET_PKIND,          0x6010, npc_set_pkind,                        \
>                                   npc_set_pkind,                        \
>                                   msg_rsp)                              \
> +M(NPC_MCAM_READ_BASE_RULE, 0x6011, npc_read_base_steer_rule, msg_req,   \
> +                                  npc_mcam_read_base_rule_rsp)         \
>  /* NIX mbox IDs (range 0x8000 - 0xFFFF) */                             \
>  M(NIX_LF_ALLOC,                0x8000, nix_lf_alloc, nix_lf_alloc_req,         \
>                                 nix_lf_alloc_rsp)                       \
> @@ -767,6 +769,7 @@ struct nix_lf_alloc_rsp {
>         uint8_t __otx2_io cgx_links;  /* No. of CGX links present in HW */
>         uint8_t __otx2_io lbk_links;  /* No. of LBK links present in HW */
>         uint8_t __otx2_io sdp_links;  /* No. of SDP links present in HW */
> +       uint8_t __otx2_io tx_link;    /* Transmit channel link number */
>  };
>
>  struct nix_lf_free_req {
> @@ -1544,6 +1547,11 @@ struct npc_mcam_read_entry_rsp {
>         uint8_t __otx2_io enable;
>  };
>
> +struct npc_mcam_read_base_rule_rsp {
> +       struct mbox_msghdr hdr;
> +       struct mcam_entry entry_data;
> +};
> +
>  /* TIM mailbox error codes
>   * Range 801 - 900.
>   */
> --
> 2.18.0
>

      reply	other threads:[~2020-09-22  9:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16 17:48 Harman Kalra
2020-09-22  8:54 ` Jerin Jacob [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=CALBAE1MpKsQrO_OMpB-htr-GXiCP+uiL31iB+SVHdFbVcmd4-A@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hkalra@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=ndabilpuram@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).