[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9a280b29-4e1b-cf4a-54c2-25a522834879@deltatee.com>
Date: Thu, 29 Jun 2017 12:37:46 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Allen Hubbe <Allen.Hubbe@...l.com>, linux-ntb@...glegroups.com,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: 'Jon Mason' <jdmason@...zu.us>,
'Dave Jiang' <dave.jiang@...el.com>,
'Bjorn Helgaas' <bhelgaas@...gle.com>,
'Greg Kroah-Hartman' <gregkh@...uxfoundation.org>,
'Kurt Schwemmer' <kurt.schwemmer@...rosemi.com>,
'Stephen Bates' <sbates@...thlin.com>,
'Serge Semin' <fancer.lancer@...il.com>
Subject: Re: [PATCH 12/16] switchtec_ntb: add link management
On 6/29/2017 12:11 PM, Allen Hubbe wrote:
> Should we only set self_partition? I think each peer should be able to set preferred speed, and negotiate down. As written here, the last peer to set the speed overrides the setting on the peer, and even that is not atomic if they race.
This function isn't actually setting the link speed. (Though I can
understand the confusion from the name.) It's just reporting the slowest
speed on the link between the peers for the link_is_up function. (Each
port will have negotiated it's own speed).
I don't think switchtec has the ability to actually change the port
speed or width. (Seeing they are negotiated on boot).
Logan
Powered by blists - more mailing lists