Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp2125428pxb; Fri, 25 Mar 2022 11:31:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzC6lrbPelpaNZ+8Fzqb1+d0RdF+f4LNFK/jujvYSyrOEPbaWTyJKxuO70Z17GOI3PSMC49 X-Received: by 2002:a17:902:ea0b:b0:154:7f33:d558 with SMTP id s11-20020a170902ea0b00b001547f33d558mr13232647plg.1.1648233113904; Fri, 25 Mar 2022 11:31:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1648233113; cv=none; d=google.com; s=arc-20160816; b=budnlhSMxH487jpfmIPSCmCaOuScSpH+7jj233IaHyvo/CAL2p4opi+CV1McWoDfcM 7t1B79Eb+4t7z8D3c1/PK+tt7G3w/Cocnby3M+RDWYcG3p0oSS6k64+5NZ+ydcvySDY7 /rRq/Cfv7HEaHQ0tHiJQX1ISc+dvifIW1Tn5cZelI1RvbfF1PJoKBsRyuJAYe1oDNfaQ qgGBrbsNAKhLIlDMRjHRkNMwtmBdyCo6e5wwhnQdXN8frdYSL4sZ3izsr/9NFg8BJQ1J 3yyizboBVrq1+n1AwZIHQM+Y1ASkd6aC9euTzzQ2Z7d4IOBR7yU++O/in+EW58gE5x7O sQfA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:message-id:subject:cc:to:from:date :dkim-signature; bh=dvWsxgGZELDgnjSNyqALjhfu9mu7hFq7nzU2cbcgKfU=; b=vKDsudArk54ZYYxhRnv1Wp5dpEow20n6xEa7kRvbLe6JiXkHWNek7G5CfNil8QKyxl pVXxOxwEEDpCVh7QdoIZwtFVYnB5dCS+t8ZT0XVPdeFjjcDHP7eUuZm5T76bkCkKtylL xRGCxN+WHhqEu9a/ulF1pjeCBVWugntMT71x3M0Q6o7cnm+PGljxnDlv1hUpwLyADzSC tRbT4Di6ZzaBg22oo7luZ8a0i1wpYWg8bqBDIBkJnx16cphTb6DYXjk0wLhkSWmfSfaf 12loJupUX04Fs+pgKoXG6hLlhNPKgUmI9USsGi+nyt1vdBfWV3tA7URu8g7jXkscBIL+ BZhQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=Egwfe4rr; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id t15-20020a17090340cf00b00153b2d16543si2935090pld.331.2022.03.25.11.31.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 25 Mar 2022 11:31:53 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=Egwfe4rr; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 80A24186FBA; Fri, 25 Mar 2022 10:52:51 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1352165AbiCXRPS (ORCPT + 99 others); Thu, 24 Mar 2022 13:15:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34956 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1352161AbiCXRPO (ORCPT ); Thu, 24 Mar 2022 13:15:14 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1EDB6326F7; Thu, 24 Mar 2022 10:13:42 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id BF3C5B82337; Thu, 24 Mar 2022 17:13:40 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 454AEC340EC; Thu, 24 Mar 2022 17:13:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648142019; bh=jMi1G5nIwMEKhuPCL/A1QiK7aP2q19+GorUJGSunucs=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=Egwfe4rrC4QgezISl4qPVGP1OusolFa0RQbX4Ftdyx/XRCHIU/gAhzejII7unpM2o 6SjwZO/Zj797OyqbQg9m8TlsZaXvDgt4CBYY1jdURGssOABT/82RBUpBQiaGiozdI3 NZDZJnWw8iOpbT38ilwI9WmWXzwdLiJRVI9jTlLhjyncEtwLPI0xlSVqXN6wdqn6RO 8uHpM6PnvAZ1BvDbWVZjxoFhnRzbZwYe+hoau7pbIaQwedMuvm5ZosuJeuI/knQz7A NX+zWUaLfR98Kp312ZBhTx+Abn/UynAxReSJVacE/gXuAwoidrONNoi37xAER1mTfk U+celXAOvWMTw== Date: Thu, 24 Mar 2022 12:13:37 -0500 From: Bjorn Helgaas To: Pali =?iso-8859-1?Q?Roh=E1r?= Cc: Lorenzo Pieralisi , Bjorn Helgaas , Rob Herring , 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 v2 3/4] PCI: Add function for parsing 'slot-power-limit-milliwatt' DT property Message-ID: <20220324171337.GA1458545@bhelgaas> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220302145733.12606-4-pali@kernel.org> X-Spam-Status: No, score=-3.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 02, 2022 at 03:57:32PM +0100, Pali Roh?r wrote: > Add function of_pci_get_slot_power_limit(), which parses the > 'slot-power-limit-milliwatt' DT property, returning the value in > milliwatts and in format ready for the PCIe Slot Capabilities Register. > > Signed-off-by: Pali Roh?r > Signed-off-by: Marek Beh?n > Reviewed-by: Rob Herring > --- > Changes in v2: > * Added support for PCIe 6.0 slot power limit encodings > * Round down slot power limit value > --- > drivers/pci/of.c | 64 +++++++++++++++++++++++++++++++++++++++++++++++ > drivers/pci/pci.h | 15 +++++++++++ > 2 files changed, 79 insertions(+) > > diff --git a/drivers/pci/of.c b/drivers/pci/of.c > index cb2e8351c2cc..549a404bd536 100644 > --- a/drivers/pci/of.c > +++ b/drivers/pci/of.c > @@ -633,3 +633,67 @@ int of_pci_get_max_link_speed(struct device_node *node) > return max_link_speed; > } > EXPORT_SYMBOL_GPL(of_pci_get_max_link_speed); > + > +/** > + * of_pci_get_slot_power_limit - Parses the "slot-power-limit-milliwatt" > + * property. > + * > + * @node: device tree node with the slot power limit information > + * @slot_power_limit_value: pointer where the value should be stored in PCIe > + * Slot Capabilities Register format > + * @slot_power_limit_scale: pointer where the scale should be stored in PCIe > + * Slot Capabilities Register format > + * > + * Returns the slot power limit in milliwatts and if @slot_power_limit_value > + * and @slot_power_limit_scale pointers are non-NULL, fills in the value and > + * scale in format used by PCIe Slot Capabilities Register. > + * > + * If the property is not found or is invalid, returns 0. > + */ > +u32 of_pci_get_slot_power_limit(struct device_node *node, > + u8 *slot_power_limit_value, > + u8 *slot_power_limit_scale) > +{ > + u32 slot_power_limit_mw; > + u8 value, scale; > + > + if (of_property_read_u32(node, "slot-power-limit-milliwatt", > + &slot_power_limit_mw)) > + slot_power_limit_mw = 0; > + > + /* Calculate Slot Power Limit Value and Slot Power Limit Scale */ > + if (slot_power_limit_mw == 0) { > + value = 0x00; > + scale = 0; > + } else if (slot_power_limit_mw <= 255) { > + value = slot_power_limit_mw; > + scale = 3; > + } else if (slot_power_limit_mw <= 255*10) { > + value = slot_power_limit_mw / 10; > + scale = 2; > + } else if (slot_power_limit_mw <= 255*100) { > + value = slot_power_limit_mw / 100; > + scale = 1; > + } else if (slot_power_limit_mw <= 239*1000) { > + value = slot_power_limit_mw / 1000; > + scale = 0; > + } else if (slot_power_limit_mw <= 250*1000) { > + value = 0xF0; > + scale = 0; > + } else if (slot_power_limit_mw <= 600*1000) { > + value = 0xF0 + (slot_power_limit_mw / 1000 - 250) / 25; > + scale = 0; > + } else { > + value = 0xFF; > + scale = 0; The purpose of this function is to return values that can be programmed into the Slot Capabilities register. The 0xFF Slot Power Limit Value is reserved, and I don't think we should use it until the spec defines a meaning for it. If the DT tells us 800W is available, we'll put 0xFF in Slot Power Limit Value. If the spec eventually defines (0xFF, 0) to mean "1000W available", a device may try to consume all 1000W, which will not work. If slot_power_limit_mw > 600*1000, I think we should advertise 600W available (value 0xFE, scale 0) and return 600W (600*1000). Bjorn