[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <27939848-7e83-2897-36f9-44f47d1bfb9c@marvell.com>
Date: Fri, 17 Jul 2020 13:49:33 +0300
From: Igor Russkikh <irusskikh@...vell.com>
To: Jakub Kicinski <kuba@...nel.org>,
Alexander Lobakin <alobakin@...vell.com>,
<linux-scsi@...r.kernel.org>, <linux-kernel@...r.kernel.org>
CC: "David S. Miller" <davem@...emloft.net>,
Michal Kalderon <mkalderon@...vell.com>,
Ariel Elior <aelior@...vell.com>,
Denis Bolotin <dbolotin@...vell.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
GR-everest-linux-l2 <GR-everest-linux-l2@...vell.com>,
<QLogic-Storage-Upstream@...ium.com>, <netdev@...r.kernel.org>
Subject: Re: [EXT] Re: [PATCH net-next 10/13] qed: add support for new port
modes
> ----------------------------------------------------------------------
> On Thu, 16 Jul 2020 14:54:43 +0300 Alexander Lobakin wrote:
>> These ports ship on new boards revisions and are supported by newer
>> firmware versions.
>>
>> Signed-off-by: Alexander Lobakin <alobakin@...vell.com>
>> Signed-off-by: Igor Russkikh <irusskikh@...vell.com>
>
> What is the driver actually doing with them, tho?
>
> Looks like you translate some firmware specific field to a driver
> specific field, but I can't figure out what part of the code cares
> about hw_info.port_mode
Hi Jakub,
You are right, this info is never used/reported.
Alexander is extending already existing non used field with new values from
our latest hardware revisions.
I thought devlink info could be a good place to output such kind of information.
Thats basically a layout of *Physical* ports on device - quite useful info I
think.
Important thing is these ports may not be directly mapped to PCI PFs. So
reading `ethtool eth*` may not explain you the real device capabilities.
Do you think it makes sense adding such info to `devlink info` then?
Thanks
Igor
Powered by blists - more mailing lists