Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp329689pxb; Tue, 12 Apr 2022 03:02:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzbm/BpnFPoQXXjmOPEvI1O6V5l8NH9HMa2leKCxAn1Mjh6eaqlAku9G7/VwK9KVREKnZ4r X-Received: by 2002:a17:90a:c484:b0:1ca:8896:5db9 with SMTP id j4-20020a17090ac48400b001ca88965db9mr4087162pjt.143.1649757778126; Tue, 12 Apr 2022 03:02:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649757778; cv=none; d=google.com; s=arc-20160816; b=FJDtfXC1aG4L0jQA+d2pceelXYAsEm6y5Up0kHWzBJFvqDZwTJSSqqXl4mVdwquxWL gtyoYgOF1tc0TJnPkygTQuNGr0610Xqoan0nkDii4RQDuuO0ZOCFfng60uzN/CNvAkpT gQ0BdsMNIpUHBtrXPXu17ABPfrock/i7CFPtJ0sTR/Qb8C32IocouzD6U4QGcmgdV/o/ LLS/F4HWNudSexSl5tG0/7ZH6oo8iKODgR4DiMf/+wj+1ck+mhcl1L8Qk7eYjKKODM2A kMTJHGvgZllSjzYutr/yf/Eov2sDN2We8oD2aUgCbfcx+11aWccKzu6hx/kjJ7HqLacd wYnQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=XK6V3c66sZC/B3xOvuL/YS556YF/Oclc8rV/YnsnKPw=; b=ZZDg4GepKTyDYgss/xtHsz/vuNkyb3o+nF1EjYX3ZvHIZfwDHW5KejVyYQXRUXDE5z HkdDq+D6Xv2xSr8MHZgt/7uadOkrZwxw00jVUCLikxfu8BZAVAKgX5pQwhlxdCOejzhZ h2qKfd1L9/tTOJQ9yx3/80AXJFCYWVxhTfsaK6wG0XUK4LMbH/Kno9Dau7d1+abNTm17 jmlEp0z2GDyPJnLZD6MvrJuhuZ8DSgRN0xOJW/WJ2gTyv2dY08ELYYdgIOTBe/vExyX3 G8BPAQYba8CtHH4Lhja0G6SuRzW1bzXNhR3p7xzQOQIT4JCZRB0HnP/kf7rdNH6LpcI5 Anow== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=IpA0H2qT; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t190-20020a6381c7000000b0039d9d578259si676969pgd.30.2022.04.12.03.02.40; Tue, 12 Apr 2022 03:02:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=IpA0H2qT; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346201AbiDKTEe (ORCPT + 99 others); Mon, 11 Apr 2022 15:04:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33168 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229764AbiDKTEd (ORCPT ); Mon, 11 Apr 2022 15:04:33 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6C8263299A; Mon, 11 Apr 2022 12:02:18 -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 dfw.source.kernel.org (Postfix) with ESMTPS id ED6036140D; Mon, 11 Apr 2022 19:02:17 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 074E9C385A3; Mon, 11 Apr 2022 19:02:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1649703737; bh=+tmcTmEhf/OADWe19T62/vDLGlq6GTerOSnvHZpMSKU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=IpA0H2qTdjOmqQitGP/Gq/2QUre3o1/dPOUDz0kikY9X/7cVtTlNThddTnJcRO/0F w0kIapxpyP4R8YJmW9hHeJN9L4n+HoWGWScA15BqG0ff//JMbhbrz/edmKuCYaScg8 ovKLiGr9o9PSHcXbk9SOnCVeZ+wD8vvseJgQ12BkBhRyii1RQfXFp320llmkGQTQgK ynOA6djmKYHjhu5xq4c1VMPBGU+3wF2jq0PxW/jK0uz5s9Ei0m2WuvWTYO0PQLCt2G DGLPE/lQ69qztf3iS3Ojq/5qvi5IHRxghIlTywOdn0rU1KAfAxpSDRxNq2mC1BXLYs djtlrTDmF6N5w== Received: by pali.im (Postfix) id B261A947; Mon, 11 Apr 2022 21:02:14 +0200 (CEST) Date: Mon, 11 Apr 2022 21:02:14 +0200 From: Pali =?utf-8?B?Um9ow6Fy?= To: Bjorn Helgaas Cc: Lorenzo Pieralisi , Bjorn Helgaas , Rob Herring , Andrew Lunn , Thomas Petazzoni , Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , Marek =?utf-8?B?QmVow7pu?= , Russell King , linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 3/4] PCI: Add function for parsing 'slot-power-limit-milliwatt' DT property Message-ID: <20220411190214.hmeau774tnrnbcod@pali> References: <20220325093827.4983-4-pali@kernel.org> <20220408152750.GA306189@bhelgaas> <20220411111407.7ycuoldxjvqnkoo4@pali> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220411111407.7ycuoldxjvqnkoo4@pali> User-Agent: NeoMutt/20180716 X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham 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 Monday 11 April 2022 13:14:07 Pali Rohár wrote: > On Friday 08 April 2022 10:27:50 Bjorn Helgaas wrote: > > On Fri, Mar 25, 2022 at 10:38:26AM +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 v3: > > > * Set 600 W when DT slot-power-limit-milliwatt > 600 W > > > 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..5ebff26edd41 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; > > > > I think the spec is poorly worded here. PCIe r6.0, sec 7.5.3.9, says: > > > > F0h > 239 W and <= 250 W Slot Power Limit > > > > I don't think it's meaningful for the spec to include a range here. > > The amount of power the slot can supply has a single maximum. I > > suspect the *intent* of F0h/00b is that a device in the slot may > > consume up to 250W. > > > > Your code above would mean that slot_power_limit_mw == 245,000 would > > cause the slot to advertise F0h/00b (250W), which seems wrong. > > So for slot_power_limit_mw == 245 W we should set following values? > > slot_power_limit_mw = 239 W > value = 0xF0 > scale = 0 I changed it in v4 > > I think we should do something like this instead: > > > > scale = 0; > > if (slot_power_limit_mw >= 600*1000) { > > value = 0xFE; > > slot_power_limit_mw = 600*1000; > > } else if (slot_power_limit_mw >= 575*1000) { > > value = 0xFD; > > slot_power_limit_mw = 575*1000; > > } ... > > This is already implemented in branch: > > } else if (slot_power_limit_mw <= 600*1000) { > value = 0xF0 + (slot_power_limit_mw / 1000 - 250) / 25; > scale = 0; > > I will just add reducing of final slot_power_limit_mw value. > > > I raised an issue with the PCI SIG about this. > > > > > + } else if (slot_power_limit_mw <= 600*1000) { > > > + value = 0xF0 + (slot_power_limit_mw / 1000 - 250) / 25; > > > + scale = 0; > > > + } else { > > > + value = 0xFE; > > > + scale = 0; > > > + } > > > + > > > + if (slot_power_limit_value) > > > + *slot_power_limit_value = value; > > > + > > > + if (slot_power_limit_scale) > > > + *slot_power_limit_scale = scale; > > > + > > > + return slot_power_limit_mw; > > > > If the DT tells us 800W is available, we'll store (FEh/00b), which > > means the slot can advertise to a downstream device that 600W is > > available. I think that's correct, since the current spec doesn't > > provide a way to encode any value larger than 600W. > > > > But the function still returns 800,000 mW, which means the next patch will > > print: > > > > %s: Slot power limit 800.0W > > > > even though it programs Slot Capabilities to advertise 600W. > > That's why I suggested setting slot_power_limit_mw = 600*1000 above. > > Ok, I will update slot_power_limit_mw value in next patch version. And also fixed this in v4. Please review v4 if is is OK now. > > > +} > > > +EXPORT_SYMBOL_GPL(of_pci_get_slot_power_limit); > > > diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h > > > index 3d60cabde1a1..e10cdec6c56e 100644 > > > --- a/drivers/pci/pci.h > > > +++ b/drivers/pci/pci.h > > > @@ -627,6 +627,9 @@ struct device_node; > > > int of_pci_parse_bus_range(struct device_node *node, struct resource *res); > > > int of_get_pci_domain_nr(struct device_node *node); > > > int of_pci_get_max_link_speed(struct device_node *node); > > > +u32 of_pci_get_slot_power_limit(struct device_node *node, > > > + u8 *slot_power_limit_value, > > > + u8 *slot_power_limit_scale); > > > void pci_set_of_node(struct pci_dev *dev); > > > void pci_release_of_node(struct pci_dev *dev); > > > void pci_set_bus_of_node(struct pci_bus *bus); > > > @@ -653,6 +656,18 @@ of_pci_get_max_link_speed(struct device_node *node) > > > return -EINVAL; > > > } > > > > > > +static inline u32 > > > +of_pci_get_slot_power_limit(struct device_node *node, > > > + u8 *slot_power_limit_value, > > > + u8 *slot_power_limit_scale) > > > +{ > > > + if (slot_power_limit_value) > > > + *slot_power_limit_value = 0; > > > + if (slot_power_limit_scale) > > > + *slot_power_limit_scale = 0; > > > + return 0; > > > +} > > > + > > > static inline void pci_set_of_node(struct pci_dev *dev) { } > > > static inline void pci_release_of_node(struct pci_dev *dev) { } > > > static inline void pci_set_bus_of_node(struct pci_bus *bus) { } > > > -- > > > 2.20.1 > > > > > > > > > _______________________________________________ > > > linux-arm-kernel mailing list > > > linux-arm-kernel@lists.infradead.org > > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel