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 43BCDC77B7C for ; Sun, 30 Apr 2023 19:14:17 +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: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:References: List-Owner; bh=FY5WopKdgVzelMnOOdmQECYJY7fbp1x6peJ1PBaqVwM=; b=g+DkJiMe2Yvm+n 2DF6RvdeJnlX1qSoyxUElpsFersm+lnU9bbR+XzwsjMRWcLp2RW3TTgD/K1Y1MZuZ7VjhBq2j0b6K IOvYgB1N/FBNJPVMK22WDYLry7QWS9OJqA7pniCPkKadhedvl7At9vdF3l5D8Ag6eONQowOvMKuIg SGMHrWGdq1xTffqGw39uY5nbNEwzBXsFF+URKoHwQsQm851UjdfaJlNK/qJO5btL6AT3aNv0/DfMI cQUhAhCCbIOvC8csaGAQ6Wnh0B2a/ylcLOAggTA1u2pn0xQV7O8nDqsb2e9ndeUO8pOGtR30tGkKo HMqzSITink4XVZ2zN3bA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1ptCUC-00Eh1n-0K; Sun, 30 Apr 2023 19:13:28 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1ptCU9-00Eh1Q-2u; Sun, 30 Apr 2023 19:13:27 +0000 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 6A00C60BE9; Sun, 30 Apr 2023 19:13:25 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6CAA4C433EF; Sun, 30 Apr 2023 19:13:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1682882004; bh=CcWs4ZFiQFleSoY0U1jMTWmqa8QyuxQSPZ++resrXaw=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=UGAO3vkoxLYCxIEk6ayKZPHBLR6hzJA+3Z6Os6wYLCDWs2JuwJjtt/s/UJlAt8j+d 81aob+39TTL6uKuO1Ndaq4zQ++yN13GrN9d7iccp+r1U8FVxQmq36LlFDb4PxnYEoh CgXPAdL5EqjK9Qubt51argcyukDYx9BewJ0J97k6PG/vG/DHQxMw5Ac8guJAc4OWlj snRZzZvQ092Uasen7m3FUOO2cUOze4zIL6nDwLLC48TVIAaQhv4NC6kTgXveRu3Fuq I8DRCLgzP1ttrno05/S6MWZARvMhPpsfENfn/6A7gJ/8C0a18ym8IAki3eYb1Awjxt FQ3tMq8shkQXQ== Date: Sun, 30 Apr 2023 14:13:23 -0500 From: Bjorn Helgaas To: Jim Quinlan Cc: linux-pci@vger.kernel.org, Nicolas Saenz Julienne , Bjorn Helgaas , Lorenzo Pieralisi , Cyril Brulebois , Phil Elwell , bcm-kernel-feedback-list@broadcom.com, james.quinlan@broadcom.com, Florian Fainelli , Lorenzo Pieralisi , Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , Rob Herring , "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" , "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" , open list Subject: Re: [PATCH v4 3/5] PCI: brcmstb: Set PCIe transaction completion timeout Message-ID: <20230430191323.GA388047@bhelgaas> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20230428223500.23337-4-jim2101024@gmail.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230430_121325_976530_8A529562 X-CRM114-Status: UNSURE ( 9.40 ) X-CRM114-Notice: Please train this message. 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="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Apr 28, 2023 at 06:34:57PM -0400, Jim Quinlan wrote: > Since the STB PCIe HW will cause a CPU abort on a PCIe transaction > completion timeout abort, we might as well extend the default timeout > limit. Further, different devices and systems may requires a larger or > smaller amount commensurate with their L1SS exit time, so the property > "brcm,completion-timeout-us" may be used to set a custom timeout value. s/requires/require/ AFAIK, other platforms do not tweak Configuration Timeout values based on L1SS exit time. Why is brcm different? Bjorn _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel