From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 484DEC5DF61 for ; Tue, 5 Nov 2019 21:53:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0392621D81 for ; Tue, 5 Nov 2019 21:53:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1572990817; bh=AtpSzcF+ikiWVL5AZdPxZ3/psINgSvSuTz/j+AwuiQI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=Mj+KoydwDOmN9kZKrB8024LHppcAseKAMT/DbXDrbpr106j2mLXxznv7odh1yZzwA ZE0C6Qho4cPsv9JPx5Uyu0f9b0/v2sRkzapG2wknRHUU9CMFM18xHdt94hwG63Ek3o dnYBWoObheFlvYlnoBZuBY69NG8Kq5iOI/5zRUKw= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730263AbfKEVxg (ORCPT ); Tue, 5 Nov 2019 16:53:36 -0500 Received: from mail-ot1-f66.google.com ([209.85.210.66]:35965 "EHLO mail-ot1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730057AbfKEVxf (ORCPT ); Tue, 5 Nov 2019 16:53:35 -0500 Received: by mail-ot1-f66.google.com with SMTP id f10so328995oto.3; Tue, 05 Nov 2019 13:53:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=PF4FeC1B4z1EiaRv3Y35zGiHOndPSUjKYmW93QdFA+M=; b=W3aNdqLajxEyB8I4UPgKLYzuoyY3Q+poRVYkGbKrkyI4gSQkx1Pwf3ris3o2d0anqH AccteWr7cFVgPg3AY0oEhzH51UwMCe3RJU7/g6i4evCXjU3M00ivJ4c+dBZVFWG7djiq yIDZzF7MS2iLd3KwXH7zaD7kLFU1lBa0m/p7Mm8Fnakjl3fAh/S3jzBZA3JIMTCvd7Ua W2A7D5EYTsSFxo1PFW7/ORwhZk0IiwzAj8znJQH6EEtWzlg1FCiREkWtd6+xx7x8SJqv DvOF3DfgpyYbPHdSHQBharofokpYEZ73Z2rCCaxdokd7tMX2AvwMI+5kLEB6HnhpxR64 H6DQ== X-Gm-Message-State: APjAAAWxEr4zarx6fssTl5lQQ1/j3P+FE7HBJunH5lXDUBVguZ8wuEHs a9eFbAWWmNDr/Se4xA6BHaWeErI= X-Google-Smtp-Source: APXvYqxAH3UBa4/0bcwAn6bLPBmEdgRBtQ7i/IwCz6UAPAR2oM/wv9oufNgH2AZpJHzNTbjp3PGc6w== X-Received: by 2002:a05:6830:4cf:: with SMTP id s15mr8462573otd.261.1572990813789; Tue, 05 Nov 2019 13:53:33 -0800 (PST) Received: from localhost (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.gmail.com with ESMTPSA id l17sm5861342oic.24.2019.11.05.13.53.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 05 Nov 2019 13:53:33 -0800 (PST) Date: Tue, 5 Nov 2019 15:53:32 -0600 From: Rob Herring 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, pankaj.dubey@samsung.com, Mark Rutland Subject: Re: [PATCH v2 1/2] dt-bindings: PCI: designware: Add binding for ZRX-DC PHY property Message-ID: <20191105215332.GA19296@bogus> References: <1572264988-17455-1-git-send-email-anvesh.s@samsung.com> <1572264988-17455-2-git-send-email-anvesh.s@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1572264988-17455-2-git-send-email-anvesh.s@samsung.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > CC: Mark Rutland > Signed-off-by: Anvesh Salveru > Signed-off-by: Pankaj Dubey > Reviewed-by: Gustavo Pimentel > --- > 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. 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. > 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 >