DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shweta Choudaha <shweta.choudaha@gmail.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	 "Zhang, Helin" <helin.zhang@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	 "shweta.choudaha@att.com" <shweta.choudaha@att.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/1] net/ixgbe: Add access and locking APIs for MDIO
Date: Wed, 11 Apr 2018 15:01:22 +0100	[thread overview]
Message-ID: <CAActUdf2Vo6nAAtL73nwVc3+D39LqPv5zE2BmQSJ8LSLPZPL+g@mail.gmail.com> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09093B75F6E8@shsmsx102.ccr.corp.intel.com>

Thanks for the review.
I have sent an updated patch.

regards,
Shweta

On Wed, Apr 4, 2018 at 3:15 AM, Lu, Wenzhuo <wenzhuo.lu@intel.com> wrote:

> Hi Shweta,
>
> > -----Original Message-----
> > From: Shweta Choudaha [mailto:shweta.choudaha@gmail.com]
> > Sent: Thursday, March 22, 2018 1:36 AM
> > To: dev@dpdk.org
> > Cc: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Ananyev, Konstantin
> > <konstantin.ananyev@intel.com>; Zhang, Helin <helin.zhang@intel.com>;
> > Yigit, Ferruh <ferruh.yigit@intel.com>; shweta.choudaha@att.com
> > Subject: [PATCH v2 1/1] net/ixgbe: Add access and locking APIs for MDIO
> >
> > From: Shweta Choudaha <shweta.choudaha@att.com>
> >
> > Add ixgbe MDIO lock/unlock and access APIs to read and write registers
> using
> > specific device address. This provides MDIO access to any devices that
> are
> > not associated with the autoprobed PHY.Export these APIs via the map file
> >
> > Signed-off-by: Shweta Choudaha <shweta.choudaha@att.com>
> > Reviewed-by: Chas Williams <chas3@att.com>
> > Reviewed-by: Luca Boccassi <bluca@debian.org>
> > ---
> >  drivers/net/ixgbe/rte_pmd_ixgbe.c           | 203
> > ++++++++++++++++++++++++++++
> >  drivers/net/ixgbe/rte_pmd_ixgbe.h           |  71 ++++++++++
> >  drivers/net/ixgbe/rte_pmd_ixgbe_version.map |   9 ++
> >  3 files changed, 283 insertions(+)
> >
> > diff --git a/drivers/net/ixgbe/rte_pmd_ixgbe.c
> > b/drivers/net/ixgbe/rte_pmd_ixgbe.c
> > index d8ca8ca31..1846af89b 100644
> > --- a/drivers/net/ixgbe/rte_pmd_ixgbe.c
> > +++ b/drivers/net/ixgbe/rte_pmd_ixgbe.c
> > @@ -5,6 +5,8 @@
> >  #include <rte_ethdev_driver.h>
> >
> >  #include "base/ixgbe_api.h"
> > +#include "base/ixgbe_x540.h"
> > +#include "base/ixgbe_x550.h"
> >  #include "ixgbe_ethdev.h"
> >  #include "rte_pmd_ixgbe.h"
> >
> > @@ -1012,3 +1014,204 @@ rte_pmd_ixgbe_bypass_wd_reset(uint16_t
> > port_id)
> >       return ixgbe_bypass_wd_reset(dev);
> >  }
> >  #endif
> > +
> > +/**
> > + *  rte_pmd_ixgbe_acquire_swfw - Acquire SWFW semaphore
> > + *  @hw: pointer to hardware structure
> > + *  @mask: Mask to specify which semaphore to acquire
> > + *
> > + *  Acquires the SWFW semaphore and get the shared phy token as needed
> > +*/ STATIC s32 rte_pmd_ixgbe_acquire_swfw(struct ixgbe_hw *hw, u32 mask)
> > +{
> > +     int retries = FW_PHY_TOKEN_RETRIES;
> > +     s32 status = IXGBE_SUCCESS;
> > +
> > +     while (--retries) {
> > +             status = ixgbe_acquire_swfw_sync_X540(hw, mask);
> " ixgbe_acquire_swfw_sync_X540" is only for x540. Why not using "
> ixgbe_acquire_swfw_semaphore" which is common.
> The same for " ixgbe_release_swfw_sync_X540".
>
>
> > a/drivers/net/ixgbe/rte_pmd_ixgbe_version.map
> > b/drivers/net/ixgbe/rte_pmd_ixgbe_version.map
> > index bf776742c..88a91627a 100644
> > --- a/drivers/net/ixgbe/rte_pmd_ixgbe_version.map
> > +++ b/drivers/net/ixgbe/rte_pmd_ixgbe_version.map
> > @@ -52,3 +52,12 @@ DPDK_17.08 {
> >       rte_pmd_ixgbe_bypass_wd_timeout_show;
> >       rte_pmd_ixgbe_bypass_wd_timeout_store;
> >  } DPDK_17.05;
> > +
> > +EXPERIMENTAL {
> > +     global:
> > +
> > +     rte_pmd_ixgbe_lock_mdio;
> > +     rte_pmd_ixgbe_unlock_mdio;
> > +     rte_pmd_ixgbe_mdio_read_unlocked;
> > +     rte_pmd_ixgbe_mdio_write_unlocked;
> > +} DPDK_17.08;
> 17.08 is old. Should add a 18.05 here.
>
> > --
> > 2.11.0
>
>

  reply	other threads:[~2018-04-11 14:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21 17:36 [dpdk-dev] [PATCH v2 0/1] net/ixgbe: Add read/write PMD MDIO API Shweta Choudaha
2018-03-21 17:36 ` [dpdk-dev] [PATCH v2 1/1] net/ixgbe: Add access and locking APIs for MDIO Shweta Choudaha
2018-04-04  2:15   ` Lu, Wenzhuo
2018-04-11 14:01     ` Shweta Choudaha [this message]
2018-04-11 13:59   ` [dpdk-dev] [PATCH v3] " Shweta Choudaha
2018-04-13  2:37     ` Zhang, Qi Z
2018-04-13 16:41       ` Shweta Choudaha
2018-04-13 16:35     ` [dpdk-dev] [PATCH v4] net/ixgbe: add " Shweta Choudaha
2018-04-15 13:32       ` Zhang, Qi Z
2018-04-17 16:14         ` Zhang, Helin

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=CAActUdf2Vo6nAAtL73nwVc3+D39LqPv5zE2BmQSJ8LSLPZPL+g@mail.gmail.com \
    --to=shweta.choudaha@gmail.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=helin.zhang@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=shweta.choudaha@att.com \
    --cc=wenzhuo.lu@intel.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).