Hi, On 13/08/19 8:37 AM, Z.q. Hou wrote: > Hi Andrew, > > Thanks a lot for your comments! > >> -----Original Message----- >> From: Andrew Murray <andrew.mur...@arm.com> >> Sent: 2019年8月12日 16:45 >> To: Z.q. Hou <zhiqiang....@nxp.com> >> Cc: linux-...@vger.kernel.org; devicet...@vger.kernel.org; >> linux-kernel@vger.kernel.org; gustavo.pimen...@synopsys.com; >> jingooh...@gmail.com; bhelg...@google.com; robh...@kernel.org; >> mark.rutl...@arm.com; shawn...@kernel.org; Leo Li >> <leoyang...@nxp.com>; lorenzo.pieral...@arm.com; M.h. Lian >> <minghuan.l...@nxp.com>; Kishon Vijay Abraham I <kis...@ti.com>; >> Gabriele Paoloni <gabriele.paol...@huawei.com> >> Subject: Re: [PATCH 1/4] dt-bingings: PCI: Remove the num-lanes from >> Required properties >> >> On Mon, Aug 12, 2019 at 04:22:16AM +0000, Z.q. Hou wrote: >>> From: Hou Zhiqiang <zhiqiang....@nxp.com> >>> >>> The num-lanes is not a mandatory property, e.g. on FSL Layerscape >>> SoCs, the PCIe link training is completed automatically base on the >>> selected SerDes protocol, it doesn't need the num-lanes to set-up the >>> link width. >>> >>> It has been added in the Optional properties. This patch is to remove >>> it from the Required properties. >> >> For clarity, maybe this paragraph can be reworded to: >> >> "It is previously in both Required and Optional properties, let's remove it >> from the Required properties". > > Agree and will change in v2. > >> >> I don't understand why this property is previously in both required and >> optional... >> >> It looks like num-lanes was first made optional back in >> 2015 and removed from the Required section (907fce090253). >> But then re-added back into the Required section in 2017 with the adition of >> bindings for EP mode (b12befecd7de). >> >> Is num-lanes actually required for EP mode? > > Kishon, please help to answer this query?
It should be optional for EP too. Thanks Kishon
