On Mon, Nov 13, 2017 at 02:35:48AM +0000, M.h. Lian wrote: [...] > > > On Friday 10 November 2017 09:18 AM, Bao Xiaowei wrote: > > > > Add the property of inbound and outbound windows number for ep driver. > > > > > > > > Signed-off-by: Bao Xiaowei <xiaowei.bao@xxxxxxx> > > > > Acked-by: Minghuan Lian <minghuan.Lian@xxxxxxx> > > > > --- > > > > v2: > > > > - no change > > > > v3: > > > > - modify the commit message > > > > v4: > > > > - no change > > > > > > > > arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 6 ++++++ > > > > 1 file changed, 6 insertions(+) > > > > > > $subject should start with something like > > > arm64: dts: ls1046a: ** Indeed. > > > > diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi > > > > b/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi > > > > index 06b5e12d04d8..f8332669663c 100644 > > > > --- a/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi > > > > +++ b/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi > > > > @@ -674,6 +674,8 @@ > > > > device_type = "pci"; > > > > dma-coherent; > > > > num-lanes = <4>; > > > > + num-ib-windows = <6>; > > > > + num-ob-windows = <6>; > > > > > > EP specific properties shouldn't be added in RC dt node. Ideally you > > > should have a separate dt node for RC and EP. > > > > It is a single PCIe controller which can be configured to either RC > > mode or EP mode. Wouldn't it conflict with the device tree > > principles to have two device tree nodes for the same PCIe > > controller? And obviously the two modes cannot be used at the same > > time so we cannot have two drivers both probe on the same hardware. > > > [Minghuan Lian] There is only one PCIe dts node in the dts file. PCIe > dts node describes the PCIe controller's hardware properties and does > not have work mode. The new properties "num-ib-windows " and > "num-ob-windows" are used to describe the inbound/outbound window > number included in the PCIe hardware. These windows are used in both > RC and EP mode. We can change work mode when resetting via RCW(reset > configuration word). I am not happy about this (that's what I am asking Rob to chime in please on DT side). 1) I do not think it is allowed to have two DT nodes in a dts with same unit address (ie same reg property) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/dra7.dtsi?h=v4.14 2) In the Synopsis Designware PCIe interface bindings we have some properties that are for RC mode and some for EP mode but there is no way from a *binding* perspective to detect in what mode the controller is: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/pci/designware-pcie.txt?h=v4.14 3) You can't use properties that in the bindings above are declared EP only for RC mode, we define bindings to respect their rules. 4) I think that a) a compatible should be added to the designware-pcie bindings to define endpoint mode and b) the same should be done for the ls1046a bindings. If the RC is programmed in EP mode DT firmware should be able to provide the information to an operating system, it is actually a _different_ component but on this I need DT people to chime in to define the best way forward. I cannot review/merge this code until the points above are clarified. Thanks, Lorenzo -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
