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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 8B720C433F5 for ; Fri, 8 Apr 2022 10:33:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=yEw/1Wn6WA3gE7Auh78p6QAArELCckDIZS+Ej9FmuXU=; b=fXxTBeciaaWAIn sQ1BI3SWltHAaPaTEY8NzWdDhpva3kooRr0hyuKOr8LkQQIVYwXlhnpyFNVILR/SJ4xPASVE+OG/d YHhxSt9KpftF1kMoHetaiOgwAW4/v9BTBiLIMQCuT25gWuFV9YwyQm0DZuOXgRZ/OSM78JwQcDM31 sUIJ8iivOf0StfjER4vcTrE7SpysDgxzC75DnD4k2XjUxZfqnl118JRhgUnsRXBlor84152wctX+3 H2CjQl1SU3F5DyPByHN3m0bsdSFkdeJl7zGD20aWisoYUhrDBd3xSJrKGl7hWTqkAYFqOhf8U6Pv3 XDpqXuFmuO1dSNNJIkbw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1ncluM-00GOHk-9i; Fri, 08 Apr 2022 10:32:02 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1ncluJ-00GOFx-3Z for linux-arm-kernel@lists.infradead.org; Fri, 08 Apr 2022 10:32:00 +0000 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 1BF4D11FB; Fri, 8 Apr 2022 03:31:56 -0700 (PDT) Received: from lpieralisi (unknown [10.57.11.200]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 05FE73F73B; Fri, 8 Apr 2022 03:31:53 -0700 (PDT) Date: Fri, 8 Apr 2022 11:31:52 +0100 From: Lorenzo Pieralisi To: Pali =?iso-8859-1?Q?Roh=E1r?= , Rob Herring Cc: Bjorn Helgaas , Andrew Lunn , Thomas Petazzoni , Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , Marek =?iso-8859-1?Q?Beh=FAn?= , Russell King , linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 2/4] dt-bindings: Add 'slot-power-limit-milliwatt' PCIe port property Message-ID: References: <20220325093827.4983-1-pali@kernel.org> <20220325093827.4983-3-pali@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220325093827.4983-3-pali@kernel.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220408_033159_249035_00243CCC X-CRM114-Status: GOOD ( 23.68 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Mar 25, 2022 at 10:38:25AM +0100, Pali Roh=E1r wrote: > This property specifies slot power limit in mW unit. It is a form-factor > and board specific value and must be initialized by hardware. > = > Some PCIe controllers delegate this work to software to allow hardware > flexibility and therefore this property basically specifies what should > host bridge program into PCIe Slot Capabilities registers. > = > The property needs to be specified in mW unit instead of the special form= at > defined by Slot Capabilities (which encodes scaling factor or different > unit). Host drivers should convert the value from mW to needed format. > = > Signed-off-by: Pali Roh=E1r > Signed-off-by: Marek Beh=FAn > = > --- > This change was already accepted into dt-schema repo by Rob Herring: > https://github.com/devicetree-org/dt-schema/pull/66 Is there a way I can check a DT binding was pulled into the schema without having to read the patch (eg just checking Rob's Acked/Reviewed tags ?) I think this patch should have been posted to devicetree@vger.kernel.org, by the way. Lorenzo > Documentation/devicetree/bindings/pci/pci.txt | 6 ++++++ > 1 file changed, 6 insertions(+) > = > diff --git a/Documentation/devicetree/bindings/pci/pci.txt b/Documentatio= n/devicetree/bindings/pci/pci.txt > index 6a8f2874a24d..b0cc133ed00d 100644 > --- a/Documentation/devicetree/bindings/pci/pci.txt > +++ b/Documentation/devicetree/bindings/pci/pci.txt > @@ -32,6 +32,12 @@ driver implementation may support the following proper= ties: > root port to downstream device and host bridge drivers can do program= ming > which depends on CLKREQ signal existence. For example, programming ro= ot port > not to advertise ASPM L1 Sub-States support if there is no CLKREQ sig= nal. > +- slot-power-limit-milliwatt: > + If present, this property specifies slot power limit in milliwatts. H= ost > + drivers can parse this property and use it for programming Root Port = or host > + bridge, or for composing and sending PCIe Set_Slot_Power_Limit messag= es > + through the Root Port or host bridge when transitioning PCIe link fro= m a > + non-DL_Up Status to a DL_Up Status. > = > PCI-PCI Bridge properties > ------------------------- > -- = > 2.20.1 > = _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel