From patchwork Wed Apr 3 21:38:57 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jim Quinlan X-Patchwork-Id: 1919432 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@legolas.ozlabs.org Authentication-Results: legolas.ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=broadcom.com header.i=@broadcom.com header.a=rsa-sha256 header.s=google header.b=FBsGBO9D; dkim-atps=neutral Authentication-Results: legolas.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=vger.kernel.org (client-ip=2604:1380:45d1:ec00::1; helo=ny.mirrors.kernel.org; envelope-from=devicetree+bounces-56071-incoming-dt=patchwork.ozlabs.org@vger.kernel.org; receiver=patchwork.ozlabs.org) Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org [IPv6:2604:1380:45d1:ec00::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384) (No client certificate requested) by legolas.ozlabs.org (Postfix) with ESMTPS id 4V8ynN04Pbz1yYn for ; Thu, 4 Apr 2024 08:39:19 +1100 (AEDT) Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id EDF4F1C20FCA for ; Wed, 3 Apr 2024 21:39:15 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id CB5DA156872; Wed, 3 Apr 2024 21:39:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b="FBsGBO9D" X-Original-To: devicetree@vger.kernel.org Received: from mail-qv1-f47.google.com (mail-qv1-f47.google.com [209.85.219.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5662818AF9 for ; Wed, 3 Apr 2024 21:39:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.219.47 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712180349; cv=none; b=YdYDpgRMQ7G+AtGOBEZtMzGYo0cgmbqb5BMi6NpK5YqCz4Rqoiyfz9k4GRToctliUQOCCtgjHRxnciaGxrv052ug+1hLz2irgXNoOpGTLcq9PfiMGTODZcE9O9FBTJx4UXo1NkPccm2zefI7S2/2siQyoSRBuP/U8LxA9hPgHDQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712180349; c=relaxed/simple; bh=IVQYPk1s252I47NjZIx7g5oUxGOk5MteJXVTVpe42SU=; h=From:To:Cc:Subject:Date:Message-Id:Content-Type; b=f25fcenI26ZrByfGXyXrLzBHDKbHjHBZw/s4XRmNrn9CsPn/7D/p10H0Pw5dSY4H2yvNDuc6jpCpkUenqgFW7Kn4hIukOWDq0qMo75Y9/j6dStZra6eRMPLbyVhpjmqX1ZLCBt4pCMQP0rMeNSRNBf4vFngHLzDxn2GKan/z8Wk= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=broadcom.com; spf=fail smtp.mailfrom=broadcom.com; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b=FBsGBO9D; arc=none smtp.client-ip=209.85.219.47 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=broadcom.com Authentication-Results: smtp.subspace.kernel.org; spf=fail smtp.mailfrom=broadcom.com Received: by mail-qv1-f47.google.com with SMTP id 6a1803df08f44-696609f5cf2so1417716d6.3 for ; Wed, 03 Apr 2024 14:39:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; t=1712180346; x=1712785146; darn=vger.kernel.org; h=message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=0z5Ze8OcuU5SJHAx3IlsTdj8Cm5Qp+mF5Ssh5F+nDE4=; b=FBsGBO9Dps4cWY2BxhE91KmsLI2hxYNFgUZQLkLNNseMKbuRPvUaqs2OMzZn4niHLl prNWiuZ2/9+UbaEgUE7A9aGiriE9CeV0rVnF6xvuijJTJ5NxbZNN+hbcLbbZlT2w9egP 9vn+h6KKUME1fkexJbRp5RROMeAq+VHlP82Z4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712180346; x=1712785146; h=message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=0z5Ze8OcuU5SJHAx3IlsTdj8Cm5Qp+mF5Ssh5F+nDE4=; b=Jcm66OslK26KaXdolWqNz8tv262oxe6Bg3DSiu57BTfHDKSgyhO0HxT88w5UetyOzJ njLLZyUyxEXL0UCR07/yVxuH0Q0ZhOs27wH0fyHEwPeq7rZzM2hK24/PQtiqCnbt+XbE RZje831HaI6rd1dWrrWlqwwrTsUvt4d898ktm0kWn0S11OIJ8/cOGPL3ikzJ9Nz4k2bf v/dNfzqpN2Vjk6kMQU/PgDcqBocUnyrXSesiuE/dcfT/iubuvn0gglT9eZMJ1zbaWMwA q3j9Vpavg3VYab+HDMPRwzDsR3weVz7FEH1h2g/ytNc3tjbF3Ugx8a1qrm5it2nz+evU 8PaQ== X-Forwarded-Encrypted: i=1; AJvYcCXsGD+zOp4IfFoYjFOgznKyiC2jmPPkPothF6O54+SAn2Cyds4bZpkZfYyQXuiUQdLgKAlRlXGXwIiQiSYIxYjM92ePD7/YUgeCGA== X-Gm-Message-State: AOJu0YxD4X3jb9+LdPKdTwv2XW5fjBK2RHk/5gilOSGmitTXKrStQv4I 3sBK+u2pBKEVu0uoQD0y1gBBu2WR0MSTBn7dvYQhqFBWb37z8pCTimC4CU9LIQ== X-Google-Smtp-Source: AGHT+IGni7gUlENPqzNkj4V/aInZkN+dBK2xlOx2HZCXjX4JhCqOiBtP3UpMHcyGVCDFWcHfeVazag== X-Received: by 2002:ad4:4eef:0:b0:699:3051:a7e5 with SMTP id dv15-20020ad44eef000000b006993051a7e5mr624650qvb.30.1712180346234; Wed, 03 Apr 2024 14:39:06 -0700 (PDT) Received: from stbsrv-and-01.and.broadcom.net ([192.19.144.250]) by smtp.gmail.com with ESMTPSA id pi10-20020a0562144a8a00b0069903cddc96sm1750739qvb.18.2024.04.03.14.39.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 03 Apr 2024 14:39:05 -0700 (PDT) From: Jim Quinlan To: 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 Cc: Conor Dooley , devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS), Florian Fainelli , Jim Quinlan , Krzysztof Kozlowski , =?utf-8?q?Krzyszto?= =?utf-8?q?f_Wilczy=C5=84ski?= , linux-arm-kernel@lists.infradead.org (moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE), linux-kernel@vger.kernel.org (open list), linux-rpi-kernel@lists.infradead.org (moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE), Lorenzo Pieralisi , Rob Herring Subject: [PATCH v9 0/4] PCI: brcmstb: Configure appropriate HW CLKREQ# mode Date: Wed, 3 Apr 2024 17:38:57 -0400 Message-Id: <20240403213902.26391-1-james.quinlan@broadcom.com> X-Mailer: git-send-email 2.17.1 Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: v9 -- v8 was setting an internal bus timeout to accomodate large L1 exit latencies. After meeting the PCIe HW team it was revealed that the HW default timeout value was set low for the purposes of HW debugging convenience; for nominal operation it needs to be set to a higher value independent of this submission's purpose. This is now a separate commit. -- With v8, Bjorne asked what was preventing a device from exceeding the time required for the above internal bus timeout. The answer to this is for us to set the endpoints' max latency {no-,}snoop value to something below this internal timeout value. If the endpoint respects this value as it should, it will not send an LTR request with a larger latency value and not put itself in a situation that requires more latency than is possible for the platform. Typically, ACPI or FW sets these max latency values. In most of our systems we do not have this happening so it is up to the RC driver to set these values in the endpoint devices. If the endpoints already have non-zero values that are lower than what we are setting, we let them be, as it is possible ACPI or FW set them and knows something that we do not. -- The "clkreq" commit has only been changed to remove the code that was setting the timeout value, as this code is now its own commit. v8 -- Un-advertise L1SS capability when in "no-l1ss" mode (Bjorn) -- Squashed last two commits of v7 (Bjorn) -- Fix DT binding description text wrapping (Bjorn) -- Fix incorrect Spec reference (Bjorn) s/PCIe Spec/PCIe Express Mini CEM 2.1 specification/ -- Text substitutions (Bjorn) s/WRT/With respect to/ s/Tclron/T_CLRon/ v7 -- Manivannan Sadhasivam suggested (a) making the property look like a network phy-mode and (b) keeping the code simple (not counting clkreq signal appearances, un-advertising capabilites, etc). This is what I have done. The property is now "brcm,clkreq-mode" and the values may be one of "safe", "default", and "no-l1ss". The default setting is to employ the most capable power savings mode. v6 -- No code has been changed. -- Changed commit subject and comment in "#PERST" commit (Bjorn, Cyril) -- Changed sign-off and author email address for all commits. This was due to a change in Broadcom's upstreaming policy. v5 -- Remove DT property "brcm,completion-timeout-us" from "DT bindings" commit. Although this error may be reported as a completion timeout, its cause was traced to an internal bus timeout which may occur even when there is no PCIe access being processed. We set a timeout of four seconds only if we are operating in "L1SS CLKREQ#" mode. -- Correct CEM 2.0 reference provided by HW engineer, s/3.2.5.2.5/3.2.5.2.2/ (Bjorn) -- Add newline to dev_info() string (Stefan) -- Change variable rval to unsigned (Stefan) -- s/implementaion/implementation/ (Bjorn) -- s/superpowersave/powersupersave/ (Bjorn) -- Slightly modify message on "PERST#" commit. -- Rebase to torvalds master v4 -- New commit that asserts PERST# for 2711/RPi SOCs at PCIe RC driver probe() time. This is done in Raspian Linux and its absence may be the cause of a failing test case. -- New commit that removes stale comment. v3 -- Rewrote commit msgs and comments refering panics if L1SS is enabled/disabled; the code snippet that unadvertises L1SS eliminates the panic scenario. (Bjorn) -- Add reference for "400ns of CLKREQ# assertion" blurb (Bjorn) -- Put binding names in DT commit Subject (Bjorn) -- Add a verb to a commit's subject line (Bjorn) -- s/accomodat(\w+)/accommodat$1/g (Bjorn) -- Rewrote commit msgs and comments refering panics if L1SS is enabled/disabled; the code snippet that unadvertises L1SS eliminates the panic scenario. (Bjorn) v2 -- Changed binding property 'brcm,completion-timeout-msec' to 'brcm,completion-timeout-us'. (StefanW for standard suffix). -- Warn when clamping timeout value, and include clamped region in message. Also add min and max in YAML. (StefanW) -- Qualify description of "brcm,completion-timeout-us" so that it refers to PCIe transactions. (StefanW) -- Remvove mention of Linux specifics in binding description. (StefanW) -- s/clkreq#/CLKREQ#/g (Bjorn) -- Refactor completion-timeout-us code to compare max and min to value given by the property (as opposed to the computed value). v1 -- The current driver assumes the downstream devices can provide CLKREQ# for ASPM. These commits accomodate devices w/ or w/o clkreq# and also handle L1SS-capable devices. -- The Raspian Linux folks have already been using a PCIe RC property "brcm,enable-l1ss". These commits use the same property, in a backward-compatible manner, and the implementaion adds more detail and also automatically identifies devices w/o a clkreq# signal, i.e. most devices plugged into an RPi CM4 IO board. Jim Quinlan (4): dt-bindings: PCI: brcmstb: Add property "brcm,clkreq-mode" PCI: brcmstb: Set reasonable value for internal bus timeout PCI: brcmstb: Set downstream maximum {no-}snoop LTR values PCI: brcmstb: Configure HW CLKREQ# mode appropriate for downstream device .../bindings/pci/brcm,stb-pcie.yaml | 18 ++ drivers/pci/controller/pcie-brcmstb.c | 161 +++++++++++++++++- 2 files changed, 170 insertions(+), 9 deletions(-) base-commit: 9f8413c4a66f2fb776d3dc3c9ed20bf435eb305e Tested-by: Cyril Brulebois