From: Jakub Kicinski <kuba@kernel•org>
To: Tony Nguyen <anthony.l.nguyen@intel•com>
Cc: davem@davemloft•net, pabeni@redhat•com, edumazet@google•com,
Anirudh Venkataramanan <anirudh.venkataramanan@intel•com>,
netdev@vger•kernel.org, Lukasz Plachno <lukasz.plachno@intel•com>,
Alexander Lobakin <alexandr.lobakin@intel•com>,
Gurucharan <gurucharanx.g@intel•com>
Subject: Re: [PATCH net-next 5/5] ice: Print human-friendly PHY types
Date: Thu, 25 Aug 2022 20:03:44 -0700 [thread overview]
Message-ID: <20220825200344.32cb445f@kernel.org> (raw)
In-Reply-To: <20220824170340.207131-6-anthony.l.nguyen@intel.com>
On Wed, 24 Aug 2022 10:03:40 -0700 Tony Nguyen wrote:
> Old:
> [ 286.130405] ice 0000:16:00.0: get phy caps - report_mode = 0x2
> [ 286.130409] ice 0000:16:00.0: phy_type_low = 0x108021020502000
> [ 286.130412] ice 0000:16:00.0: phy_type_high = 0x0
> [ 286.130415] ice 0000:16:00.0: caps = 0xc8
> [ 286.130419] ice 0000:16:00.0: low_power_ctrl_an = 0x4
> [ 286.130421] ice 0000:16:00.0: eee_cap = 0x0
> [ 286.130424] ice 0000:16:00.0: eeer_value = 0x0
> [ 286.130427] ice 0000:16:00.0: link_fec_options = 0xdf
> [ 286.130430] ice 0000:16:00.0: module_compliance_enforcement = 0x0
> [ 286.130433] ice 0000:16:00.0: extended_compliance_code = 0xb
> [ 286.130435] ice 0000:16:00.0: module_type[0] = 0x11
> [ 286.130438] ice 0000:16:00.0: module_type[1] = 0x1
> [ 286.130441] ice 0000:16:00.0: module_type[2] = 0x0
>
> New:
> [ 1128.297347] ice 0000:16:00.0: get phy caps dump
> [ 1128.297351] ice 0000:16:00.0: phy_caps_active: phy_type_low: 0x0108021020502000
> [ 1128.297355] ice 0000:16:00.0: phy_caps_active: bit(13): 10G_SFI_DA
> [ 1128.297359] ice 0000:16:00.0: phy_caps_active: bit(20): 25GBASE_CR
> [ 1128.297362] ice 0000:16:00.0: phy_caps_active: bit(22): 25GBASE_CR1
> [ 1128.297365] ice 0000:16:00.0: phy_caps_active: bit(29): 25G_AUI_C2C
> [ 1128.297368] ice 0000:16:00.0: phy_caps_active: bit(36): 50GBASE_CR2
> [ 1128.297371] ice 0000:16:00.0: phy_caps_active: bit(41): 50G_LAUI2
> [ 1128.297374] ice 0000:16:00.0: phy_caps_active: bit(51): 100GBASE_CR4
> [ 1128.297377] ice 0000:16:00.0: phy_caps_active: bit(56): 100G_CAUI4
> [ 1128.297380] ice 0000:16:00.0: phy_caps_active: phy_type_high: 0x0000000000000000
> [ 1128.297383] ice 0000:16:00.0: phy_caps_active: report_mode = 0x4
> [ 1128.297386] ice 0000:16:00.0: phy_caps_active: caps = 0xc8
> [ 1128.297389] ice 0000:16:00.0: phy_caps_active: low_power_ctrl_an = 0x4
> [ 1128.297392] ice 0000:16:00.0: phy_caps_active: eee_cap = 0x0
> [ 1128.297394] ice 0000:16:00.0: phy_caps_active: eeer_value = 0x0
> [ 1128.297397] ice 0000:16:00.0: phy_caps_active: link_fec_options = 0xdf
> [ 1128.297400] ice 0000:16:00.0: phy_caps_active: module_compliance_enforcement = 0x0
> [ 1128.297402] ice 0000:16:00.0: phy_caps_active: extended_compliance_code = 0xb
> [ 1128.297405] ice 0000:16:00.0: phy_caps_active: module_type[0] = 0x11
> [ 1128.297408] ice 0000:16:00.0: phy_caps_active: module_type[1] = 0x1
> [ 1128.297411] ice 0000:16:00.0: phy_caps_active: module_type[2] = 0x0
Is this not something that can be read via ethtool -m ?
next prev parent reply other threads:[~2022-08-26 3:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 17:03 [PATCH net-next 0/5][pull request] Intel Wired LAN Driver Updates 2022-08-24 (ice) Tony Nguyen
2022-08-24 17:03 ` [PATCH net-next 1/5] ice: Add support for ip TTL & ToS offload Tony Nguyen
2022-08-24 17:03 ` [PATCH net-next 2/5] ice: Add port option admin queue commands Tony Nguyen
2022-08-24 17:03 ` [PATCH net-next 3/5] ice: Add additional flags to ice_nvm_write_activate Tony Nguyen
2022-08-24 17:03 ` [PATCH net-next 4/5] ice: Implement devlink port split operations Tony Nguyen
2022-08-24 17:03 ` [PATCH net-next 5/5] ice: Print human-friendly PHY types Tony Nguyen
2022-08-26 3:03 ` Jakub Kicinski [this message]
2022-08-30 18:33 ` Jesse Brandeburg
2022-08-30 21:54 ` Jakub Kicinski
2022-08-26 10:50 ` [PATCH net-next 0/5][pull request] Intel Wired LAN Driver Updates 2022-08-24 (ice) patchwork-bot+netdevbpf
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=20220825200344.32cb445f@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=alexandr.lobakin@intel$(echo .)com \
--cc=anirudh.venkataramanan@intel$(echo .)com \
--cc=anthony.l.nguyen@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gurucharanx.g@intel$(echo .)com \
--cc=lukasz.plachno@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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