mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "lipeng (Y)" <lipeng321@huawei.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>,
	<yisen.zhuang@huawei.com>, <salil.mehta@huawei.com>
Subject: Re: [PATCH net-next 1/3] net: hns3: add support for multiple media type
Date: Fri, 3 May 2019 11:13:23 +0800	[thread overview]
Message-ID: <1d7faec8-22f7-0e8f-7e38-9ad600134a7c@huawei.com> (raw)
In-Reply-To: <20190501123750.GA9844@lunn.ch>



On 2019/5/1 20:37, Andrew Lunn wrote:
> On Wed, May 01, 2019 at 11:05:42AM +0800, Peng Li wrote:
>> From: Jian Shen <shenjian15@huawei.com>
>>
>> Previously, we can only identify copper and fiber type, the
>> supported link modes of port information are always showing
>> SR type. This patch adds support for multiple media types,
>> include SR, LR CR, KR. Driver needs to query the media type
>> from firmware periodicly, and updates the port information.
>>
>> The new port information looks like this:
>> Settings for eth0:
>>          Supported ports: [ FIBRE ]
>>          Supported link modes:   25000baseCR/Full
>>                                  25000baseSR/Full
>>                                  1000baseX/Full
>>                                  10000baseCR/Full
>>                                  10000baseSR/Full
>>                                  10000baseLR/Full
>>          Supported pause frame use: Symmetric
>>          Supports auto-negotiation: No
>>          Supported FEC modes: None BaseR
>>          Advertised link modes:  25000baseCR/Full
>>                                  25000baseSR/Full
>>                                  1000baseX/Full
>>                                  10000baseCR/Full
>>                                  10000baseSR/Full
>>                                  10000baseLR/Full
> Hi Peng
>
> If it does not support auto-negotiation, do these advertised link
> modes make any sense? Does it really advertise, or is it all fixed
> configured?
>
> 	Andrew
>
> .
Hi Andrew:

it makes no sense when auto-negotiation is not supported.
I should handle it differently with the case supports auto-negotiation
and not supports auto-negotiation.

I will fix it in next version, result like below:
Settings for eth0:
         Supported ports: [ FIBRE ]
         Supported link modes:   25000baseCR/Full
                                 25000baseSR/Full
                                 1000baseX/Full
                                 10000baseCR/Full
                                 10000baseSR/Full
                                 10000baseLR/Full
         Supported pause frame use: Symmetric
         Supports auto-negotiation: No
         Supported FEC modes: None BaseR
         Advertised link modes:  Not reported
         Advertised pause frame use: No
         Advertised auto-negotiation: No
         Advertised FEC modes: Not reported
         Speed: 10000Mb/s
         Duplex: Full
         Port: FIBRE
         PHYAD: 0
         Transceiver: internal
         Auto-negotiation: off
         Current message level: 0x00000036 (54)
                                probe link ifdown ifup
         Link detected: yes

         Wish I have understood your comments correctly.


Thanks!


>



  reply	other threads:[~2019-05-03  3:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01  3:05 [PATCH net-next 0/3] net: hns3: enhance capabilities for fibre port Peng Li
2019-05-01  3:05 ` [PATCH net-next 1/3] net: hns3: add support for multiple media type Peng Li
2019-05-01 12:37   ` Andrew Lunn
2019-05-03  3:13     ` lipeng (Y) [this message]
2019-05-03  9:54       ` lipeng (Y)
2019-05-01  3:05 ` [PATCH net-next 2/3] net: hns3: add autoneg and change speed support for fibre port Peng Li
2019-05-01  3:05 ` [PATCH net-next 3/3] net: hns3: add support for FEC encoding control Peng Li

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=1d7faec8-22f7-0e8f-7e38-9ad600134a7c@huawei.com \
    --to=lipeng321@huawei.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=salil.mehta@huawei.com \
    --cc=yisen.zhuang@huawei.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

all inboxes | Powered by JetHome®