On Tue, Nov 05, 2019 at 03:53:32PM -0600, Rob Herring wrote: > On Mon, Oct 28, 2019 at 05:46:27PM +0530, Anvesh Salveru wrote: > > Add support for ZRX-DC compliant PHYs. If PHY is not compliant to ZRX-DC > > specification, then after every 100ms link should transition to recovery > > state during the low power states which increases power consumption. > > > > Platforms with ZRX-DC compliant PHY can use "snps,phy-zrxdc-compliant" > > property in DesignWare controller DT node. > > > > CC: Rob Herring <robh+dt@xxxxxxxxxx> > > CC: Mark Rutland <mark.rutland@xxxxxxx> > > Signed-off-by: Anvesh Salveru <anvesh.s@xxxxxxxxxxx> > > Signed-off-by: Pankaj Dubey <pankaj.dubey@xxxxxxxxxxx> > > Reviewed-by: Gustavo Pimentel <gustavo.pimentel@xxxxxxxxxxxx> > > --- > > Change in v2: None > > > > Documentation/devicetree/bindings/pci/designware-pcie.txt | 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/Documentation/devicetree/bindings/pci/designware-pcie.txt b/Documentation/devicetree/bindings/pci/designware-pcie.txt > > index 78494c4050f7..9507ac38ac89 100644 > > --- a/Documentation/devicetree/bindings/pci/designware-pcie.txt > > +++ b/Documentation/devicetree/bindings/pci/designware-pcie.txt > > @@ -38,6 +38,8 @@ Optional properties: > > for data corruption. CDM registers include standard PCIe configuration > > space registers, Port Logic registers, DMA and iATU (internal Address > > Translation Unit) registers. > > +- snps,phy-zrxdc-compliant: This property is needed if phy complies with the > > + ZRX-DC specification. > > If this is a property of the phy, then it belongs in the phy node or > should just be implied by the phy's compatible. As suggested in the previous revision of this series [1], this is absolutely a property of the phy. > IOW, you should be able > to support this or not without changing DTs. > > Is this spec Synopys specific? (About the only thing Google turns up are > your patches.) If not, then probably shouldn't have a 'snps' prefix. This was also unfamiliar to me, however my current understanding is that Zrx-dc describes the 'Receiver DC single ended impedance' limits, this is specified in the PCI specification (table 'Common Receiver Parameters'), with a different limit for each speed. I believe the purpose of this series is to to satisfy the following implementation note in the spec "Ports that meet the Zrx-dc specification for 2.5 GT/s while in the L1.Idle state are therefore not required to implement the 100 ms timeout and transition to Recovery should avoid implementing it, since it will reduce the power savings expected from the L1 state". In other words, if it is known that the phy is compliant then an unnecessary transition to a higher energy state can be avoided. Though it's the PCI controller (in this case) that must action this and must find out about the phy it is connected to. So in my view 'phy-zrxdc-compliant' should be a property of a phy (without snps prefix), and if a controller wants to determine if it is compliant then there must be a phandle to the phy so the controller can find out. [1] https://patchwork.kernel.org/patch/11202121/ Thanks, Andrew Murray > > > RC mode: > > - num-viewport: number of view ports configured in hardware. If a platform > > does not specify it, the driver assumes 2. > > -- > > 2.17.1 > >
