From: "Zhang, Helin" <helin.zhang@intel.com>
To: Shweta Choudaha <shweta.choudaha@gmail.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"Greenwalt, Paul" <paul.greenwalt@intel.com>,
"Tantilov, Emil S" <emil.s.tantilov@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Cc: Shweta Choudaha <shweta.choudaha@att.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Dai, Wei" <wei.dai@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 2/2] net/ixgbe : backplane port MDIO support
Date: Wed, 10 Jan 2018 03:17:03 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E71ACEFEB0@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1509978323-9879-2-git-send-email-shweta.choudaha@gmail.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Shweta Choudaha
> Sent: Monday, November 6, 2017 10:25 PM
> To: dev@dpdk.org
> Cc: Shweta Choudaha
> Subject: [dpdk-dev] [PATCH v2 2/2] net/ixgbe : backplane port MDIO support
>
> From: Shweta Choudaha <shweta.choudaha@att.com>
>
> Initialize MDIO read/write functions for backplan port
> (IXGBE_DEV_ID_X550EM_A_KR_L) to enable read/write registers via MDIO
>
> 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/base/ixgbe_x550.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ixgbe/base/ixgbe_x550.c
> b/drivers/net/ixgbe/base/ixgbe_x550.c
> index 9862391..3f89dc4 100644
> --- a/drivers/net/ixgbe/base/ixgbe_x550.c
> +++ b/drivers/net/ixgbe/base/ixgbe_x550.c
> @@ -2374,6 +2374,7 @@ s32 ixgbe_init_phy_ops_X550em(struct ixgbe_hw
> *hw)
> }
>
> switch (hw->device_id) {
> + case IXGBE_DEV_ID_X550EM_A_KR_L:
Basically this device ID is for a specific SoC platform, there is no external PHY for it.
We prefer to NACK it. I added more experts here to answer more questions if you have.
Note that they are not working on DPDK, and they are experts on ixgbe NIC/SW.
Or we can discuss more if you have any requests to Intel.
Sorry,
Helin
> case IXGBE_DEV_ID_X550EM_A_1G_T:
> case IXGBE_DEV_ID_X550EM_A_1G_T_L:
> phy->ops.read_reg_mdi = ixgbe_read_phy_reg_mdi_22;
> --
> 2.1.4
next prev parent reply other threads:[~2018-01-10 3:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 13:42 [dpdk-dev] [PATCH 1/2] net/ixgbe: add and export MDIO APIs Shweta Choudaha
2017-11-06 14:25 ` [dpdk-dev] [PATCH v2 " Shweta Choudaha
2017-11-06 14:25 ` [dpdk-dev] [PATCH v2 2/2] net/ixgbe : backplane port MDIO support Shweta Choudaha
2017-12-21 3:23 ` Zhang, Helin
2018-01-10 3:17 ` Zhang, Helin [this message]
2018-01-23 14:14 ` Shweta Choudaha
2017-12-21 3:25 ` [dpdk-dev] [PATCH v2 1/2] net/ixgbe: add and export MDIO APIs Zhang, Helin
2018-01-23 15:12 ` Shweta Choudaha
2018-01-23 15:05 ` [dpdk-dev] [PATCH v3 " Shweta Choudaha
2018-01-23 15:05 ` [dpdk-dev] [PATCH v3 2/2] net/ixgbe : backplane port MDIO support Shweta Choudaha
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=F35DEAC7BCE34641BA9FAC6BCA4A12E71ACEFEB0@SHSMSX103.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=dev@dpdk.org \
--cc=emil.s.tantilov@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jingjing.wu@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=paul.greenwalt@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=shweta.choudaha@att.com \
--cc=shweta.choudaha@gmail.com \
--cc=wei.dai@intel.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).