<div dir="ltr"> <div> <div id="m_-855273323119444482mail-editor-reference-message-container"> <span> <div style="font-family:Aptos;font-size:12pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt"> <span style="font-weight:bold">From: </span>Ferruh Yigit <<a href="mailto:ferruh.yigit@amd.com" target="_blank">ferruh.yigit@amd.com</a>><br> <span style="font-weight:bold">Date: </span>Wednesday, May 22, 2024 at 2:00 PM<br> <span style="font-weight:bold">To: </span>Damodharam Ammepalli <<a href="mailto:damodharam.ammepalli@broadcom.com" target="_blank">damodharam.ammepalli@broadcom.com</a>>, Ajit Khaparde <<a href="mailto:ajit.khaparde@broadcom.com" target="_blank">ajit.khaparde@broadcom.com</a>><br> <span style="font-weight:bold">Cc: </span><a href="mailto:dev@dpdk.org" target="_blank">dev@dpdk.org</a> <<a href="mailto:dev@dpdk.org" target="_blank">dev@dpdk.org</a>>, Thomas Monjalon <<a href="mailto:thomas@monjalon.net" target="_blank">thomas@monjalon.net</a>>, huangdengdui <<a href="mailto:huangdengdui@huawei.com" target="_blank">huangdengdui@huawei.com</a>>, lihuisong (C) <<a href="mailto:lihuisong@huawei.com" target="_blank">lihuisong@huawei.com</a>>, <a href="mailto:stephen@networkplumber.org" target="_blank">stephen@networkplumber.org</a> <<a href="mailto:stephen@networkplumber.org" target="_blank">stephen@networkplumber.org</a>>, <a href="mailto:fengchengwen@huawei.com" target="_blank">fengchengwen@huawei.com</a> <<a href="mailto:fengchengwen@huawei.com" target="_blank">fengchengwen@huawei.com</a>>, <a href="mailto:haijie1@huawei.com" target="_blank">haijie1@huawei.com</a> <<a href="mailto:haijie1@huawei.com" target="_blank">haijie1@huawei.com</a>><br> <span style="font-weight:bold">Subject: </span>Re: [RFC 0/2] Add support for link speed lanes<br> <br> </div> <font size="2"><span style="font-size:11pt"> <div>On 3/22/2024 10:25 PM, Damodharam Ammepalli wrote:<br> > BRCM576xx NIC modules support speeds with different lanes configuration.<br> > This is an alternate proposal to<br> > <a href="https://www.google.com/url?q=https://patchwork.dpdk.org/project/dpdk/list/?series%3D31593&source=gmail-imap&ust=1717016402000000&usg=AOvVaw1jrFok7jqKY0zhtLzKKg1Z" target="_blank"> https://www.google.com/url?q=https://patchwork.dpdk.org/project/dpdk/list/?series%3D31593&source=gmail-imap&ust=1717016402000000&usg=AOvVaw1jrFok7jqKY0zhtLzKKg1Z</a><br> > <br> > Please provide your review. Broadcom driver patches will follow.<br> > <br> > Damodharam Ammepalli (2):<br> > lib/ethdev: Add link_speed lanes support into rte lib<br> > testpmd: Add speed lanes to testpmd config and show command<br> > <br> <br> Hi Damodharam,<br> <br> As discussed in other thread, having dedicated APIs for setting lane<br> makes API more clear, so we can continue with this design.<br> <br> This RFC proposes two APIs, but agreement on other thread was around<br> three new APIs.<br> <br> Copy/pasting Thomas's suggestion<br> "<br> There are 3 needs:<br> - set PHY lane config<br> - get PHY lane config<br> - get PHY lane capabilities<br> "<br> <br> And "get PHY lane capabilities" should return capability per speed,<br> similar to FEC one.<br> <br> <br> Can you please update this RFC to have three APIs as mentioned above?<br> <br> Thanks,<br> Ferruh</div><div><br></div><div>Noted Ferruh. Will update this RFC as commented.<br> <br> </div> </span></font></span></div> </div> </div> <br> <span style="background-color:rgb(255,255,255)"><font size="2">This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.</font></span>