Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp4322654ybg; Mon, 21 Oct 2019 07:17:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqxP/iO72FYa/s/QbtLDb/cBwKVm/3zFk8KAMRFWjY8nMBJkcBmXdwa8PLK5hlQ2ia6bbzPl X-Received: by 2002:a17:906:7c57:: with SMTP id g23mr22352936ejp.116.1571667432246; Mon, 21 Oct 2019 07:17:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571667432; cv=none; d=google.com; s=arc-20160816; b=ksdy1+VMh3uBy6lLXo6Ltzq2O+o6dFMq4nD81nabi1SWZEeC279H0GTKGVkfyPh562 tsVhq2WXes2qoxJpNyzIg+gK7/7aTFdohNx2uicjPkQFWvQrwP0R9XP5Aa3jBmfWUo06 Ff7Ahaf9pYKC6Or4jd10LolzNnplwlwY1KD+HamHFnKmH4qxgtk1zGOgFJ03ex1zTMpP rtv3G8rSEM5LT+KjiZQm9615p17cmP8FRGZEgbXK3qz/j+5M7L/L/BpBn9j/9qxicRqz NsGiP5m+y1bNvDuiqtYwHOGSs89A+ejnAChErm4gJr/WI+jzKSd2xRuRvm1N4SlvlKu0 oKgg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=GTDqh7ymc4fp5hCo/GFblYGIUvaJhEZuKtIdwCjQfMk=; b=IFm54qxRm+SFCEOTpZqgRdx1LCv40+DopAcoHim3f+ZJOY5jFtXoxxVyYyZsOklf4X 6ars6AqdCOxdvaHUAhDoypyrcuILjocEVLwj16SeOS2LhgLUEZNBzwjbS/pkPIqnI+/9 4pUyAK2gR8sJGG+CZXBlKbPbeN1eb4UlDsO8BVZVdHm6WjVL6CTO45HEVQ9jArmRYJvD Vnb2UTrj5MVrSw8ArYGLO6ju/j4DWQ1d1ZUc9aCuUAWuatgztd51QZpgEw18HSIgZYUU R/TUZURY76mVj3j6gcmFj5S/hZctqmE/OvIFV2L6t70/Fx/hfVGzbHSBCsu6j3AMru/H SFSw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b8si10384515edc.231.2019.10.21.07.16.48; Mon, 21 Oct 2019 07:17:12 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729348AbfJUOQG (ORCPT + 99 others); Mon, 21 Oct 2019 10:16:06 -0400 Received: from [217.140.110.172] ([217.140.110.172]:53870 "EHLO foss.arm.com" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1728551AbfJUOQF (ORCPT ); Mon, 21 Oct 2019 10:16:05 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 71E1E1007; Mon, 21 Oct 2019 07:15:44 -0700 (PDT) Received: from localhost (unknown [10.37.6.20]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id A115B3F71F; Mon, 21 Oct 2019 07:15:43 -0700 (PDT) Date: Mon, 21 Oct 2019 15:15:41 +0100 From: Andrew Murray To: Anvesh Salveru Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, bhelgaas@google.com, gustavo.pimentel@synopsys.com, jingoohan1@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com, Pankaj Dubey Subject: Re: [PATCH 1/2] dt-bindings: PCI: designware: Add binding for ZRX-DC PHY property Message-ID: <20191021141541.GS47056@e119886-lin.cambridge.arm.com> References: <1571660755-30270-1-git-send-email-anvesh.s@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1571660755-30270-1-git-send-email-anvesh.s@samsung.com> User-Agent: Mutt/1.10.1+81 (426a6c1) (2018-08-26) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 21, 2019 at 05:55:55PM +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. > > Signed-off-by: Anvesh Salveru > Signed-off-by: Pankaj Dubey > --- > 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 Strictly speaking, this is a property of the phy - not the controller that uses it. If I understand correctly, there are some DW based PCI controllers that use a phandle reference in DT to a Phy (such as fsl,imx6q-pcie.txt). Therefore it feels like this is in the wrong place. Is there a reason this isn't described in the Phy? Thanks, Andrew Murray > + ZRX-DC specification. > 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 >